OP Online Payment - Merchant Callback API (1.2.2-oas3.1)
Download OpenAPI specification:Download
OP Online Payment allows merchants and payment service providers to collect e-commerce payments as credit transfers to an OP account from both OP customers and other banks' customers (add-on service).
The OP Online Payment service includes the collection of payments and the making of payment status requests and payment refunds. OP Online Payment API's documentation consists of three parts:
- REST API: initiation of online payments, refund and status query
- Browser flow API: initiation of the payment flow in the browser
- Merchant callback API: an optional service for receiving notifications on the payment status changes
The Merchant callback API defines a specification for a backend interface capable of receiving notifications from the OP Online Payment service. Implementing this interface is optional for merchants, but highly recommended.
The notifications are sent to the target URL provided by the merchant when the payment is created in the OP Online Payment REST API.
The authenticity and integrity of the notification is verified according to the authentication signature scheme described in the document Authentication Signature for OP Online Payment API using the HMAC signature received and the public key of OP.
v1.2.1 (04/2024)
Added
- added code examples for Payment status change notification signature verifying event handlers in multiple languages
Changed
- Updated API doc format from OpenAPI 3.0.1 to 3.1.0
v1.2 (03/2024)
Changed
- Updated API doc format from Swagger 2.0 to OpenAPI 3.0.1
v1.1.1 (12/2020)
Initial version
Payment status change notification Webhook
The following notification is sent to the merchant’s callback address when the status of the payment changes. The notification is sent once, and the merchant should respond with HTTP 200 OK response when the notification has been received. The merchant should define its callback address when creating an Online Payment using the REST API.
Authorizations:
header Parameters
x-request-id required | string <uuid> <= 36 characters Unique identifier (UUID) of the request. |
x-session-id required | string <uuid> <= 36 characters Unique identifier (UUID) of the session. |
Date required | string Standard HTTP Date header containing the date and time when the request was sent. |
Request Body schema: application/jsonrequired
Result info
paymentId required | string <alphanumeric> <= 36 characters ID of the payment (from the OP Online Payment REST API Create payment response). |
status required | string Enum: "CANCELLED" "REJECTED" "PROCESSED"
|
paymentType required | string Enum: "INVOICE" "CREDIT" "OTHER_CREDIT"
|
Responses
Request samples
- Payload
- HTTP wire request (example)
- C#
- Java
- Node.js
- PHP
- Python
{- "paymentId": "ec1253bd-791a-4252-9da8-b1d7163d3c69",
- "status": "PROCESSED",
- "paymentType": "CREDIT"
}