Bancontact card for API only

A Bancontact card payment is like a regular card payment, except for the following:

• There is no CVC. For co-badged cards, the CVC field can still appear.
• 3D Secure authentication is mandatory.
• Separate captures are not supported.

This page explains how to accept Bancontact card card payments with raw card data.

If you are not fully PCI compliant, use our Bancontact card Component for Web or Android instead.

Requirements

Build your payment form for Bancontact card

When making a Bancontact card payment, collect the following shopper details:

Card details	Example input	Required
Card number	"6703444444444449"
Card expiry month	"03"
Card expiry year	"30"
Cardholder name	"S.Hopper"

You can also get the required fields from the /paymentMethods response, as explained in our API-only integration guide. In your call, specify:

• countryCode: BE
• amount.currency: EUR.

The required input fields are included in the object with type: bcmc.

Make a payment

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

• paymentMethod.type: scheme.
• paymentMethod.brand: bcmc.
• paymentMethod.number: The card number (without separators).
• paymentMethod.expiryMonth: The card expiry month.
• paymentMethod.expiryYear: The card expiry year.
• paymentMethod.holderName: The name of the cardholder.
• browserInfo: The shopper's browser information.

  The browserInfo is required for web-based integration.

• returnURL: The URL where the shopper will be redirected back to after completing the 3D Secure authentication.

Sample /payments request for web-based implementation:

The /payments response contains an action object with type: redirect.

Handle the redirect

To complete the payment, redirect the shopper to perform 3D Secure authentication.
For more information and detailed instructions, refer to Handling redirects.

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

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

Add Bancontact card in your live Customer Area.

See also