Payments
Creates a new customer-initiated payment.
After a payment is created a payment method (card, bank, saved token) must be added to it. The user can attempt adding payment method multiple times until ultimately one is successful. The checkout process is continued by either redirecting the user to the gateway hosted checkout page or integrating directly with EGW APIs.
Additionally, the setupToken fields can be used to save the used payment method for future 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
Bad Request
Forbidden
Not Found
Conflict
Service Unavailable
Creates a new merchant-initiated payment - payment without direct involvement of the end user (e.g. subscriptions).
Only previously saved payment method token can be used for merchant-initiated payments. Before creating merchant-initiated payments it is necessary to setup a token agreement during an initial customer-initiated payment.
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
Bad Request
Forbidden
Not Found
Conflict
Service Unavailable
Returns the content of a payment object
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
Bad Request
Forbidden
Not Found
Conflict
Service Unavailable
Capturing an authorized payment will complete (finalise) the payment, this is only used for card payments
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
Bad Request
Forbidden
Not Found
Conflict
Service Unavailable
A payment can be cancelled when it is initialized or authorized
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
Bad Request
Forbidden
Not Found
Conflict
Service Unavailable
Last updated
Was this helpful?

