In early 2021, one of Belgium's major banks started issuing new debit cards that are co-badged with Bancontact and Visa Debit, replacing the existing Maestro scheme. As of mid-August 2021 there are 1 million of these cards in circulation, and the expectation is that this will grow to 4 million by the beginning of 2022.
We have seen issues processing these co-badged cards with some older Adyen integrations. Here we describe the issues, when they can occur, and how you can avoid being impacted.
If you have further questions after reading the information on this page, reach out to your Adyen contact.
Which transactions are impacted?
When shoppers pay with a Bancontact card, they can choose Credit card, Payconiq by Bancontact, or Bancontact card.
-
Credit card : Bancontact cards can also be accepted as a generic credit or debit card.
We have seen no issues with this flow. -
Payconiq by Bancontact: Sometimes referred to as Bancontact mobile.
We have seen no issues with this flow. -
Bancontact card: This is the regular Bancontact card flow that requires 3D Secure.
This is the flow where we have seen issues processing the new co-badged cards in some older Adyen integrations..
What issues can occur?
When you are using a Classic SDK integration or an older Drop-in or Components integration, your shoppers may experience the following issues when they try to make a Bancontact card payment using the new co-badged card.
Can't enter card details
In some cases, shoppers are unable to enter their card details, and they see an "invalid card" message. Both you and Adyen won't know this happened because the error occurs on the front end and the payment never starts.
Routing issues
For co-badged cards shoppers should be able to select which scheme to use for the payment. In some cases shoppers don't get this option and a default scheme is chosen.
Is my integration affected?
To find out whether your integration is affected by the Bancontact card processing issues, refer to the integration-specific advice below.
API-only
If you are using our API-only integration you may experience issues processing the new co-badged Bancontact cards.
To check whether your integration is impacted, make a test transaction using the special test card.
Classic Checkout SDKs
If you are using a Classic Checkout SDK integration (for Web, iOS, or Android) you may experience issues processing the new co-badged Bancontact cards.
We recommend migrating to the latest version of Drop-in. Read our migration guide for information on how to do this.
Classic API integration
If you are using the old Classic API integration you may experience issues processing the new co-badged Bancontact cards.
To check whether your integration is impacted, make a test transaction using the special test card.
Classic Hosted Payment Pages (HPP) integration
We have seen no issues with Bancontact transactions for Classic HPP integrations.
Drop-in
Drop-in for Web integrations on a version lower than 4.2.0 may experience issues when processing the new co-badged Bancontact cards.
We recommend updating to the latest version of Drop-in for Web. To use the latest version of Drop-in, you also need to update to the latest version of the Checkout API.
We have observed no issues processing the new co-badged cards with more recent versions of Drop-in for Web, nor with the Drop-in for iOS and Drop-in for Android integrations.
Components
Components for Web integrations on a version lower than 4.2.0 may experience issues when processing the new co-badged Bancontact cards.
We recommend updating to the latest version of Components for Web. To use the latest version of Components, you also need to update to the latest version of the Checkout API.
We have observed no issues processing the new co-badged cards with more recent versions of Components, nor with the Components for iOS and Components for Android integrations.
Pay by Link
We have seen no issues with Bancontact transactions for Pay by Link.
In-person payments
We have seen no issues with Bancontact transactions for in-person payments integrations.
Test your Bancontact integration
To check whether your integration is impacted by issues with Bancontact card payments with the new co-badged cards, make a test payment using the following test card.
Make this transaction in your TEST environment. This card will not work in a LIVE environment.
| Test card number | CVV2/CVC2 | Username | Password | Issuing country | Expiry date |
|---|---|---|---|---|---|
| 4871 0499 9999 9910 | Bancontact: None Visa: 737 |
user | password | BE | 03/2030 |
If a test transaction with these card details is successful, then you are not impacted. If the test transaction fails, reach out to your Adyen contact for more information.