Bancontact card Component integration

This page explains how to add Bancontact card to your existing Android Components integration.

Requirements

Select the server-side flow that your integration uses:

API reference

Bancontact card Configuration

Recurring payments

Bancontact supports tokenization for recurring payments.

You can use recurring transactions through the Bancontact Wallet Initiated Program (WIP).

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 first transaction goes through SCA, there is no liability shift. The issuer remains liable.

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.

To test recurring payments, contact our Support Team to configure your test environment.

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 recurring.token.created webhook containing:

• type: recurring.token.created
• shopperReference: your unique identifier for the shopper.
• eventId: The pspReference of the initial payment.
• storedPaymentMethodId: 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 storedPaymentMethodId from the recurring.token.created webhook. 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 WIP.

Test and go live

Before making live payments, use the following credentials to test your integration:

¹ Depending on your payment method setup, transactions with this test card are routed to Bancontact or Visa.

You can force a decline using these credentials with "holderName": "DECLINED".

    "paymentMethod": {
      "type": "bcmc",
      "number": "4871049999999910",
      "holderName": "DECLINED",
      "expiryMonth": "03",
      "expiryYear": "2030"
    }

This gets the following response:

    "refusalReason": "Refused",
    "resultCode": "Refused",

You can check the status of test payments in your Customer Area > Payments > Payment list.

Add Bancontact card in your live Customer Area.

See also