Co-branded cards
In certain regions and countries, regulations require that cardholders be given the choice of the card brand (e.g. Visa, CB) that they wish to use when paying with a co-branded card.
This feature can be allow users to collect rewards, for example, tied to a specific scheme. It can also lead to reduced processing costs.
To support co-branded cards, your platform needs to obtain the choice of card brand from the user at the moment they authorize the transaction, and pass this choice on to Mangopay when you make the pay-in API request.
Best practice – Integrate via Checkout SDK
The Checkout SDK identifies and presents co-branded cards to the user at payment, meaning you only have to pass this information on to Mangopay in the pay-in call.
How to support co-branded cards
Your platform can manage co-branded cards as follows:
Register the card
Tokenize the user’s card as described in the card registration guide.
Obtain the card BIN from the Card object
Call the GET View a Card endpoint to obtain the Card’s Alias
. The first six digits are the card’s .
Look up the BIN to see if it's a co-branded card
Call the POST Look up metadata for a payment method with the card BIN.
In the API response, if the card is co-branded then two BinData
object parameters are returned. For example:
If co-branded, present the choice to the user
In the example above, the user needs to be able to choose between CB and VISA.
Send the user's choice in the pay-in
Once the user has indicated their choice, send the value in the PreferredCardNetwork
parameter in the transaction API call. This allows Mangopay to ensure the correct network is used to request the payment.
The PreferredCardNetwork
parameter has the allowed values VISA
, MASTERCARD
, CB
, MAESTRO
.
The parameter is available on the following endpoints:
Related resources
Was this page helpful?