ECommPay Gate API
ECommPay Gate API
Flutterwave
Card payments
Token operations
Cash Voucher actions
Additional information submission
ADVCash
Apple Pay
Asian Banks
ATM
Bancontact
Banks
Bank Transfer
Card payments via partners
Cash
Cash in Kazakhstan
China UnionPay
Crypto
EcoPayz
Money transfer payments
Google Pay
Interac E-Transfer
Mobile
M-Pesa
Neteller
Online banking
Payment links
Qiwi Wallet
Skrill
Turkey QR
Voucher
Wallet
Wallet payments via partners
WebMoney
Requests for customer details
Customer actions
Requests for information
Neosurf
Models
Powered by Stoplight

Requests

The ECommPay payment platform accepts POST requests supporting HTTP version 1.1 or higher and TLS of version 1.2 or higher in JSON format. Requests can be processed synchronously or asynchronously depending on the type of the request.

Requests for retrieving information (for example, to check payment status) are processed synchronously. The payment platform receives the request and returns the HTTP response that contains the required information within one HTTP session because processing such requests requires only the resources of the platform.

Requests for making payments are processed asynchronously. The payment platform receives the request and returns the HTTP response first, following which intermediate and final results of the payment processing are returned in callbacks to the web service URL (for example, when additional actions from the merchant are required, or once the payment has been fully processed).

For more information, see Interaction concepts.