Skip to content
Create account or Sign in
The Stripe Docs logo
/
Ask AI
Create accountSign in
Get started
Payments
Revenue
Platforms and marketplaces
Money management
Developer resources
APIs & SDKsHelp
Overview
About Stripe payments
Upgrade your integration
Payments analytics
Online payments
OverviewFind your use caseUse Managed Payments
Use Payment Links
Use a prebuilt checkout page
Build a custom integration with Elements
Build an in-app integration
Payment methods
Add payment methods
    Overview
    Payment method integration options
    Manage default payment methods in the Dashboard
    Payment method types
    Cards
      CITs and MITs
      How cards work
      Card Product Codes
      Cartes Bancaires
      eftpos Australia
      Co-badged cards compliance
      Installments
    Pay with Stripe balance
    Stablecoin payments
    Bank debits
    Bank redirects
    Bank transfers
    Credit transfers (Sources)
    Buy now, pay later
    Real-time payments
    Vouchers
    Wallets
    Enable local payment methods by country
    Custom payment methods
Manage payment methods
Faster checkout with Link
Payment interfaces
Payment Links
Checkout
Web Elements
In-app Payments
Payment scenarios
Handle multiple currencies
Custom payment flows
Flexible acquiring
Orchestration
In-person payments
Terminal
Beyond payments
Incorporate your company
Crypto
Agentic commerce
Financial Connections
Climate
Understand fraud
Radar fraud protection
Manage disputes
Verify identities
United States
English (United States)
HomePaymentsAdd payment methodsCards

Co-badged cards compliance

Learn about EU regulations requiring customer choice for co-badged cards.

Regulation (EU) 2015/751 requires businesses in the European Economic Area (EEA) to honor customers’ card brand choice for co-badged cards (for example, Cartes Bancaires cards co-badged with Visa). This means you must allow cardholders to select a preferred card brand on your payment page in accordance with these guidelines:

  • Display the available card networks on your online payment page or in-person checkout flow: All available card networks must be clearly identified during the checkout process. The visual quality, clarity, and size of the brand logos must be consistent, and it should be clear to cardholders how to select a card network.
  • Abide by the cardholder’s preferred card network: Where the cardholder chooses their preferred card network, you must use it when confirming a payment or storing card details for future use. If the cardholder doesn’t make a choice, you can choose your card network for the transaction.
  • Allow updates to the preferred card network: You must present cardholders updating their payment methods that are saved for future use with the option to change their preferred card network when they’re updating their payment details. For example, you can provide a customer portal for managing saved payment methods.

Does this regulation apply to me?

Regulation (EU) 2015/751 applies to all businesses in the EEA that can process Cartes Bancaires. Sign in and return to this section to view if co-badged card regulation applies to you.

When regulation applies

Regulation (EU) 2015/751 applies to the following businesses and Stripe-supported transaction types:

Payment channelSubject to card brand choice regulationTransaction types
OnlineBusinesses in the EEA that can process Cartes BancairesThe payment method is a co-badged Cartes Bancaires card, and the currency is EUR.
In-personBusinesses in France that can process Cartes BancairesThe payment method is a co-badged Cartes Bancaires card.
In-personBusinesses in Germany that can process GirocardThe payment method is a co-badged Girocard.

Applicable in:

Austria
Belgium
Bulgaria
Croatia
Cyprus
Czech Republic
Denmark
Estonia
Finland
France
Germany
Greece
Hungary
Iceland
Ireland
Italy
Latvia
Liechtenstein
Lithuania
Luxembourg
Malta
Netherlands
Norway
Poland
Portugal
Romania
Slovakia
Slovenia
Spain
Sweden

Integration guides

Stripe-hosted UIs, such as Checkout, Payment Links, Elements, and Stripe Terminal, automatically display a network selector when you meet the applicability criteria. You must configure these UIs according to the guides below.

For other integrations, you’re fully responsible for making sure your integration complies with the regulation requirements.

Sandbox environments

When using sandboxes, Cartes Bancaires is always enabled for online payments, which means you might see the network selector on Stripe-hosted UIs in a sandbox, even if you don’t enable Cartes Bancaires. This allows you to preview how Stripe-hosted UIs handle co-badged cards if Cartes Bancaires were enabled.

Stripe Checkout supports customer card brand choice, by default. Customers who enter a co-badged card in Checkout can select their option for card brand choice.

The card input with a co-badged card in Stripe Checkout

Card input with a co-badged card

Identify the processing network

The charge object associated with a successful payment contains a network field that indicates which card network processed the payment. For example, you can identify the network for a transaction using a card as follows:

{ "id": "ch_1Ff52K2eZvKYlo2CWe10i0s7", "object": "charge", ... "payment_method_details": { "card": { "brand": "visa", ... "network": "cartes_bancaires", }, "type": "card" } }

If you use a Terminal integration, review the specific regional requirements to identify the network used.

Testing

You can use the following co-badged cards to test your integration.

NumberBrandCVCDate
Cartes Bancaires or VisaAny 3 digitsAny future date
Cartes Bancaires or MastercardAny 3 digitsAny future date

If you use a Terminal integration, see the simulated test cards that you can use with a simulated reader to verify network routing.

Was this page helpful?
YesNo
  • Need help? Contact Support.
  • Check out our changelog.
  • Questions? Contact Sales.
  • LLM? Read llms.txt.
  • Powered by Markdoc