No momento, esta página não está disponível em português

Bancontact mobile Drop-in integration

Add Bancontact mobile to an existing Drop-in integration.

This page explains how to add Bancontact mobile to your existing Web Drop-in integration.

Our Web Drop-in renders Bancontact mobile in your payment form, and redirects the shopper to the Bancontact mobile app depending on how they are accessing your site:

For shoppers on desktop or laptop, the shopper is presented a QR code.
For shoppers on mobile, the shopper is switched to the Bancontact mobile 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 mobile app.

Requirements

Requirement	Description
Integration type	Make sure that you have an existing Web Drop-in integration.
Setup steps	Before you begin: Add Bancontact mobile in your test Customer Area. To receive the `bcmcmobile.urlIntent` parameter in the payment response: In your Customer Area, go to Developers > Additional data. Under 3D Secure select the checkbox for 3DS2 Additional Fields.

API reference

You do not need to send additional fields for Bancontact mobile. To see optional fields that you can send for all payment methods, choose the endpoint you integrated:

/sessions: This is the default with Drop-in v5.0.0 or later.
/payments: If you implemented an additional use case.

Drop-in configuration

There are no configuration steps specific to Bancontact mobile required for Drop-in.

Recurring

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 shopper token.
Use the token to make future payments for the shopper.

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.

To create a token, include in your /sessions or /payments request:

storePaymentMethod: true
shopperReference: Your unique identifier for the shopper (minimum length three characters).

When the payment has been settled, you receive a webhook containing:

eventCode: RECURRING_CONTRACT
originalReference: The pspReference of 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:

paymentMethod.storedPaymentMethodId: The pspReference from 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.
shopperInteraction: ContAuth.
recurringProcessingModel: Subscription or UnscheduledCardOnFile.

For more information about the shopperInteraction and recurringProcessingModel fields, refer to Tokenization.

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.