Embedded Payment flow
Use the embedded flow so that payer does not leave your checkout page
Introduction
Use our direct payment processing endpoints to start a transaction in the embedded flow. The payer can start a transaction (CIT) on your website or your point of sale. Or you (the merchant) can start the payment without interaction with the payer (MIT). The status can be fetched via the Order:Status API or via our exchange calls/webhooks.
A transaction can be completed at once, or use the Authorize & Capture flow depending on the payment method used.

Click on the recipe below to get more detailed information regarding the embedded flow
Third party 3DSecure providers
If you like to use an external 3DSecure provider, you need to register them merchant and our acquirer BIN's in their system. Please make sure that this provider is always using up to date directory servers and versions on based on 3DSecure 2.2
Scheme | Acquiring BIN |
---|---|
Visa | 439557 |
Mastercard | 270204 |
American Express | 10000000232 |
Bancontact | 700012 |
The merchant ID and MCC can be found in the Global Management System and can be different based on the used serviceId
Example of a payload that the 3DS vendor should send in to the scheme.
[
'acctNumber' => '670364*******8004',
'acquirerBIN' => '#############', // GET_FROM_LIST_ABOVE
'acquirerMerchantID' => '', // GET_FROM_CONFIG
'mcc' => '####', // GET_FROM_CONFIG
'merchantCountryCode' => '528', // GET_FROM_CONFIG
'merchantName' => 'TRADE.NAME', // GET_FROM_CONFIG
......
]
Updated 3 months ago