Payments

Create a new customer-initiated payment

post

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.

Authorizations
OpenID ConnectRequired

This API uses OAuth 2 with the client credentials flow. More info

Path parameters
versionstringRequired
Header parameters
X-Request-Idstring · uuidRequired

ID of the request, unique to the call, as determined by the initiating party

Body
channelstring · enumRequired

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)
Possible values:
descriptionstring · max: 255Optional

Description of the payment

merchantReferencestring · max: 255Optional

Merchant's payment reference

orderNumberstring · max: 255Required

Merchant's order number

Pattern: ^[a-zA-Z0-9/-?:().,'+\-]*$
participantIdstring · max: 64Required

Unique ID of the participant

preferredCountrystringOptional

Default country for bank selection in the gateway hosted checkout page

preferredLocalestring · enumOptional

Default locale for the gateway hosted checkout page

Possible values:
shopAgreementIdstring · max: 64Required

Unique ID of the shop

shopRedirectUrlstring · min: 1Required
Responses
post
/egw/{version}/payments/cit

Create a new merchant-initiated payment

post

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.

Authorizations
OpenID ConnectRequired

This API uses OAuth 2 with the client credentials flow. More info

Path parameters
versionstringRequired
Header parameters
X-Request-Idstring · uuidRequired

ID of the request, unique to the call, as determined by the initiating party

Body
channelstring · enumRequired

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)
Possible values:
descriptionstring · max: 255Optional

Description of the payment

merchantReferencestring · max: 255Optional

Merchant's payment reference

orderNumberstring · max: 255Required

Merchant's order number

Pattern: ^[a-zA-Z0-9/-?:().,'+\-]*$
participantIdstring · max: 64Required

Unique ID of the participant

shopAgreementIdstring · max: 64Required

Unique ID of the shop

Responses
post
/egw/{version}/payments/mit

Get payment information

get

Returns the content of a payment object

Authorizations
OpenID ConnectRequired

This API uses OAuth 2 with the client credentials flow. More info

Path parameters
paymentIdstring · max: 64Required

Unique ID of the payment

versionstringRequired
Query parameters
Header parameters
X-Request-Idstring · uuidRequired

ID of the request, unique to the call, as determined by the initiating party

Responses
get
/egw/{version}/payments/{paymentId}

Captures an existing payment

patch

Capturing an authorized payment will complete (finalise) the payment, this is only used for card payments

Authorizations
OpenID ConnectRequired

This API uses OAuth 2 with the client credentials flow. More info

Path parameters
paymentIdstring · max: 64Required

Unique ID of the payment

versionstringRequired
Header parameters
X-Request-Idstring · uuidRequired

ID of the request, unique to the call, as determined by the initiating party

Body

The request for capturing an existing payment

Responses
patch
/egw/{version}/payments/{paymentId}/capture

Cancels a payment

patch

A payment can be cancelled when it is initialized or authorized

Authorizations
OpenID ConnectRequired

This API uses OAuth 2 with the client credentials flow. More info

Path parameters
paymentIdstring · max: 64Required

Unique ID of the payment

versionstringRequired
Header parameters
X-Request-Idstring · uuidRequired

ID of the request, unique to the call, as determined by the initiating party

Body

The request for cancelling a payment

reasonstring · enumOptional

Reason to cancel the payment

Possible values:
Responses
patch
/egw/{version}/payments/{paymentId}/cancel

Last updated

Was this helpful?