3D Secure Card Payments

Suggest Edits

3D Secure card payment data can be added to authorizations, purchases, and refunds. All fields should be included under the extra key in the request payload.

The values for sli, xid, cavv, par and ver should be supplied by the 3D Secure MPI being used for transaction authentication.

If you do not have an MPI, Fat Zebra can provide an MPI. Refer to the 3DS2 Integration documentation for more information.

Field name	Type	Description
sli	String (2-digits)	The Security Level Indicator (SLI) indicates the type of card holder authentication used for the transaction. Accepted values are described in the table bellow.
xid	String	The XID is the transaction ID from the 3D Secure provider. This is Base64 encoded data.
cavv	String	The CAVV is the card authentication verification value, provided by the 3D Secure Provider. This is Base64 encoded data.
par	String	This is the `PARes` value from 3D Secure
ver	String	This is the `VERes` value from 3D Secure
threeds_version	String	3DS version used for authenticating the card. The version may include the major, minor, and build numbers, e.g. `2`, `2.1`, or `2.1.0` are all accepted values. If omitted, this field will default to a value of `1`.
directory_server_txn_id	String	Directory Server Transaction ID from the 3D Secure provider. This is commonly a string in UUID format.

"sli" accepted values	Description
"05"	Secure, Authenticated transaction with XID and CAVV present
"06"	Secure, Non-authenticated transaction (XID present, CAVV not present)
"07"	Secure, Non-authenticated transaction (XID and CAVV not present). This is the default value.

Note: All fields should be included under the extra key in the request payload.

{
    "extra": {
        "sli": "05",
        "cavv": "MzM2OGI2ZjkwYjYwY2FjODQ3ZWU=",
        "xid": "ZGUzNzgwYzQxM2ZlMWM0MzVkMjc=",
        "par": "Y",
        "ver": "Y",
        "directory_server_txn_id": "5ddb4c13-2e30-4901-9854-5f0305097a25",
        "threeds_version": "2.1.0"
    }
}

Updated about 2 years ago