All 3-D Secure test transactions go to the Peach Payments 3-D Secure simulator. Use these test cards for testing. Cards that are not listed on that page return the 000.400.109 Card is not enrolled for 3DS version 2 error.

To use your own test card, force the card enrolment via a custom parameter. You can also override the default flow to test a frictionless or a challenge workflow. Furthermore, you can force a challenge by sending the appropriate challenge indicator flag.

Summary of available custom parameters:

Parameter	Effect
`customParameters[3DS2_enrolled]=true`	Use any test card to test 3-D Secure, even if it's not on the list below.
`customParameters[3DS2_flow]=challenge`	Force the authentication to execute the challenge flow.
`customParameters[3DS2_flow]=frictionless`	Force the authentication to execute the frictionless flow.
`threeDSecure.challengeIndicator=4`	Force the authentication to a challenge flow, redirecting the cardholder to the issuer's authentication page.

Cards to use with the Mobile SDK

When using a mobile app, you can present the cardholder challenge in different ways. To simulate these scenarios in a mobile app, use the following cards for testing.

Brand	Card number	User interface	UI type
Visa	4200000000000042	Native	Text
Visa	4200000000000067	HTML	Text
Visa	4012000000003119	Native	Single select
Visa	4012000000003127	Native	Multi select
Visa	4012000000003085	Native	OOB
Mastercard	5200000000000015	Native	Text
Mastercard	5200000000000049	HTML	Text
Maestro	6799998900000060018	Native	Text
Maestro	6773670009114879	HTML	Text
American Express	343434343434343	Native	Text
American Express	375987000000021	HTML	Text
American Express	375987000169735	Native	Single select
American Express	375987000169743	Native	Multi select
American Express	375987000169750	Native	OOB

📘
To learn more about how 3-D Secure works with the Mobile SDK, follow this guide.