---
title: "Co-badged cards compliance"
description: "Find out the requirements for your integration to be compliant with co-badged card regulations."
url: "https://docs.adyen.com/online-payments/co-badged-cards-compliance"
source_url: "https://docs.adyen.com/online-payments/co-badged-cards-compliance.md"
canonical: "https://docs.adyen.com/online-payments/co-badged-cards-compliance"
last_modified: "2025-07-25T10:37:00+02:00"
language: "en"
---

# Co-badged cards compliance

Find out the requirements for your integration to be compliant with co-badged card regulations.

[View source](/online-payments/co-badged-cards-compliance.md)

Some regions require additional configuration to be compliant with regulations for co-badged cards. To make sure your integration is compliant with the latest regulations, we recommend you always upgrade to the latest version available.

## Requirements for integration

Use the table below to find the minimum requirement for your integration to be compliant with co-badged card regulations:

| Integration type                                                                                                                              | Requirement                                                                                                                                                              |
| --------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| [Checkout API-only](/online-payments/build-your-integration/advanced-flow/?platform=Web\&integration=API%20only\&version=71)                  | Find out [how to identify card brands](/payment-methods/cards/raw-card-data#co-badged) so you can make your front end integration compliant with the regulations.        |
| [Custom card integration with encryption](/payment-methods/cards/custom-card-integration)                                                     | Find out how to [make your integration compliant](/payment-methods/cards/custom-card-integration#showing-co-badged-cards).                                               |
| [Web Drop-in or Components](/online-payments/build-your-integration/sessions-flow?platform=Web\&integration=Components)                       | Use [v6.21.0](https://github.com/Adyen/adyen-web/releases/tag/v6.21.0) or later.                                                                                         |
| [iOS Drop-in or Components](/online-payments/ios)                                                                                             | Use [v5.19.1](https://github.com/Adyen/adyen-ios/releases/tag/5.19.1) or later.                                                                                          |
| [Android Drop-in or Components](/online-payments/android)                                                                                     | Use [v5.13.0](https://github.com/Adyen/adyen-android/releases/tag/5.13.0) or later.                                                                                      |
| [React Native Drop-in or Components](/online-payments/react-native)                                                                           | Use [v2.7.0](https://github.com/Adyen/adyen-react-native/releases/tag/2.7.0) or later.                                                                                   |
| [Flutter Drop-in or Components](/online-payments/build-your-integration/sessions-flow/?platform=Flutter\&integration=Drop-in\&version=latest) | Use [v1.5.0](https://github.com/Adyen/adyen-flutter/releases/tag/v1.5.0) or later.                                                                                       |
| [Salesforce Commerce Cloud SFRA cartridge](/plugins/salesforce-commerce-cloud/sfra/)                                                          | Use [v25.5.0](https://github.com/Adyen/adyen-salesforce-commerce-cloud/releases/tag/25.5.0) or later.                                                                    |
| [Adobe Commerce plugin](/plugins/adobe-commerce/)                                                                                             | Use [v10.2.0](https://github.com/Adyen/adyen-magento2/releases/tag/v10.2.0) or later.                                                                                    |
| [Classic API-only](/online-payments/classic-integrations/classic-api-integration)                                                             | Make sure that your integration satisfies the [regulation requirements](/online-payments/classic-integrations/classic-api-integration#requirements-for-co-badged-cards). |

If you are using our Drop-in or Components with one of the versions listed above with Checkout API v71, your integration is compliant out-of-the-box. If you use an earlier version of the Checkout API, you can [make your integration compliant](#do-not-discriminate-between-card-products) by adding additional front-end configuration.

## Regulations

### Tab: European Economic Area

The [EU IFR Regulation 2015/751 article 8](https://eur-lex.europa.eu/eli/reg/2015/751/oj) for co-badged cards issued in the European Economic Area (EEA) requires that if a cardholder uses a co-badged card, and you support both brands, you must let them choose the brand to pay with.

### Guidelines

To make sure you are compliant with the scheme requirements, follow these guidelines:

#### Clearly identify payment schemes

When a cardholder enters their card number during checkout, identify the available payment schemes clearly by name and/or logo, for example, Visa, Mastercard, Cartes Bancaires, Bancontact, or Dankort. These need to have the same visual quality, clarity, and size. It must be clear to the cardholder that they can select their preferred card brand, and how to make that selection, for example, by using a checkbox or a radio button.

#### Do not discriminate between card products

If you accept both credit and debit cards, to be compliant, your checkout must have a cards section that refers to both debit and credit cards. You cannot present only a credit card section. The following are examples of compliant labels for the card payments section in your checkout form:

* **Cards**
* **Card payment**

If you offer Mastercard, there are additional requirements, and you must use the label **Card brand selection (optional)**.

If you accept Cartes Bancaires, Bancontact, or Dankort, you are accepting debit cards as these are debit offerings.

If you use a Drop-in or Components [version that meets the minimum requirement](#requirements-for-integration) with [Checkout API v71](/online-payments/release-notes/?integration_type=api\&version%5B0%5D=71), your integration is compliant with this guideline.

If you use an earlier version of Checkout API, you can change the name of the payment method in your checkout form. How you do this depends on your integration. For example, for Web Drop-in integrations, you need to add the [`name` configuration object](/payment-methods/cards/web-drop-in/#optional-configuration).

#### Honor the cardholder's choice

If the cardholder selects a brand to pay with, you must honor that choice, and it is not allowed to route the payment to another payment scheme.

#### Preselect a scheme for cardholders that do not make a choice

If the cardholder does not make a choice, you can choose your preferred scheme over which to route the payment. For these cases, preselect a card scheme that will be used when no choice is made. Card schemes require to be clear to your shoppers about which brand the payment will be routed to, even if the shopper does not make a selection.

### Guidelines for stored co-badged cards

When a shopper makes the first transaction to store their co-badged card details, let them choose a scheme to pay with, and inform them that the recurring payments will be processed by the scheme that they choose. These are the possible options:

* If the shopper chooses a scheme, you must store and honor the shopper's choice, and use that scheme for the recurring transactions.
* If the shopper does not make a choice, you can choose a scheme. For these cases, you can preselect a card scheme to show your shoppers which scheme will be used to process the recurring transactions.

### Tab: Australia

The [Reserve Bank of Australia (RBA) regulations](https://www.rba.gov.au/payments-and-infrastructure/review-of-retail-payments-regulation/conclusions-paper-202110/dual-network-debit-cards-and-least-cost-routing.html#box-d) for co-badged cards require you to do the following:

### Honor the cardholder's choice

You can decide if you want to let the cardholder choose which network their transaction will be processed through. If you let the cardholder choose a network, you must process the transaction with the network they choose.

### Inform the shopper that network routing can occur

If the shopper doesn't choose a network, you must reasonably indicate that the transaction can be processed through either network. For example, you can include text that says, "If you use a debit card with two networks, your payment can be processed through either network.”.

### Show the shopper which networks their transaction can be processed through

If you do not let the shopper choose a network, you must inform them of the networks their transaction can be processed through. You must show the logos of all of these network options.
