3D Secure 2 Authentication

Important to Consider

To trigger specific 3D Secure 2 user journeys:

  • Include the cardHolderName as specified in the CardHolderName Table

    The cardHolderName corresponds to an expected transaction result.

  • Ensure Judopay has enabled 3D Secure 2 on your sandbox tokens.

    • If 3D Secure 2 is not enabled on your tokens, the test transaction will be successful, however it will not have followed the 3D Secure 2 verification process.

 

The following 3D Secure 2 scenarios are intended for merchants who are directly integrating with Judopay, to test the 3D Secure 2 frictionless and challenge flows.
If you are integrating using Judopay's front end / UI SDK, the 3D Secure 2 flows are handled on your behalf.

 

CardHolderName Table

To trigger a challenge response without device details, from the CardHolderName table, use cardHolderName:

  • Frictionless NoMethod

with challengeRequestIndicator=challengeAsMandate.

 

If you specify a different cardHolderName to any found in the table below, the Frictionless Successful flow will be the default flow.

CardHolderName

Flow Type

Expected Responses

ECI*

Frictionless Successful

Frictionless

DeviceDetails

Receipt

05

Frictionless NoMethod

Frictionless Receipt 05

Frictionless AuthNotSuccess

Frictionless

DeviceDetails

Error code 177

06

Frictionless AuthFailed

Frictionless

DeviceDetails

Error code 165

07

Frictionless IssuerReject

Frictionless

DeviceDetails

Error code 186

07

Frictionless AuthenticationError

Frictionless

DeviceDetails

Error code 182

07

Challenge Required

Challenge

DeviceDetails

Challenge

Receipt

N/A

*Electronic Commerce Indicator

The Electronic Commerce Indicator (ECI) as received from the 3D Secure Server. Denotes the 3D Secure Authentication status, used to show liability status.

For more information, see Liability Shift.

You should check how your app responds to the different transaction results.

 

Testing 3D Secure 2 Flows (Frictionless Flow)

Request Example:

 

Authorisation Successful with 3D Secure 2

To trigger specific 3D Secure 2 user journeys, include the cardHolderName as specified in the CardHolderName Table

The cardHolderName corresponds to an expected transaction result.
cardHolderName is case sensitive, make sure it appears as below:

Card Type

CardHolderName

Card Number

Expiry Date

Start Date

CV2

Address

 Expected Outcome*

Visa

Frictionless Successful

4976 0000 0000 3436

12/25

11/20

452

32 Mulberry Street,
Eastfort,

Violetdell

VL14 8PA

The 3D Secure 2 flow will return conditional steps should additional information be required from the consumer.

 

In response to the initial call:

  • First Response: Device Details

No additional information is required:

  • Second Response: Receipt

Step One:

Initial request -> Device Details response:

{  
    "methodUrl":"https://test.portal.gpwebpay.com/ paysim/sim/acs",  
    "version": "2.2.0",  
    "receiptId": "933044681309327360",  
    "result": "Additional device data is needed for 3D Secure 2",  
    "message": "Issuer ACS has requested additional device data gathering", 
    "md" "ewogICJ0aHJlZURTU2VydmVyVHJh" 
}

 

Step Two:

Receipt response:

