Bancontact mobile Redirect Component

Use our Redirect Component to handle the redirect to the Bancontact app. When adding Bancontact to your existing Components integration, you also need to:

1. Show Bancontact in your payment form.
2. Handle the redirect result when the shopper returns to your app.

Requirements

Show Bancontact in your payment form

Include Bancontact in the list of available payment methods. You do not need to collect any information from the shopper in your payment form.

1. Specify in your /paymentMethods request:

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

The response contains paymentMethod.type: bcmc_mobile.

Optional configuration

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

Make a payment

1. When the shopper selects the button to pay, make a /payments request, specifying:

   • paymentMethod.type: bcmc_mobile
   • returnURL: The 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).

   The /payments response contains:

   • action: Object containing information about the redirect.

2. Pass the action object to your client app. You need this to initialize the Redirect Component.

Handle the redirect

Use the QRCodeComponent to redirect the shopper to the Bancontact app:

Step 1: Initialize the QR Code Component

1. Before initializing the Component, make sure that you have added the following to your build.gradle file:

   Check the latest version on GitHub.

2. Create a configuration object for the Component, passing your client key:

3. To initialize an instance of the Component, call PROVIDER.get from the Component and pass in the context (for example, this@YourActivity), application class, and the configuration object created in the previous step:

4. From your instance, call handleAction and pass:

   • the context (for example, this@YourActivity)
   • the action object from the deserialized /payments response.

Step 2: Handle the redirect

1. Add an IntentFilter to the Activity that will handle the returnUrl specified in your /payments request.

   The ${applicationId} will be replaced with your.package.name at build time.

2. Get the result of the redirect from the Activity. Pass the intent back to the Component. Depending on your activity's launchMode, you can get this intent in either onCreate or onNewIntent.

3. The Component notifies the observer with the actionComponentData object from the data in intent.data. Pass this to your server.

Step 3: Check the payment result

After the shopper returns to your app, make a POST /payments/details request from your server, providing:

• details: The actionComponentData.details object from the from the QRCodeComponent

  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

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

We support recurring transactions for Bancontact through SEPA Direct Debit. 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.

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