Testing your Integration
...
Testing Overview
Testing your Direct (API) Inte...

Testing 3D Secure 2 Authentication

Testing 3D Secure 2 Authentication



Important to Consider

  • 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 Frictionless 3D Secure 2 Flows

Request Example




Successful Frictionless Scenarios




Frictionless Successful:

Frictionless Successful
Expected Outcome*
Example Response: Step One
Example Response: Step Two

Card Type

CardHolderName

Card Number

Expiry Date

Start Date

CV2

Address

Visa

Frictionless Successful

4976 0000 0000 3436

12/25

11/20

452

32 Mulberry Street, Eastfort, Violetdell VL14 8PA



Frictionless NoMethod:

Frictionless NoMethod
Expected Outcome*
Example Response: Step One

Card Type

CardHolderName

Card Number

Expiry Date

Start Date

CV2

Address

Visa

Frictionless NoMethod

4921 8100 0000 5462

12/25

11/20

441

11 Jackson Close, Stoneden, Wildefay WL2 7DQ

*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:



Unsuccessful Frictionless Scenarios

Frictionless AuthNotSuccess:

Frictionless AuthNotSuccess
Expected Outcome*
Example Response: Step One
Example Error Response

Card Type

CardHolderName

Card Number

Expiry Date

Start Date

CV2

Address

Visa

Frictionless AuthNotSuccess

422169 0000004963



12/25

11/20

125

274 Grove Street, Rayvale, Vertland VT22 6JN





Frictionless AuthFailed:

Frictionless AuthFailed
Expected Outcome*
Example Response: Step One
Example Error Response

Card Type

CardHolderName

Card Number

Expiry Date

Start Date

CV2

Address

Visa

Frictionless AuthFailed

492181 0000009076

12/25

11/20

875

4 Laurel Drive, Prywynne, Swynbeach SY7 0JB





Frictionless IssuerReject:

Frictionless IssuerReject
Expected Outcome*
Example Response: Step One
Example Error Response

Card Type

CardHolderName

Card Number

Expiry Date

Start Date

CV2

Address

Visa

Frictionless IssuerReject

4792840 000009202

12/25

11/20

654

9 Pearl Street, Dracmeadow, Byhedge BH11 9BB





Frictionless AuthenticationError:

Frictionless AuthenticationError
Expected Outcome*
Example Response: Step One
Example Error Response

Card Type

CardHolderName

Card Number

Expiry Date

Start Date

CV2

Address

Visa

Frictionless AuthenticationError

4921810 000005850

12/25

11/20

217

54 Madison Avenue, Aldapple, Rayland RL5 0HA

*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:



Testing a Challenge 3D Secure 2 Flow



Challenge Required:

Challenge Required
Expected Outcome*
Example Response: Step One
Example Response: Step Two
Example Response: Step Three

Card Type

CardHolderName

Card Number

Expiry Date

Start Date

CV2

Address

Visa

Challenge Required

4792840 000009202

12/25

11/20

654

9 Pearl Street, Dracmeadow, Byhedge BH11 9BB

*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.