Payments
This API uses OAuth 2 with the client credentials flow. More info
ID of the request, unique to the call, as determined by the initiating party
Identifies the method or channel through which a payment was initiated:
- BROWSER - payment initiated when the customer makes a regular online purchase via a website (e-shop)
Description of the payment
Merchant's payment reference
Merchant's order number
^[a-zA-Z0-9/-?:().,'+\-]*$Unique ID of the participant
Default country for bank selection in the gateway hosted checkout page
Default locale for the gateway hosted checkout page
Unique ID of the shop
OK
Unique ID of the participant
Unique ID of the payment
Bad Request
Forbidden
Not Found
Conflict
Service Unavailable
This API uses OAuth 2 with the client credentials flow. More info
ID of the request, unique to the call, as determined by the initiating party
Identifies the method or channel through which a payment was initiated:
- RECURRING - payment initiated by the merchant or backend system without customer presence, on a predefined schedule with a fixed or variable amount (e.g., monthly subscription, utility bill)
- MERCHANT - payment initiated by the merchant or backend system without customer presence, on an ad-hoc basis with a variable amount and undefined frequency (e.g., automatic top-up, partial shipments, no-show fees, or other post-service charges)
Description of the payment
Merchant's payment reference
Merchant's order number
^[a-zA-Z0-9/-?:().,'+\-]*$Unique ID of the participant
Unique ID of the shop
OK
Unique ID of the participant
Unique ID of the payment
Bad Request
Forbidden
Not Found
Conflict
Service Unavailable
This API uses OAuth 2 with the client credentials flow. More info
Unique ID of the payment
ID of the request, unique to the call, as determined by the initiating party
OK
Identifies the method or channel through which a payment was initiated:
- BROWSER - payment initiated when the customer makes a regular online purchase via a website (e-shop)
- RECURRING - payment initiated by the merchant or backend system without customer presence, on a predefined schedule with a fixed or variable amount (e.g., monthly subscription, utility bill)
- MERCHANT - payment initiated by the merchant or backend system without customer presence, on an ad-hoc basis with a variable amount and undefined frequency (e.g., automatic top-up, partial shipments, no-show fees, or other post-service charges)
- PAYMENT_LINK - payment initiated when the customer clicks a link provided by the merchant (e.g., via a button in an app or website, a link sent via SMS, chat or other messaging channel)
- QR_CODE - payment initiated when the customer scans a QR code presented by the merchant (e.g., in-store or on-screen)
Merchant's payment reference
Merchant's order number
Unique ID of the participant
Unique ID of the payment
Bad Request
Forbidden
Not Found
Conflict
Service Unavailable
This API uses OAuth 2 with the client credentials flow. More info
Unique ID of the payment
ID of the request, unique to the call, as determined by the initiating party
The request for capturing an existing payment
OK
The response after capturing a card payment
Unique ID of the payment
Current status of the payment
Bad Request
Forbidden
Not Found
Conflict
Service Unavailable
This API uses OAuth 2 with the client credentials flow. More info
Unique ID of the payment
ID of the request, unique to the call, as determined by the initiating party
The request for cancelling a payment
Reason to cancel the payment
OK
The response after cancelling a payment
Unique ID of the payment
Current status of the payment
Bad Request
Forbidden
Not Found
Conflict
Service Unavailable
Last updated
Was this helpful?

