Co-badged cards feature multiple card schemes on the same physical card. This allows cardholders the flexibility to use a different card scheme, depending on where the card is being used.
For example, a co-badged card can feature an international card scheme like Mastercard or Visa alongside a domestic card scheme like Cartes Bancaires.
For co-badged cards, authentication and authorisation must be performed using the same card scheme. Ravelin’s 3DS Server provides you the ability to select the card scheme that will be used for authentication.
Our version response contains a list of card ranges where each card range is for different a card scheme that can be used to authenticate the cardholder. You can select the appropriate card scheme and the associated details like the supported version and method URL depending on your use case.
If you know the card scheme that will be used for authentication prior to making the version request, you can specify it in the request and we will return the version recommendation and other associated fields for that card scheme. Our default version recommendation will use the international card scheme for co-badged cards.
You can specify the card scheme, from the ones returned in the Version Response card ranges, in the Authenticate Request that you would like to use for authentication.
For co-badged cards, if you need the authentication to be routed to the domestic card scheme’s director server (e.g. Cartes Bancaires) you must specify the card scheme in the Authenticate Request. By default the authentication will be routed to the international card scheme’s directory server.
In most cases, there is a requirement to ensure that the directory server used in the authentication flow matches the card scheme used in the authorisation. Please talk to your payment partners to understand individual card scheme requirements.
Was this page helpful?