Credit Card Customer Token
Tokenizing credit cards
Security considerations when Tokenizing credit cards
For traditional credit cards (eg. VISA, MasterCard, AMEX), you will want to provide some security information, in order to increase the chances of a successful transaction.
We support the following security methods:
3DS2
3DS1
MOTO
Depending on the specified security method, additional data will be required.
3DS2
cavv
The authenticationValue from your 3D Secure 2 provider
dsTransID
The unique transaction identifier assigned by the DS to identify a single transaction
eci
The electronic commerce indicator
3DS1
authenticationResponse
From the paResponse from the issuer access control system
directoryResponse
The enrollment response from the VERes message from the directory server
cavv
The authentication value for the 3D Secure authentication session. The returned value is a Base64-encoded 20-byte array
cavvAlgorithm
The CAVV Algorithm used during the authentication
xid
The transaction identifier assigned by directory server (base64 encoded, 20 bytes in a decoded form)
eci
The electronic commerce indicator
MOTO
This is a fallback method if no 3DS information is available.
Create a credit card customer token
Here is an example of a successful request for a credit card tokenisation, with 3DS1.
Create customer token using a credit card
POST https://staging.api.xpay.xcover.com/customer-tokens/credit-card
Headers
Authorization*
string
Bearer {{JWT}}
Failure Scenarios
There are many reasons why a tokenization of a credit card may fail. Here are some examples.
Missing Card Details
Card Declined
Invalid Credit Card Number
Last updated