Docschargebeedocs

HomeBillingPaymentsRevRecGrowth
Support

Product Updates

  • Release Notes

Payment Methods

  • Payment Methods Overview
  • Cards
  • Direct Debit
  • Bank Based Payments
  • Wallets
  • Vouchers
  • Articles and FAQ

Payment Gateways and Configuration

  • Payment Gateways Overview
  • Chargebee Test Gateway
  • Chargebee Pay
  • Stripe
  • Adyen
  • Braintree
  • Authorize.net
  • PayPal Payment Services
  • GoCardless
  • Razorpay
  • Checkout.com
  • Mollie
  • BlueSnap
  • CyberSource
  • Global Payments
  • QuickBooks Payments
  • Worldline Online Payments(formerly Ingenico)
  • Worldpay
  • J.P. Morgan Mobility Payment Solutions
  • Twikey
  • dLocal
  • Bank of America
  • Solidgate
  • Pay.com
  • EBANX
  • BluePay
  • Sage Pay
  • Paymill
  • Bambora (formerly Beanstream)
  • E-xact Direct Integration
  • Orbital (Chase Paymentech)
  • Pin Payments
  • Moneris
  • Elavon
  • Network Merchants Incorporated (NMI)
  • eWay Rapid
  • Ecentric
  • Windcave
  • Metrics Global
  • Nuvei
  • Paystack
  • Articles and FAQ

Level 2/3 Data Support

  • Level 2/3 Data Support

Advanced Routing

  • Advanced Routing

Dunning

  • Dunning
  • Articles and FAQ

Offline Checkout

  • Offline Checkout
  • Articles and FAQ

Transaction Sync & Invoice Mapping

  • Transaction Sync and Invoice Mapping

Fraud Management

  • Fraud Management

Error Handling

  • Errors with Root Cause and Troubleshooting

Payment Lifecycle Logs

  • Payment Intents
  • Transactions
  • Gateway Activity Logs
  • Articles and FAQ

Others

  • Reach (Merchant of Record)
  • Payment Verification
  • Bulk Deletion of Payment Methods
  • Custom Payment Methods
  • Payment Initiator Parameter
  • PSD2 and Strong Customer Authentication
  • RBI e-Mandate
  • RBI Tokenization Regulations
  • Chargeback Management
  • Transaction Descriptors
  • Payment Preferences
  • Visa Trial Rules
  • Mastercard Trial Rules
  • Co-badged Card Compliance
  • Articles and FAQ
  1. Payments
  2. Others
  3. Co-badged Card Compliance
  1. Payments
  2. Others
  3. Co-badged Card Compliance

Co-badged Card Compliance

Co-badged cards are payment cards that carry logos and functions of two or more payment networks. This means a single card can be used with multiple payment schemes, typically providing the cardholder with more flexibility in how and where they make payments.

For example, a co-badged card might feature both Visa and Mastercard along with a local payment network logo, such as Cartes Bancaires (France's domestic network) or Dankort (Denmark's local network).

Chargebee currently supports Cartes Bancaires with Stripe as part of co-badged card compliance. Learn more

Benefits of co-badged cards

The following are benefits of using co-badged cards:

  • Wider acceptance: Cardholders can use the same card for both domestic (via local card scheme) and international (via Visa/Mastercard) transactions, which may increase acceptance in both domestic and international transactions.
  • Lower fees for domestic use: Transactions routed through local card schemes may generally have lower fees.

Regulation

Regulation 2015/751 of the European Payments Initiative (EPI) requires that cardholders using co-badged cards must be clearly informed of their payment scheme options if the service supports multiple schemes.

The regulation focuses on these key principles:

  • Identify payment schemes: Clearly display the available payment schemes (for example, Visa, Mastercard) with consistent logos and sizes.
  • Honor cardholder's choice: You can set a default payment scheme, but if the cardholder selects a specific scheme, you must route the payment through that chosen scheme.

Applicability

  • Display of accepted payment schemes: Merchants must clearly indicate the payment schemes (for example, Cartes Bancaires, Visa, or Mastercard) they accept before initiating a transaction.
    image
  • Automatic selection of default scheme: For co-badged cards, if a merchant supports only one payment scheme, the payment page should automatically select that scheme. However, the customer must still be notified of this selection and their available options.
  • Limited requirement: According to Article 10 of Regulation 2015/751, merchants are only required to default to the supported scheme if they do not accept both schemes on a co-badged card. While merchants are not required to adopt additional payment brands, they must provide a choice to customers when both schemes are supported.

Was this article helpful?