These docs are for v1.0.1. Click to read the latest docs for v2.1.0.

New data

3D Secure 2 requires 10 times more data fields than 3D Secure 1. This data is classified into three main buckets: Device Information, Browser Information and Merchant Risk Information (consists of cardholder account information, specific purchase information, prior transaction authentication information, merchant cardholder account authentication information).
The submitted data allows issuers to run transaction based risk analysis. Hence, the more data a merchant provides, the better are the chances for a frictionless flow to be applied during the payment.

The data elements are divided into "required", "conditional" and "optional" fields.

Required fields

📘

We take care of all the required fields

There is nothing to be done here.

Conditional and optional fields

Find below some examples of the new conditional and optional data fields:

  • Cardholder Account Information
  • Cardholder Account Number
  • Cardholder Account Identifier
  • Cardholder Billing Address City
  • Cardholder Billing Address Country
  • Cardholder Billing Address Line 1
  • Cardholder Billing Address Line 2
  • Cardholder Billing Address Line 3
  • Cardholder Billing Address Postal Code
  • Cardholder Billing Address State
  • Cardholder Email Address
  • Cardholder Home Phone Number
  • Cardholder Mobile Phone Number
  • Cardholder Name
  • Cardholder Shipping Address City
  • Cardholder Shipping Address Country
  • Cardholder Shipping Address Line 1
  • Cardholder Shipping Address Line 2
  • Cardholder Shipping Address Line 3
  • Cardholder Shipping Address Postal Code
  • Cardholder Shipping Address State
  • Cardholder Work Phone Number

🚧

Submitting optional and conditional parameters

Please get in contact with us if you need to submit 3D Secure 2.0 optional and/or conditional parameters.