Bancontact mobile Drop-in integration

Our Android Drop-in renders Bancontact in your payment form, and redirects the shopper to the Bancontact app to complete the payment.

Requirements

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:

• countryCode: BE.
• amount.currency: EUR.

Optional configuration

When you create the Bancontact configuration object, you can optionally add configuration parameters.

val bcmcConfiguration = BcmcConfiguration.Builder(context, "YOUR_CLIENT_KEY")
    // Makes the cardholder name required.
    .setHolderNameRequired(true)
    // When you are ready to accept live payments, change the value to one of our live environments.
    .setEnvironment(Environment.TEST)
    .build()

Make a payment

When the shopper proceeds to pay, Drop-in returns the paymentComponentData.paymentMethod.

1. Pass the paymentComponentData.paymentMethod to your server.

2. From your server, make a /payments request, specifying:

   • paymentMethod: The paymentComponentData.paymentMethod from 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 RedirectComponent.getReturnUrl(context).
   curlJavaPHPC#NodeJS (JavaScript)GoPythonRubyNodeJS (TypeScript)curlJavaPHPC#NodeJS (JavaScript)GoPythonRubyNodeJS (TypeScript)

   Expand view

   Copy link to code block

   Copy code

   Copy code

   curl https://checkout-test.adyen.com/checkout/v68/payments \
   -H 'x-api-key: ADYEN_API_KEY' \
   -H 'content-type: application/json' \
   -d '{
     "merchantAccount":"ADYEN_MERCHANT_ACCOUNT",
     "reference":"YOUR_ORDER_NUMBER",
     "amount":{
       "currency":"EUR",
       "value":1000
     },
     "paymentMethodpaymentComponentData.paymentMethod from app":{
       "type":"bcmc_mobile"
     },
     "returnUrl":"adyencheckout://your.package.name"
   }'

   The /payments response contains:

   • action: Object containing information about the redirect.
   /payments response

   Expand view

   Copy link to code block

   Copy code

   Copy code

   {
     "resultCode": "Pending",
     "action": {
        "paymentData": "Ab02b4c0!BQABAgCpM2q6...==",
        "paymentMethodType": "bcmc_mobile",
        "url": "https://checkoutshopper-test.adyen.com/checkoutshopper/checkoutPaymentRedirect?redirectData=...",
        "qrCodeData": "BEP://1bcmc-test.adyen.com/pal/bep$RYB4BPBNXDTVG3PLKTXV5OVE",
        "type": "qrCode"
     },
     "additionalData": {
        "bcmcmobile.urlIntent": "BEPGenApp://DoTx?TransId=1bcmc-test.adyen.com/pal/bep$P5..."
   }

3. Pass the action object 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 actionComponentData object.

From your server, make a POST /payments/details request providing:

• details: The actionComponentData.details object from Drop-in.

curl https://checkout-test.adyen.com/checkout/v68/payments/details \
-H 'x-api-key: ADYEN_API_KEY' \
-H 'content-type: application/json' \
-d '{
     "details": {
       "redirectResult": "eyJ0cmFuc1N0YXR1cyI6IlkifQ=="
   }
}'

You receive a response containing:

• resultCode: Use this to present the payment result to your shopper.
• pspReference: Our unique identifier for the transaction.

{
     "resultCode": "Authorised",
     "pspReference": "PPKFQ89R6QRXGN82"
}

Present the payment result

Use the  resultCode from the /payments/details response to present the payment result to your shopper. You will also receive the outcome of the payment asynchronously in a webhook.

For Bancontact payments, you can receive the following resultCode values:

Recurring payments

Bancontact supports tokenization for recurring payments.

You can use recurring transactions through the Bancontact Wallet Initiated Program (WIP) and SEPA Direct Debit.

Bancontact Wallet Initiated Program

The Bancontact Wallet Initiated Program (WIP) is a service that streamlines checkout and supports subscription-based billing. It offers the following:

• Bancontact One-Click Pay to speed up checkout and boost conversion rates
• Bancontact Recurring to support merchant-initiated recurring or subscription payments

You have to sign up to be able to use this service and not all companies are eligible to use Bancontact WIP. To enable Bancontact WIP, contact our Support Team.

When you enable Bancontact WIP, transaction amount limits apply to ensure controlled and secure payments.

Shoppers go through Strong Customer Authentication (SCA) one time when they complete their first transaction and give their consent. Subsequent transactions do not require SCA, which reduces friction and improves the checkout flow. Because the transaction goes through SCA, there is a liability shift.

Make a recurring payment

To make recurring payments, you need to:

1. Create a shopper token.
2. Use the token to make future payments for the shopper.

Create a token

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 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.

The following example shows a recurring Subscription payment using SEPA Direct Debit.

curl https://checkout-test.adyen.com/checkout/v68/payments \
-H 'x-api-key: ADYEN_API_KEY' \
-H 'content-type: application/json' \
-d '{
       "amount":{
          "value":1000,
          "currency":"EUR"
       },
       "paymentMethod":{
          "type":"sepadirectdebit",
          "recurringDetailReference":"7219687191761347"
       },
       "reference":"YOUR_ORDER_NUMBER",
       "merchantAccount":"YOUR_MERCHANT_ACCOUNT",
       "shopperReference":"YOUR_UNIQUE_SHOPPER_ID_IOfW3k9G2PvXFu2j",
       "shopperInteraction":"ContAuth",
       "recurringProcessingModel": "Subscription"
}'

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:

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.

See also