{  
    "receiptId": "933048235499622400",  
    "yourPaymentReference": "df11021c-7435-4894-8eb2a",  
    "type": "Payment",  
    "createdAt": "2023-01-18T17:20:34.5486+00:00",  
    "result": "Success",  
    "message": "AuthCode: 150",  
    "judoId": 100502814,  
    "merchantName": "Shodan - Cybersource Routing",  
    "appearsOnStatementAs": "APL*/ShodanCybersourceRo",  
    "originalAmount": "150.10",  
    "netAmount": "150.10",  
    "amount": "150.10",  
    "currency": "GBP",  
    "acquirerTransactionId": "7017269349",  
    "externalBankResponseCode": "0",  
    "cardDetails":  {  
        "cardLastfour": "1111",  
        "endDate": "1224",  
        "cardToken": "SOF-jUB--6lcSFKEIePAvizxvA",  
        "cardType": 1,  
        "cardScheme": "Visa",  
        "cardFunding": "Credit",  
        "cardCategory": "",  
        "cardQualifier": 0,  
        "cardCountry": "US",  
        "bank": "Jpmorgan Chase Bank, N.A."  
        },  
    "billingAddress":  {  
        "address1": "My house",  
        "address2": "My street",  
        "town": "My town",  
        "postCode": "RM17 5YT",  
        "countryCode": 826,  
        "line1": "My house",  
        "line2": "My street",  
        "city": "My town"  
        },  
    "consumer":  {  
        "consumerToken": "130pi5vHbcmDYQHU",  
        "yourConsumerReference": "3ds2 test-1"  
        },  
    "threeDSecure":  {  
        "attempted": true,  
        "result": "PASSED"  
        },  
    "risks":  {  
        "postCodeCheck": "UNKNOWN",  
        "cv2Check": "UNKNOWN",  
        "eciIndicator": "05"  
        } 
}

 

 

 

Visa

Frictionless NoMethod

4921 8100 0000 5462

12/25

11/20

441

11 Jackson Close, 

Stoneden,

Wildefay

WL2 7DQ

The 3D Secure 2 flow will return conditional steps should additional information be required from the consumer.

 

In response to the initial call, no additional information is required:

  • First Response: Receipt

Step One:

Receipt response:

{  
    "receiptId": "933048235499622400",  
    "yourPaymentReference": "df11021c-7435-4894-8eb2a",  
    "type": "Payment",  
    "createdAt": "2023-01-18T17:20:34.5486+00:00",  
    "result": "Success",  
    "message": "AuthCode: 150",  
    "judoId": 100502814,  
    "merchantName": "Shodan - Cybersource Routing",  
    "appearsOnStatementAs": "APL*/ShodanCybersourceRo",  
    "originalAmount": "150.10",  
    "netAmount": "150.10",  
    "amount": "150.10",  
    "currency": "GBP",  
    "acquirerTransactionId": "7017269349",  
    "externalBankResponseCode": "0",  
    "cardDetails":  {  
        "cardLastfour": "1111",  
        "endDate": "1224",  
        "cardToken": "SOF-jUB--6lcSFKEIePAvizxvA",  
        "cardType": 1,  
        "cardScheme": "Visa",  
        "cardFunding": "Credit",  
        "cardCategory": "",  
        "cardQualifier": 0,  
        "cardCountry": "US",  
        "bank": "Jpmorgan Chase Bank, N.A."  
        },  
    "billingAddress":  {  
        "address1": "My house",  
        "address2": "My street",  
        "town": "My town",  
        "postCode": "RM17 5YT",  
        "countryCode": 826,  
        "line1": "My house",  
        "line2": "My street",  
        "city": "My town"  
        },  
    "consumer":  {  
        "consumerToken": "130pi5vHbcmDYQHU",  
        "yourConsumerReference": "3ds2 test-1"  
        },  
    "threeDSecure":  {  
        "attempted": true,  
        "result": "PASSED"  
        },  
    "risks":  {  
        "postCodeCheck": "UNKNOWN",  
        "cv2Check": "UNKNOWN",  
        "eciIndicator": "05"  
        } 
}

 

 

*The expected outcome shows the conditional steps within the 3DS 2 flow. Depending on how you are integrating with Judopay, you may only see the receipt or error response. For example, if you are using Judopay's front end / UI SDK, this will handle the conditional steps on your behalf. You will not see the conditional device details check step, as this occurs in the background.


It is useful to have an understanding of the full 3DS 2 payment flow, including the conditional steps, to verify how it relates to the user journey in your app. For more information on the 3DS 2 flow, see Overview of the Frictionless and Challenge Flow.

 

Testing 3D Secure 2 Flows (Non-Frictionless Flow)

To trigger specific 3D Secure 2 user journeys, include the cardHolderName as specified in the CardHolderName Table

The cardHolderName corresponds to an expected transaction result.
cardHolderName is case sensitive, make sure it appears as below:

Card Type

