Introduction
Bancontact uses a redirect-based payment flow. When a customer selects Bancontact at checkout, they are redirected to their bank’s interface to authenticate and authorize the payment, then redirected back to your website or app upon completion. Bancontact is a single-use payment method where customers must authenticate each payment. This guide explains the process of integrating Bancontact into your app or website using Payrails via Stripe.Pre-requisites
Before you start accepting Bancontact payments with Payrails, there are a few requirements you must meet:Your use of Bancontact must be in accordance with Stripe’s Bancontact Terms of Service.
Ways to integrate Bancontact
Payrails SDK
Server-to-server integration
Parse Bancontact from lookup response
Pass Bancontact payment method in request to authorize payment with Payrails
Note on amountsEUR uses 2 decimal places. Amounts should be provided in the smallest currency unit—for example,
2000 for €20.00.Bancontact is a redirect-based, single-use payment method. After calling the authorize endpoint, the customer will be redirected to their bank’s interface to authenticate and confirm the payment. Once confirmed, the customer will be redirected back to the
returnInfo.success URL. The refund period for Bancontact is up to 180 days after the original payment. There is no dispute process—customers authenticate directly with their bank.Handle the redirect response
Required meta fields
Bancontact requires the following fields to be present in every authorize request:Supported currencies
Bancontact via Stripe supports the following presentment currency:- EUR — Euro
Supported regions / countries
Customer regions
Bancontact is available to customers based in:- Belgium 🇧🇪
Merchant regions
Stripe accounts in the following countries and regions can accept Bancontact payments:- 🇪🇺 European Economic Area
- 🇦🇺 Australia
- 🇨🇦 Canada
- 🇭🇰 Hong Kong
- 🇯🇵 Japan
- 🇲🇽 Mexico
- 🇳🇿 New Zealand
- 🇸🇬 Singapore
- 🇺🇸 United States