Overview
User management
- Users
- User regulatory status
- User e-money
User verification
- User data format
- KYC documents
- UBO declarations
Wallets
- User wallets
- Client wallets
Cards
- Card registrations
- Cards
- Metadata
- Card validations
Card pay-ins
- Direct card pay-ins
- Recurring card pay-ins
- Preauthorizations
- Deposit preauthorizations
- Web card pay-ins
Banking pay-ins
- Bank wires
- Virtual IBAN
- Direct debits
- Web direct debits
APM pay-ins
- Apple Pay
- Bancontact
- BLIK
- Giropay
- Google Pay
- iDEAL
- Klarna
- MB WAY
- Multibanco
- Payconiq
- PayPal
- Satispay
Transfers
- Transfers
Refunds
- Refunds
Disputes
- Disputes
- Dispute documents
- Repudiations
- Dispute settlement
Payouts
- Bank accounts
- Payouts
FX conversions
- Conversion rates
- Quotes
- Conversions
Transactions
- Transactions
Helpers
- API responses
- Country authorizations
- Webhooks
- Events
- Reports
Platform account
- Client
- Dashboard permissions
View a Card Validation
Path parameters
The unique identifier of the Card object, obtained during the card registration process.
The unique identifier of the Card Validation object.
Responses
The unique identifier of the object.
The unique identifier of the user at the source of the transaction.
Returned values: CREATED
, SUCCEEDED
, FAILED
The status of the transaction.
Max. length: 255 characters
The URL to which users are automatically returned after 3DS2 if it is triggered (i.e., if the SecureModeNeeded
parameter is set to true
).
Max. length: 255 characters
The URL to which to redirect the user to proceed to 3DS2 validation.
Whether or not the SecureMode
was used.
The IP address of the end user initiating the transaction, in IPV4 or IPV6 format.
Information about the browser used by the end user (author) to perform the payment.
The exact content of the HTTP accept headers as sent to the platform from the end user’s browser.
Whether or not the end user’s browser has the ability to execute Java.
Max. length: 6 characters
The browser language, made up of the language code and the country (e.g., “en-US”).
The value representing the depth of the screen’s color palette for displaying images, in bits per pixel.
Max. length: 6 characters
The height of the screen in pixels.
Max. length: 6 characters
The width of the screen in pixels.
The difference in minutes between the browser’s timezone and UTC.
Max. length: 255 characters
The exact content of the HTTP User-Agent header.
Whether or not the end user’s browser has the ability to execute JavaScript.
Returned values: VISA
, MASTERCARD
, CB
, MAESTRO
The card network to use, as chosen by the cardholder, in case of co-branded card products.
Default value: DEFAULT
Allowed values: DEFAULT, FORCE, NO_CHOICE
The mode applied for the 3DS protocol for CB, Visa, and Mastercard. The options are:
DEFAULT
– Requests an exemption to strong customer authentication (SCA), and thus a frictionless payment experience, if allowed by your Mangopay contract and accepted by the issuer.FORCE
– Requests SCA.NO_CHOICE
– Leaves the choice to the issuer whether to allow for a frictionless payment experience or to enforce SCA.
Note: Sending the FORCE value automatically sets the ValidationUsage value to MIT.
Default value: MIT
Allowed values: MIT, CIT
Indicates the intended usage of the card:
- CIT – For customer-initiated transactions (CITs), meaning 3DS is less likely to be required on the card validation.
- MIT – For merchant-initiated transactions (MITs), meaning 3DS is more likely to be required on the card validation.
Note: The MIT value is returned automatically if the SecureMode value is FORCE, even if CIT is sent.
Returned values: UNKNOWN
, VALID
, INVALID
Whether the card is valid or not.
UNKNOWN
– No payment or card validation has been processed, so the validity of the card remains unknown.VALID
– The first payment or card validation using the card was processed successfully within 24 hours of the initial card registration.INVALID
– The first payment or card validation using the card was attempted and failed, or the status of the corresponding card registration wasCREATED
for more than 24 hours.
Once a card is set toINVALID
, it cannot be set back toVALID
. A new card registration will be necessary to make a payment.
The date and time at which the object was created.
Returned values: CARD_VALIDATION
The type of the card validation.
Returned values: V1
, V2_1
The 3DS protocol version applied to the transaction.
The code indicating the result of the operation. This information is mostly used to handle errors or for filtering purposes.
The explanation of the result code.
Max. length: 255 characters
Custom data that you can add to this object.
For transactions (pay-in, transfer, payout), you can use this parameter to identify corresponding information regarding the user, transaction, or payment methods on your platform.
Information about the card used for the transaction.
If the information or data is not available, null
is returned.
The 6-digit bank identification number (BIN) of the card issuer.
The name of the card issuer.
Format: ISO 3166-1 alpha-2 two-letter country code
The country where the card was issued.
Returned values: DEBIT
, CREDIT
, CHARGE CARD
.
The type of card product.
The card brand. Examples include: AMERICAN EXPRESS
, DISCOVER
, JCB
, MASTERCARD
, VISA
, etc.
Note: The possible returned values are numerous and liable to evolve over time.
The subtype of the card product. Examples include: CLASSIC
, GOLD
, PLATINUM
, PREPAID
, etc.
Note: The possible returned values are numerous and liable to evolve over time.
Was this page helpful?