CardHolderName

Card Number

Expiry Date

Start Date

CV2

Address

 Expected Outcome*

Visa

Frictionless AuthNotSuccess

422169 00000
04963

12/25

11/20

125

274 Grove Street,

Rayvale,

Vertland

VT22 6JN

The 3D Secure 2 flow will return conditional steps should additional information be required from the consumer.

 

In response to the initial call:

  • First Response: Device Details

In response to the call made to /resume3ds

  • Error code 177: Authentication was attempted but failed due to Issuer response.

Step One:

Initial request -> Device Details response:

{  
    "methodUrl":"https://test.portal.gpwebpay.com/ paysim/sim/acs",  
    "version": "2.2.0",  
    "receiptId": "933044681309327360",  
    "result": "Additional device data is needed for 3D Secure 2",  
    "message": "Issuer ACS has requested additional device data gathering", 
    "md" "ewogICJ0aHJlZURTU2VydmVyVHJh" 
}

 

Error response:

{  
    "message": "Authentication was attempted but failed due to Issuer response.",  
    "code": 177,  
    "category": 4
}

 

 

 

Visa

Frictionless AuthFailed

492181 0000
009076

12/25

11/20

875

4 Laurel Drive,

Prywynne,

Swynbeach 

SY7 0JB

The 3D Secure 2 flow will return conditional steps should additional information be required from the consumer.

 

In response to the initial call:

  • First Response: Device Details

In response to the call made to /resume3ds

  • Error code 165: Unable to process transaction. Card authentication failed with 3DS Server.

Step One:

Initial request -> Device Details response:

{  
    "methodUrl":"https://test.portal.gpwebpay.com/ paysim/sim/acs",  
    "version": "2.2.0",  
    "receiptId": "933044681309327360",  
    "result": "Additional device data is needed for 3D Secure 2",  
    "message": "Issuer ACS has requested additional device data gathering", 
    "md" "ewogICJ0aHJlZURTU2VydmVyVHJh" 
}

 

Error response:

{  
    "message": "Unable to process transaction. Card authentication failed with 3DS Server.",  
    "code": 165,  
    "category": 4
}

 

 

 

Visa

Frictionless IssuerReject

4792840 0000
09202

12/25

11/20

654

9 Pearl Street, 

Dracmeadow, 

Byhedge

BH11 9BB

The 3D Secure 2 flow will return conditional steps should additional information be required from the consumer.

 

In response to the initial call:

  • First Response: Device Details

In response to the call made to /resume3ds

  • Error code 186: Authentication rejected by the Issuer as card used is flagged as stolen.

Step One:

Initial request -> Device Details response:

{  
    "methodUrl":"https://test.portal.gpwebpay.com/ paysim/sim/acs",  
    "version": "2.2.0",  
    "receiptId": "933044681309327360",  
    "result": "Additional device data is needed for 3D Secure 2",  
    "message": "Issuer ACS has requested additional device data gathering", 
    "md" "ewogICJ0aHJlZURTU2VydmVyVHJh" 
}

 

Error response:

{  
    "message": "Authentication rejected by the Issuer as card used is flagged as stolen.",  
    "code": 186,   
    "category": 4
}

 

 

 

Visa

Frictionless AuthenticationError

4921810 0000
05850

12/25

11/20

217

54 Madison Avenue,

Aldapple,

Rayland

RL5 0HA

The 3D Secure 2 flow will return conditional steps should additional information be required from the consumer.

 

In response to the initial call:

  • First Response: Device Details

In response to the call made to /resume3ds

  • Error code 182: Unable to authenticate transaction as card authentication has failed.

Step One:

Initial request -> Device Details response:

{  
    "methodUrl":"https://test.portal.gpwebpay.com/ paysim/sim/acs",  
    "version": "2.2.0",  
    "receiptId": "933044681309327360",  
    "result": "Additional device data is needed for 3D Secure 2",  
    "message": "Issuer ACS has requested additional device data gathering", 
    "md" "ewogICJ0aHJlZURTU2VydmVyVHJh" 
}

 

Error response:

