On this page, you can find additional configuration for adding Bancontact to your Components integration.
Our iOS Component renders Bancontact in your payment form, and redirects the shopper to the Bancontact app depending on how they are accessing your app:
- For shoppers on mobile, the shopper is switched to the Bancontact app. If this fails, the shopper is presented a QR code as a fallback.
- For shoppers on tablet, the shopper is presented with both a QR code and a button to switch to the Bancontact app.
Before you begin
This page assumes you have already:
You must also enable additional API response fields:
- In your Customer Area, go to Developers > Additional data.
- Under 3D Secure, select the checkbox for 3DS2 Additional Fields.
You don't need to send additional fields for Bancontact. To see optional fields that you can send for all payment methods, choose the endpoint you integrated:
- /sessions: This is the default with Components v5.0.0 or later.
- /payments: If you implemented an additional use case.
If your integration uses iOS Components v5.0.0 or later, configure and create an instance of the Bancontact Component:
//Create a payment method object for Bancontact. let paymentMethod = paymentMethods.paymentMethod(ofType: bcmc_mobileComponentPaymentMethod.self) //Create a configuration object for the Bancontact Component. var bcmc_mobileComponentConfiguration = bcmc_mobileComponent.Configuration() //Set additional parameters on the configuration object. bcmc_mobileComponentConfiguration.localizationParameters = //Optional custom localization parameters.
There is no required Bancontact-specific integration for Components.
Bancontact recurring payments are not available in the test environment. To test your integration, do a penny test in the live environment instead.
We support recurring transactions for Bancontact through SEPA Direct Debit. To make recurring payments, you need to:
Create a token
We strongly recommend that you request explicit permission from the shopper if you intend to make recurring SEPA payments. Being transparent about the payment schedule and the charged amount reduces the risk of chargebacks.
- shopperReference: Your unique identifier for the shopper (minimum length three characters).
When the payment has been settled, you receive a webhook containing:
pspReferenceof the initial payment.
pspReference: This is the token that you need to make recurring payments for this shopper.
Make sure that your server is able to receive RECURRING_CONTRACT as part of your standard webhooks. You can enable the RECURRING_CONTRACT event code in the webhook settings page.
Make a payment with a token
To make a payment with the token, include in your /payments request:
pspReferencefrom the RECURRING_CONTRACT. You can also get this value by using the /listRecurringDetails endpoint.
shopperReference: The unique shopper identifier that you specified when creating the token.
recurringProcessingModel: Subscription or UnscheduledCardOnFile.
For more information about the
recurringProcessingModel fields, refer to Recurring transaction types.
Test and go live
Bancontact does not have a test platform, but you can simulate authorized or declined payments.
To simulate authorized or declined payments, make a test payment using the following last three digits for the payment amount:
|Amount ending in||Description||Result|
|000||Simulates an approved transaction within fifteen seconds.||Authorised|
|123||Simulates a refused transaction within fifteen seconds.||Refused|
Any other scenarios must be tested in the live environment using real payment details and small amounts.
Before you can accept live payments, you need to submit a request for Bancontact in your live Customer Area.