{"title":"Testing 3D Secure 2 authentication","category":"default","creationDate":1779533780,"content":"<p>Test your integration to make sure that you can handle <a href=\"\/online-payments\/3d-secure\">3D Secure 2 authentication<\/a> scenarios.<\/p>\n<p>If you configured <a href=\"\/risk-management\/dynamic-3d-secure\/\">Dynamic 3D Secure<\/a> and your default rule is set to <span translate=\"no\"><strong>Prefer Not<\/strong><\/span> do either of the following to trigger 3D Secure 2 scenarios while testing:<\/p>\n<ul>\n<li>Set your default Dynamic 3D Secure rule to <span translate=\"no\"><strong>Always<\/strong><\/span>.<\/li>\n<li>Include <code>authenticationData.attemptAuthentication<\/code> in your API request.<\/li>\n<li>Use an amount that triggers authentication.<\/li>\n<\/ul>\n<p>When prompted for 3D Secure 2 text challenges:<\/p>\n<ul>\n<li>For web and mobile browser integrations, use password: <span translate=\"no\"><strong>password<\/strong><\/span>.<\/li>\n<li>For native mobile (app-based) integrations, use password: <span translate=\"no\"><strong>1234<\/strong><\/span>.<\/li>\n<\/ul>\n<p>If you want to test failed scenarios, use the wrong password (any value other than password provided) to fail the authentication challenge.<\/p>\n<p>To view the details and results of your test payments, do either of the following:<\/p>\n<ul>\n<li>In your <a href=\"https:\/\/ca-test.adyen.com\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\" class=\"external-link no-image\">test Customer Area<\/a>, go to <strong>Transactions<\/strong> &gt; <strong>Payments<\/strong>.<\/li>\n<li>Check the <span translate=\"no\"><strong>AUTHORISATION<\/strong><\/span> <a href=\"\/development-resources\/webhooks\/webhook-types\/#transaction-events\">webhook<\/a> you received. The <code>success<\/code> field informs you of the outcome of a payment request.<\/li>\n<\/ul>\n<h2 id=\"test-cards\">Test cards<\/h2>\n<p>These cards are enrolled in 3D Secure.<\/p>\n<p>Make test payments with the following cards to make sure your integration can handle 3D Secure 2 authentication scenarios.<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Card Type<\/th>\n<th style=\"text-align: left;\">Card Number<\/th>\n<th style=\"text-align: left;\">Expiry Date<\/th>\n<th style=\"text-align: center;\">Security Code (CVC\/CVV\/CID)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">American Express<\/td>\n<td style=\"text-align: left;\">3714 4963 5398 431<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">7373<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Bancontact \/ Maestro<\/td>\n<td style=\"text-align: left;\">6703 4444 4444 4449<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">Not applicable<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Bancontact \/ Visa<\/td>\n<td style=\"text-align: left;\">4871 0499 9999 9910<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">737<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Cartes Bancaires \/ Visa Debit<\/td>\n<td style=\"text-align: left;\">4035 5014 2814 6300<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">737<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Cartes Bancaires<\/td>\n<td style=\"text-align: left;\">4360 0000 0100 0005<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">737<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">China UnionPay (Credit)<\/td>\n<td style=\"text-align: left;\">6250 9470 0000 0014<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">123<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">China UnionPay (Debit)<\/td>\n<td style=\"text-align: left;\">6250 9460 0000 0016<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">123<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Diners<\/td>\n<td style=\"text-align: left;\">3056 9309 0259 04<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">737<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Discover<\/td>\n<td style=\"text-align: left;\">6011 1111 1111 1117<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">737<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">JCB \/ Mastercard<\/td>\n<td style=\"text-align: left;\">3566 1111 1111 1113<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">737<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Maestro<\/td>\n<td style=\"text-align: left;\">5000 5500 0000 0029<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">Not applicable<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mastercard<\/td>\n<td style=\"text-align: left;\">5454 5454 5454 5454<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">737<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mastercard Credit<\/td>\n<td style=\"text-align: left;\">2222 4000 1000 0008<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">737<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">4917 6100 0000 0000<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">737<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa Classic<\/td>\n<td style=\"text-align: left;\">4166 6766 6766 6746<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: center;\">737<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>When you make a payment request with these cards, you receive the following result codes depending on your integration:<\/p>\n<ul>\n<li><span translate=\"no\"><strong>RedirectShopper<\/strong><\/span>: you receive this result code if you use <a href=\"\/online-payments\/3d-secure\/redirect-3ds2\/\">Redirect authentication<\/a>.<\/li>\n<li><span translate=\"no\"><strong>IdentifyShopper<\/strong><\/span>: you receive this result code if you use <a href=\"\/online-payments\/3d-secure\/native-3ds2\/\">Native authentication<\/a>.<\/li>\n<li><span translate=\"no\"><strong>ChallengeShopper<\/strong><\/span>: you get this result code after you submit the 3D Secure 2 device fingerprinting result for Native authentication, unless you specify a frictionless flow.<\/li>\n<\/ul>\n<h2>3D Secure 2 challenge action<\/h2>\n<p>If your integration uses the <a href=\"\/online-payments\/build-your-integration\">Advanced flow<\/a>, test this scenario. This does not apply to integrations using the Sessions flow.<\/p>\n<p>Test a payment that requires handling the action object included in a payment response that includes the <span translate=\"no\"><strong>ChallengeShopper<\/strong><\/span> <a href=\"\/online-payments\/build-your-integration\/payment-result-codes#3d-secure-authentication\">result code<\/a>. Use the following payment details:<\/p>\n<table>\n<thead>\n<tr>\n<th>Card type<\/th>\n<th>Card number<\/th>\n<th>Expiry date<\/th>\n<th>Security code (CVC\/CVV\/CID)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Visa<\/td>\n<td>4212 3456 7891 0006<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>If the payment was not successful, check that your client-side and server-side integration handles the required action from the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> response.<\/p>\n<h2>Frictionless flow<\/h2>\n<p>If your integration uses the <a href=\"\/online-payments\/build-your-integration\">Advanced flow<\/a>, test this scenario. This does not apply to integrations using the Sessions flow.<\/p>\n<p>Test a payment that goes through <a href=\"\/online-payments\/3d-secure\/#frictionless-flow\">frictionless flow<\/a>, where your integration must provide a device fingerprint. No further authentication interaction with the client-side UI is required. Use the following payment details:<\/p>\n<table>\n<thead>\n<tr>\n<th>Card type<\/th>\n<th>Card number<\/th>\n<th>Expiry date<\/th>\n<th>Security code (CVC\/CVV\/CID)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2815 0512 9736<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>If the payment was not successful, check that your client-side and server-side integration handles the required action from the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">\/payments<\/a> response.<\/p>\n<h2>Mobile app integration<\/h2>\n<p>On mobile, shoppers can get different types of 3D Secure 2 authentication challenges. Use the following payment details to make test payments and test specific scenarios.<\/p>\n<p>When prompted for 3D Secure 2 text challenge for native mobile (app-based) integrations, use password: <span translate=\"no\"><strong>1234<\/strong><\/span>. If you want to test failed scenarios, use the wrong password (any value other than <span translate=\"no\"><strong>1234<\/strong><\/span>) to fail the authentication challenge.<\/p>\n<table>\n<thead>\n<tr>\n<th>Card type<\/th>\n<th>Card number<\/th>\n<th>Expiry date<\/th>\n<th>Security code (CVC\/CVV\/CID)<\/th>\n<th>Scenario<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2855 6567 2311<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>Basic text authentication<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2874 9905 2008<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>Basic single select<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2815 9233 1633<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>Basic multi select<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2888 2269 6974<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>Basic out-of-band (OOB) authentication<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2895 0084 3268<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>HTML out-of-band (OOB) authentication<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2861 5377 1465<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>App single select and text authentication<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>To test advanced 3D Secure 2 authentication scenarios for native mobile (app-based) integrations, use the following test cards:<\/p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Card type<\/th>\n<th style=\"text-align: left;\">Card number<\/th>\n<th style=\"text-align: left;\">Expiry Date<\/th>\n<th style=\"text-align: left;\">Security Code (CVC\/CVV\/CID)<\/th>\n<th style=\"text-align: left;\">Scenario<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">4917 6100 0000 0042<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: left;\">737<\/td>\n<td style=\"text-align: left;\">ACS sends an empty Challenge Response (<code>CRes<\/code>)<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">4917 6100 0000 0067<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: left;\">737<\/td>\n<td style=\"text-align: left;\">Invalid content in the <code>acsSignedContent<\/code> field in Authentication Response (<code>ARes<\/code>)<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Visa<\/td>\n<td style=\"text-align: left;\">4917 6100 0000 0059<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: left;\">737<\/td>\n<td style=\"text-align: left;\">Challenge Response (<code>CRes<\/code>) timeout<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>To test the scenario where a payment is routed to the <a href=\"\/online-payments\/3d-secure\/redirect-3ds2\">Redirect 3D Secure 2<\/a> flow for your native mobile (app-based) integration, make a test payment without the  <a href=\"https:\/\/docs.adyen.com\/api-explorer\/Checkout\/latest\/post\/payments#request-paymentMethod-CardDetails-threeDS2SdkVersion\" class=\"codeLabel  external-link no-image\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">paymentMethod.threeDS2SdkVersion<\/a> parameter.<\/p>\n<h2>Standalone authentication flow<\/h2>\n<p>If your integration uses the <a href=\"\/online-payments\/3d-secure\/standalone-authentication\/\">standalone authentication flow<\/a>, test that your integration can handle the possible outcomes using our <a href=\"#test-cards\">test cards<\/a>.<\/p>\n<p>In this flow, you receive an <span translate=\"no\"><strong>AUTHENTICATION<\/strong><\/span> webhook, instead of the <span translate=\"no\"><strong>AUTHORISATION<\/strong><\/span> webhook to inform you of the payment request outcome.<\/p>\n<h2>Authentication without liability shift<\/h2>\n<p>Test a payment that goes through 3D Secure 2 authentication without <a href=\"\/online-payments\/3d-secure-for-regulation-compliance\/#3dsecurechargebackliabilityshiftrules\">liability shift<\/a>, use the following payment details.<\/p>\n<p>When prompted for a 3D Secure 2 text challenge, use password: <span translate=\"no\"><strong>NoLiabilityShift<\/strong><\/span>.<\/p>\n<table>\n<thead>\n<tr>\n<th>Card type<\/th>\n<th>Card number<\/th>\n<th>Expiry date<\/th>\n<th>Security code (CVC\/CVV\/CID)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Visa<\/td>\n<td>4917 6100 0000 0000<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Advanced scenarios<\/h2>\n<p>Test the following scenarios to make sure your integration can handle advanced 3D Secure 2 flows.<\/p>\n<p>Use the following test cards to test scenarios returning <code>ARes<\/code> (Authentication Response) with different <code>transStatus<\/code> values:<\/p>\n<ul>\n<li><span translate=\"no\"><strong>Y<\/strong><\/span>: Authentication \/ account verification successful.<\/li>\n<li><span translate=\"no\"><strong>N<\/strong><\/span>: Not Authenticated \/ account not verified. Transaction denied.<\/li>\n<li><span translate=\"no\"><strong>A<\/strong><\/span>: Authentication \/ verification was attempted but could not be verified.<\/li>\n<li><span translate=\"no\"><strong>U<\/strong><\/span>: Authentication \/ account verification could not be performed.<\/li>\n<li><span translate=\"no\"><strong>R<\/strong><\/span>: Authentication \/ account verification rejected by the Issuer.<\/li>\n<\/ul>\n<table>\n<thead>\n<tr>\n<th style=\"text-align: left;\">Card type<\/th>\n<th style=\"text-align: left;\">Card number<\/th>\n<th style=\"text-align: left;\">Expiry date<\/th>\n<th style=\"text-align: left;\">Security Code (CVC\/CVV\/CID)<\/th>\n<th style=\"text-align: left;\">Scenario<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td style=\"text-align: left;\">Mastercard<\/td>\n<td style=\"text-align: left;\">5201 2815 0512 9736<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: left;\">737<\/td>\n<td style=\"text-align: left;\">Return <code>ARes<\/code> with <code>transStatus<\/code>=<span translate=\"no\"><strong>Y<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mastercard<\/td>\n<td style=\"text-align: left;\">5201 2812 6243 5268<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: left;\">737<\/td>\n<td style=\"text-align: left;\">Return <code>ARes<\/code> with <code>transStatus<\/code>=<span translate=\"no\"><strong>N<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mastercard<\/td>\n<td style=\"text-align: left;\">5201 2850 9382 3592<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: left;\">737<\/td>\n<td style=\"text-align: left;\">Return <code>ARes<\/code> with <code>transStatus<\/code>=<span translate=\"no\"><strong>A<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mastercard<\/td>\n<td style=\"text-align: left;\">5201 2828 2836 6351<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: left;\">737<\/td>\n<td style=\"text-align: left;\">Return <code>ARes<\/code> with <code>transStatus<\/code>=<span translate=\"no\"><strong>U<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mastercard<\/td>\n<td style=\"text-align: left;\">5201 2864 9681 6589<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: left;\">737<\/td>\n<td style=\"text-align: left;\">Return <code>ARes<\/code> with <code>transStatus<\/code>=<span translate=\"no\"><strong>R<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left;\">Mastercard<\/td>\n<td style=\"text-align: left;\">5201 2846 7071 7533<\/td>\n<td style=\"text-align: left;\">03\/2030<\/td>\n<td style=\"text-align: left;\">737<\/td>\n<td style=\"text-align: left;\">Return <code>ARes<\/code> with <code>transStatus<\/code>=<span translate=\"no\"><strong>U<\/strong><\/span> and <a href=\"\/online-payments\/3d-secure\/api-reference\/#possible-transstatusreason-values\">\n  <code>transStatusReason<\/code>\n<\/a>=<span translate=\"no\"><strong>06<\/strong><\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Use the following test cards to test other advanced 3D Secure 2 scenarios.<\/p>\n<table>\n<thead>\n<tr>\n<th>Card type<\/th>\n<th>Card number<\/th>\n<th>Expiry date<\/th>\n<th>Security Code (CVC\/CVV\/CID)<\/th>\n<th>Scenario<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2829 9900 5515<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>Timeout error<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2886 9531 5843<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>Connection failure error<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2858 9491 2800<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>Version number not supported error<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2852 4062 4612<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>Access denied error<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2859 4986 5169<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>MCC not valid error<\/td>\n<\/tr>\n<tr>\n<td>Mastercard<\/td>\n<td>5201 2829 4084 9714<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<td>Invalid endpoint error<\/td>\n<\/tr>\n<\/tbody>\n<\/table>","url":"https:\/\/docs.adyen.com\/development-resources\/testing\/3d-secure-2-authentication","articleFields":{"description":"Test 3D Secure 2 authentication with your integration and troubleshoot issues before it goes live.","cache_enable":false},"algolia":{"url":"https:\/\/docs.adyen.com\/development-resources\/testing\/3d-secure-2-authentication","title":"Testing 3D Secure 2 authentication","content":"Test your integration to make sure that you can handle 3D Secure 2 authentication scenarios.\nIf you configured Dynamic 3D Secure and your default rule is set to Prefer Not do either of the following to trigger 3D Secure 2 scenarios while testing:\n\nSet your default Dynamic 3D Secure rule to Always.\nInclude authenticationData.attemptAuthentication in your API request.\nUse an amount that triggers authentication.\n\nWhen prompted for 3D Secure 2 text challenges:\n\nFor web and mobile browser integrations, use password: password.\nFor native mobile (app-based) integrations, use password: 1234.\n\nIf you want to test failed scenarios, use the wrong password (any value other than password provided) to fail the authentication challenge.\nTo view the details and results of your test payments, do either of the following:\n\nIn your test Customer Area, go to Transactions &gt; Payments.\nCheck the AUTHORISATION webhook you received. The success field informs you of the outcome of a payment request.\n\nTest cards\nThese cards are enrolled in 3D Secure.\nMake test payments with the following cards to make sure your integration can handle 3D Secure 2 authentication scenarios.\n\n\n\nCard Type\nCard Number\nExpiry Date\nSecurity Code (CVC\/CVV\/CID)\n\n\n\n\nAmerican Express\n3714 4963 5398 431\n03\/2030\n7373\n\n\nBancontact \/ Maestro\n6703 4444 4444 4449\n03\/2030\nNot applicable\n\n\nBancontact \/ Visa\n4871 0499 9999 9910\n03\/2030\n737\n\n\nCartes Bancaires \/ Visa Debit\n4035 5014 2814 6300\n03\/2030\n737\n\n\nCartes Bancaires\n4360 0000 0100 0005\n03\/2030\n737\n\n\nChina UnionPay (Credit)\n6250 9470 0000 0014\n03\/2030\n123\n\n\nChina UnionPay (Debit)\n6250 9460 0000 0016\n03\/2030\n123\n\n\nDiners\n3056 9309 0259 04\n03\/2030\n737\n\n\nDiscover\n6011 1111 1111 1117\n03\/2030\n737\n\n\nJCB \/ Mastercard\n3566 1111 1111 1113\n03\/2030\n737\n\n\nMaestro\n5000 5500 0000 0029\n03\/2030\nNot applicable\n\n\nMastercard\n5454 5454 5454 5454\n03\/2030\n737\n\n\nMastercard Credit\n2222 4000 1000 0008\n03\/2030\n737\n\n\nVisa\n4917 6100 0000 0000\n03\/2030\n737\n\n\nVisa Classic\n4166 6766 6766 6746\n03\/2030\n737\n\n\n\nWhen you make a payment request with these cards, you receive the following result codes depending on your integration:\n\nRedirectShopper: you receive this result code if you use Redirect authentication.\nIdentifyShopper: you receive this result code if you use Native authentication.\nChallengeShopper: you get this result code after you submit the 3D Secure 2 device fingerprinting result for Native authentication, unless you specify a frictionless flow.\n\n3D Secure 2 challenge action\nIf your integration uses the Advanced flow, test this scenario. This does not apply to integrations using the Sessions flow.\nTest a payment that requires handling the action object included in a payment response that includes the ChallengeShopper result code. Use the following payment details:\n\n\n\nCard type\nCard number\nExpiry date\nSecurity code (CVC\/CVV\/CID)\n\n\n\n\nVisa\n4212 3456 7891 0006\n03\/2030\n737\n\n\n\nIf the payment was not successful, check that your client-side and server-side integration handles the required action from the  \/payments response.\nFrictionless flow\nIf your integration uses the Advanced flow, test this scenario. This does not apply to integrations using the Sessions flow.\nTest a payment that goes through frictionless flow, where your integration must provide a device fingerprint. No further authentication interaction with the client-side UI is required. Use the following payment details:\n\n\n\nCard type\nCard number\nExpiry date\nSecurity code (CVC\/CVV\/CID)\n\n\n\n\nMastercard\n5201 2815 0512 9736\n03\/2030\n737\n\n\n\nIf the payment was not successful, check that your client-side and server-side integration handles the required action from the  \/payments response.\nMobile app integration\nOn mobile, shoppers can get different types of 3D Secure 2 authentication challenges. Use the following payment details to make test payments and test specific scenarios.\nWhen prompted for 3D Secure 2 text challenge for native mobile (app-based) integrations, use password: 1234. If you want to test failed scenarios, use the wrong password (any value other than 1234) to fail the authentication challenge.\n\n\n\nCard type\nCard number\nExpiry date\nSecurity code (CVC\/CVV\/CID)\nScenario\n\n\n\n\nMastercard\n5201 2855 6567 2311\n03\/2030\n737\nBasic text authentication\n\n\nMastercard\n5201 2874 9905 2008\n03\/2030\n737\nBasic single select\n\n\nMastercard\n5201 2815 9233 1633\n03\/2030\n737\nBasic multi select\n\n\nMastercard\n5201 2888 2269 6974\n03\/2030\n737\nBasic out-of-band (OOB) authentication\n\n\nMastercard\n5201 2895 0084 3268\n03\/2030\n737\nHTML out-of-band (OOB) authentication\n\n\nMastercard\n5201 2861 5377 1465\n03\/2030\n737\nApp single select and text authentication\n\n\n\nTo test advanced 3D Secure 2 authentication scenarios for native mobile (app-based) integrations, use the following test cards:\n\n\n\nCard type\nCard number\nExpiry Date\nSecurity Code (CVC\/CVV\/CID)\nScenario\n\n\n\n\nVisa\n4917 6100 0000 0042\n03\/2030\n737\nACS sends an empty Challenge Response (CRes)\n\n\nVisa\n4917 6100 0000 0067\n03\/2030\n737\nInvalid content in the acsSignedContent field in Authentication Response (ARes)\n\n\nVisa\n4917 6100 0000 0059\n03\/2030\n737\nChallenge Response (CRes) timeout\n\n\n\nTo test the scenario where a payment is routed to the Redirect 3D Secure 2 flow for your native mobile (app-based) integration, make a test payment without the  paymentMethod.threeDS2SdkVersion parameter.\nStandalone authentication flow\nIf your integration uses the standalone authentication flow, test that your integration can handle the possible outcomes using our test cards.\nIn this flow, you receive an AUTHENTICATION webhook, instead of the AUTHORISATION webhook to inform you of the payment request outcome.\nAuthentication without liability shift\nTest a payment that goes through 3D Secure 2 authentication without liability shift, use the following payment details.\nWhen prompted for a 3D Secure 2 text challenge, use password: NoLiabilityShift.\n\n\n\nCard type\nCard number\nExpiry date\nSecurity code (CVC\/CVV\/CID)\n\n\n\n\nVisa\n4917 6100 0000 0000\n03\/2030\n737\n\n\n\nAdvanced scenarios\nTest the following scenarios to make sure your integration can handle advanced 3D Secure 2 flows.\nUse the following test cards to test scenarios returning ARes (Authentication Response) with different transStatus values:\n\nY: Authentication \/ account verification successful.\nN: Not Authenticated \/ account not verified. Transaction denied.\nA: Authentication \/ verification was attempted but could not be verified.\nU: Authentication \/ account verification could not be performed.\nR: Authentication \/ account verification rejected by the Issuer.\n\n\n\n\nCard type\nCard number\nExpiry date\nSecurity Code (CVC\/CVV\/CID)\nScenario\n\n\n\n\nMastercard\n5201 2815 0512 9736\n03\/2030\n737\nReturn ARes with transStatus=Y\n\n\nMastercard\n5201 2812 6243 5268\n03\/2030\n737\nReturn ARes with transStatus=N\n\n\nMastercard\n5201 2850 9382 3592\n03\/2030\n737\nReturn ARes with transStatus=A\n\n\nMastercard\n5201 2828 2836 6351\n03\/2030\n737\nReturn ARes with transStatus=U\n\n\nMastercard\n5201 2864 9681 6589\n03\/2030\n737\nReturn ARes with transStatus=R\n\n\nMastercard\n5201 2846 7071 7533\n03\/2030\n737\nReturn ARes with transStatus=U and \n  transStatusReason\n=06\n\n\n\nUse the following test cards to test other advanced 3D Secure 2 scenarios.\n\n\n\nCard type\nCard number\nExpiry date\nSecurity Code (CVC\/CVV\/CID)\nScenario\n\n\n\n\nMastercard\n5201 2829 9900 5515\n03\/2030\n737\nTimeout error\n\n\nMastercard\n5201 2886 9531 5843\n03\/2030\n737\nConnection failure error\n\n\nMastercard\n5201 2858 9491 2800\n03\/2030\n737\nVersion number not supported error\n\n\nMastercard\n5201 2852 4062 4612\n03\/2030\n737\nAccess denied error\n\n\nMastercard\n5201 2859 4986 5169\n03\/2030\n737\nMCC not valid error\n\n\nMastercard\n5201 2829 4084 9714\n03\/2030\n737\nInvalid endpoint error\n\n\n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Development resources","lvl2":"Testing your online payments integration","lvl3":"Testing 3D Secure 2 authentication"},"hierarchy_url":{"lvl0":"https:\/\/docs.adyen.com\/","lvl1":"https:\/\/docs.adyen.com\/development-resources","lvl2":"https:\/\/docs.adyen.com\/development-resources\/testing","lvl3":"\/development-resources\/testing\/3d-secure-2-authentication"},"levels":4,"category":"Development Resources","category_color":"green","tags":["Testing","Secure","authentication"]}}