{  
    "message": "Unable to authenticate transaction as card authentication has failed.",  
    "code": 182, 
    "category": 4
}

 

 

 
Visa

Challenge Required

4792840 0000
09202

12/25

11/20

654

9 Pearl Street, 

Dracmeadow, 

Byhedge

BH11 9BB

The 3D Secure 2 flow will return conditional steps should additional information be required from the consumer.

 

In response to the initial call:

  • First Response: Device Details

In response to the call made to /resume3ds

  • Second Response :Challenge

In response to the call made to /complete3ds

  • Third Response: Receipt

Step One:

Initial request -> Device Details response:

{  
    "methodUrl":"https://test.portal.gpwebpay.com/ paysim/sim/acs",  
    "version": "2.2.0",  
    "receiptId": "933044681309327360",  
    "result": "Additional device data is needed for 3D Secure 2",  
    "message": "Issuer ACS has requested additional device data gathering", 
    "md" "ewogICJ0aHJlZURTU2VydmVyVHJh" 
}

 

Step Two:

Resume 3ds2 request -> Challenge Required response:

{  
    "challengeUrl": "https://acs2p.test.gpe.cz/challenge",  
    "cReq": "ewogICJtZXNzYWdlVHlwZSIgOi",  
    "version": "2.1.0",  
    "receiptId": "933047860931497984",  
    "result": "Challenge completion is needed for 3D Secure 2",  
    "message": "Issuer ACS has responded with a Challenge URL",  
    "md": "ewogICJ0aHJlZURTU2VydmVyVHJhb" 
}

 

Step Three:

Complete 3ds2 request -> Receipt response:

{  
    "receiptId": "933048235499622400",  
    "yourPaymentReference": "df11021c-7435-4894-8eb2a",  
    "type": "Payment",  
    "createdAt": "2023-01-18T17:20:34.5486+00:00",  
    "result": "Success",  
    "message": "AuthCode: 150",  
    "judoId": 100502814,  
    "merchantName": "Shodan - Cybersource Routing",  
    "appearsOnStatementAs": "APL*/ShodanCybersourceRo",  
    "originalAmount": "150.10",  
    "netAmount": "150.10",  
    "amount": "150.10",  
    "currency": "GBP",  
    "acquirerTransactionId": "7017269349",  
    "externalBankResponseCode": "0",  
    "cardDetails":  {  
        "cardLastfour": "1111",  
        "endDate": "1224",  
        "cardToken": "SOF-jUB--6lcSFKEIePAvizxvA",  
        "cardType": 1,  
        "cardScheme": "Visa",  
        "cardFunding": "Credit",  
        "cardCategory": "",  
        "cardQualifier": 0,  
        "cardCountry": "US",  
        "bank": "Jpmorgan Chase Bank, N.A."  
        },  
    "billingAddress":  {  
        "address1": "My house",  
        "address2": "My street",  
        "town": "My town",  
        "postCode": "RM17 5YT",  
        "countryCode": 826,  
        "line1": "My house",  
        "line2": "My street",  
        "city": "My town"  
        },  
    "consumer":  {  
        "consumerToken": "130pi5vHbcmDYQHU",  
        "yourConsumerReference": "3ds2 test-1"  
        },  
    "threeDSecure":  {  
        "attempted": true,  
        "result": "PASSED"  
        },  
    "risks":  {  
        "postCodeCheck": "UNKNOWN",  
        "cv2Check": "UNKNOWN",  
        "eciIndicator": "05"  
        } 
}

 

*The expected outcome shows the conditional steps within the 3DS 2 flow. Depending on how you are integrating with Judopay, you may only see the receipt or error response. For example, if you are using Judopay's front end / UI SDK, this will handle the conditional steps on your behalf. You will not see the conditional device details check step, as this occurs in the background.

 

It is useful to have an understanding of the full 3DS 2 payment flow, including the conditional steps, to verify how it relates to the user journey in your app. For more information on the 3DS 2 flow, see Overview of the Frictionless and Challenge Flow.

 

For a list of possible error codes, types and descriptions, see Error Codes and Descriptions