THREE DS 2.0 PROTOCOL

3D Secure 2.0 (3DS 2.0) is the latest update of the 3D Secure authentication protocol, which allows issuing banks to verify card owners during the transaction process. Verifying card owners can transfer liability for fraud disputes away from the merchants who utilize 3DS.

This requires merchants to send additional data with each transaction to help the issuing bank/network determine if the cardholder is actually making the transaction. If there is a mismatch, then the bank will respond asking the customer for additional user authentication data.

The issuer’s 3D Secure service provider assesses the transaction risk.

• If the transaction is determined as high-risk, the transaction goes through a challenge.

• If the transaction is deemed as low-risk, no further action is required on the cardholder’s end. The issuer sends the authentication result to the merchant, who in turn submits the transaction for authorisation with a flag indicating the authentication result.

Mandatory Params:

colourDepth :: Int
javaEnabled :: Boolean
cookieEnabled :: Boolean
javaScriptEnabled :: Boolean
language :: String
screenHeight :: Int
screenWidth :: Int
timeZone :: Int

ALL Params:

{ acceptHeaders :: NullOrUndefined String ,
colourDepth :: Int ,
javaEnabled :: Boolean ,
javaScriptEnabled :: Boolean ,
cookieEnabled :: Boolean ,
language :: String ,
screenHeight :: Int ,
screenWidth :: Int ,
ipAddress :: NullOrUndefined String ,
userAgent :: NullOrUndefined String ,
timeZone :: Int ,
acceptContent :: NullOrUndefined String ,
threeDSecureChallengeWindowSize :: NullOrUndefined String ,
mobilePhoneModel :: NullOrUndefined String }