Our Android Drop-in renders Bancontact in your payment form, and redirects the shopper to the Bancontact app to complete the payment.
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.
Show Bancontact in your payment form
Drop-in uses the
countryCode and the
amount.currency from the /paymentMethods request to show the available payment methods to your shopper.
To show Bancontact in your payment form, specify in your /paymentMethods request:
When you create the Bancontact configuration object, you can optionally add configuration parameters.
Make a payment
When the shopper proceeds to pay, Drop-in returns the
paymentComponentData.paymentMethodto your server.
From your server, make a /payments request, specifying:
paymentComponentData.paymentMethodfrom your client app.
returnURL: URL to where the shopper should be redirected back to after they complete the payment. Get this URL from the Component in the
The /payments response contains:
action: Object containing information about the redirect.
actionobject to your client app. Drop-in needs this to redirect the shopper to the Bancontact app.
Check the payment result
Drop-in redirects the shopper to complete the payment. When the shopper returns back to your app, Drop-in provides the
From your server, make a POST /payments/details request providing:
actionComponentData.detailsobject from Drop-in.
You receive a response containing:
resultCode: Use this to present the payment result to your shopper.
pspReference: Our unique identifier for the transaction.
Present the payment result
For Bancontact payments, you can receive the following
|resultCode||Description||Action to take|
|Authorised||The payment was successful.||Inform the shopper that the payment was successful.|
|Cancelled||The shopper cancelled the payment.||Ask the shopper whether they want to continue with the order, or ask them to select a different payment method.|
|Error||There was an error when the payment was being processed. For more information, check the
||Inform the shopper that there was an error processing their payment.|
|The payment order was successfully received.||Inform the shopper that you've received their order, and are waiting for the payment to clear.
You will receive the final result of the payment in an AUTHORISATION webhook.
|Refused||The payment was refused. For more information, check the
||Ask the shopper to try the payment again using a different payment method.|
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.