Skip to main content
Bancontact is a widely used online payment method in Belgium. Customers pay with a Bancontact card or the Bancontact app linked to their Belgian bank account, and confirm each payment with their bank. Payrails processes Bancontact through five payment service providers (PSPs). The flow is the same with each one, but the required request fields and the supported workflows differ. Pick a PSP below for its setup steps and request examples.

​
How a Bancontact payment works

Bancontact is a redirect payment method:
  1. The customer selects Bancontact at checkout.
  2. Payrails returns a redirect URL from the PSP, and the customer goes to Bancontact or their bank.
  3. The customer confirms the payment in the Bancontact app or with their bank.
  4. The customer returns to your returnInfo URL.
  5. Payrails receives the final result from the PSP and updates the payment.
Each payment is single-use: the customer confirms every payment on its own. Payrails captures Bancontact payments immediately, so a successful payment is final. To return funds, refund the payment. Refunds work with every PSP except Worldpay.

​
Supported currencies and countries

Bancontact supports EUR (euro) as its only presentment currency.

​
Integrate Bancontact

Choose the PSP that processes Bancontact for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

Adyen

Bancontact via Adyen

Checkout.com

Bancontact via Checkout.com

Nuvei

Bancontact via Nuvei

Stripe

Bancontact via Stripe

Worldpay

Bancontact via Worldpay

​
Compare PSPs

Save Instruments and merchant-initiated transactions (MIT) work only with Adyen. The first Bancontact payment through Adyen creates a SEPA Direct Debit mandate, and Payrails charges later MIT payments against that mandate.

​
Ways to integrate Bancontact

  • Payrails SDK: the Web SDK shows Bancontact when your workflow returns it as a payment option, and redirects the customer to complete the payment. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with bancontact as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026