Card processing overview
Mangopay offers a range of card payment features and integration options.
Brands and currencies
Mangopay supports the following card brands and currencies, defined by the CardType parameter.
| Brand | CardType | Currencies |
|---|---|---|
| Mastercard International | CB_VISA_MASTERCARD | See the currencies page for details |
| Visa International | ||
| CB France | ||
| AMEX International | AMEX | See the currencies page for details |
| Maestro International | MAESTRO | EUR |
| Bancontact Belgium | BCMC | EUR |
Card registration
Processing card payments with Mangopay involves passing sensitive card details to a dedicated tokenization server to generate a CardId.
Initiate card tokenization
Call the POST Create a Card Registration endpoint to initiate the flow and obtain a secure URL to which you can send card details.
Tokenize the card
Send the cardholder’s sensitive data directly to the tokenization server, without passing yours or Mangopay’s, thanks to the POST Tokenize the card endpoint.
Update the card registration object
Send the RegistrationData received from the tokenization server via PUT Update a Card Registration to generate a CardId.
Use the card object for a payment flow
Use the CardId to call the Mangopay API to initiate a one-time, recurring, or preauthorized card payment flow.
Deactivate the card
Deactivate the card if you don’t have the user’s permission to save their payment details. You can follow the same tokenization process for a future payment.
This process involves two distinct API objects:
- Card Registration - The object to safely tokenize the card and create the Card object.
- Card - The tokenized version of the card, whose
CardIdwill allow you to make payments.
For more detailed guidance, see the how-to guide for one-time payments.
Best practice – Use Checkout SDK
The Mangopay Checkout SDK takes care of card tokenization for you, and simplifies your integration for cards and other payment methods.
Learn more →Payment flows
Once the card is tokenized, a number of payment flows are available depending on the CardType.
One-time card payment
Allow a user to pay once, and save their card details for future payments if you have permission.
Availability:
- All card types
Direct card pay-in
Process a one-time card payment with a registered card
Validation without debit
Check the validity of a card, including 3DS authentication, without requesting payment.
Availability:
CB_VISA_MASTERCARDonly
Card validation
Validate a card without debiting it
Recurring card payments
Set up a subscription, installments, or other recurring card transactions.
Availability:
CB_VISA_MASTERCARDonly
Recurring card payments
Set up and process subscriptions and installment payments
7-day preauthorization
Authorize and reserve funds on a card to be captured later, at one time or in multiple captures.
Availability:
CB_VISA_MASTERCARD– Partial and multiple capturesAMEX– Single capture only (partial but not multiple)MAESTRO– Full capture only (not partial or multiple)
Preauthorization (7 days)
Secure funds for 6.5 days and charge the card with one or multiple captures
30-day preauthorization
Authorize and reserve funds on a card to be captured later, including a complement in addition to the preauthorized amount.
Availability:
CB_VISA_MASTERCARDonly
Deposit preauthorization (30 days)
Secure funds for 29.5 days and capture the preauthorized amount and/or a complement
3DS
Redirection for cardholder authentication, using the 3DS protocol, is applicable to all card payment flows.
Refunds
Refunds are supported on all card brands and for all pay-in flows. For more information, see the Refunds guide.
Chargebacks and disputes
All card pay-ins may be subject to a chargeback, which is when the end user opposes a payment with their issuing bank. When a chargeback occurs, a dispute is created which may be contestable. For more information, see the Disputes guide.
Related resources
Was this page helpful?