{"title":"Testing risk features","category":"default","creationDate":1779620072,"content":"<h2>Chargebacks<\/h2>\n<p>If a shopper disputes a transaction, it can become a chargeback.<\/p>\n<p>To test the dispute flow, you can simulate a chargeback to <a href=\"\/risk-management\/disputes-api\/test-applicable-dispute-reasons\/\">test chargeback scenarios<\/a>.<br \/>\nYou can then use your Customer Area or the Disputes API to handle the simulated dispute.<\/p>\n<h2>Risk management<\/h2>\n<p>When you use RevenueProtect, and have turned on and configured risk rules, you can <a href=\"\/risk-management\/configure-manual-risk\/#test-risk-rules\">test if the risk rule triggers<\/a>.<\/p>\n<h2>Address Verification System (AVS)<\/h2>\n<p>You have to include billing address details in the payment request to enable and test <a href=\"\/risk-management\/avs-checks#enable-and-test-avs\">AVS<\/a>.<\/p>\n<p>To test AVS, you can use the following AVS test cards and billing addresses:<\/p>\n<table>\n<thead>\n<tr>\n<th>Card Number<\/th>\n<th>Card Type<\/th>\n<th>House Number<\/th>\n<th>Address<\/th>\n<th>ZIP Code<\/th>\n<th>Country\/region<\/th>\n<th>Expiry Date<\/th>\n<th>Security Code (CVV\/CVC\/CID)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>5555555555554444<\/td>\n<td>Mastercard<\/td>\n<td>10<\/td>\n<td>Downing Street, London.<\/td>\n<td>SW1A 2AA<\/td>\n<td>GB<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<\/tr>\n<tr>\n<td>374251018720018<\/td>\n<td>Amex<\/td>\n<td>1600<\/td>\n<td>Pennsylvania Ave NW Washington, DC.<\/td>\n<td>20500<\/td>\n<td>US<\/td>\n<td>03\/2030<\/td>\n<td>7373<\/td>\n<\/tr>\n<tr>\n<td>374251021090003<\/td>\n<td>Amex<\/td>\n<td>1<\/td>\n<td>Infinite Loop Cupertino, CA.<\/td>\n<td>95014<\/td>\n<td>US<\/td>\n<td>03\/2030<\/td>\n<td>7373<\/td>\n<\/tr>\n<tr>\n<td>374101012180018<\/td>\n<td>Amex<\/td>\n<td>10<\/td>\n<td>Downing Street, London.<\/td>\n<td>SW1A 2AA<\/td>\n<td>GB<\/td>\n<td>03\/2030<\/td>\n<td>7373<\/td>\n<\/tr>\n<tr>\n<td>374251033270007<\/td>\n<td>Amex<\/td>\n<td>8-10<\/td>\n<td>Broadway, Westminster, London.<\/td>\n<td>SW1H 0BG<\/td>\n<td>GB<\/td>\n<td>03\/2030<\/td>\n<td>7373<\/td>\n<\/tr>\n<tr>\n<td>4400000000000008<\/td>\n<td>Visa<\/td>\n<td>1<\/td>\n<td>Infinite Loop Cupertino, CA.<\/td>\n<td>95014<\/td>\n<td>US<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<\/tr>\n<tr>\n<td>4444333322221111<\/td>\n<td>Visa<\/td>\n<td>8-10<\/td>\n<td>Broadway, Westminster, London.<\/td>\n<td>SW1H 0BG<\/td>\n<td>GB<\/td>\n<td>03\/2030<\/td>\n<td>737<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<ol>\n<li>Make a test card payment.<\/li>\n<li>Get the AVS result in your API response or webhook for the corresponding PSP reference.<br \/>\nFor an overview of the different AVS responses and codes, see:\n<ul>\n<li><a href=\"\/risk-management\/avs-checks\/#avs-mapping-table\">AVS responses<\/a> for online payments.<\/li>\n<li><a href=\"\/point-of-sale\/mail-and-telephone-order-moto\/avs-responses-pos\">AVS responses<\/a> for in-person payments.<\/li>\n<\/ul><\/li>\n<\/ol>\n<h2>Auto Rescue<\/h2>\n<p>For shopper-not-present transactions, like subscription renewal payments, the <a href=\"\/online-payments\/auto-rescue\/\">Auto Rescue<\/a> feature determines when to automatically retry failed payments. Test it by enabling it in your test Customer Area and triggering the following scenarios.<\/p>\n<h3>Retry attempts<\/h3>\n<p>In these test scenarios, the payment is refused, so Auto Rescue makes retry attempts. To trigger specific retry scenarios, include the following values in the <code>merchantReference<\/code> field when making a test  <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> request:<\/p>\n<table>\n<thead>\n<tr>\n<th>Scenario<\/th>\n<th>Merchant order reference value<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>The first retry attempt succeeds.<\/td>\n<td><span translate=\"no\"><strong>AutoRescueSuccessfulFirst<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td>The first retry attempt fails. The second retry attempt is successful.<\/td>\n<td><span translate=\"no\"><strong>AutoRescueSuccessfulSecond<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td>All retry attempts fail.<\/td>\n<td><span translate=\"no\"><strong>AutoRescueFailed<\/strong><\/span><\/td>\n<\/tr>\n<tr>\n<td>The payment is refused because of fraud, so there's no retry attempt.<\/td>\n<td><span translate=\"no\"><strong>AutoRescueFraud<\/strong><\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>For scenarios where Auto Rescue is triggered, you get an <span translate=\"no\"><strong>AUTHORISATION<\/strong><\/span> webhook for each payment retry. The <code>success<\/code> field in the webhook shows if the retry was successful.<\/p>\n<h3>Failed retry attempt that sends a payment link<\/h3>\n<p>If you enabled sending a Pay by Link payment link if Auto Rescue retry attempts fail.<\/p>\n<p>In this scenario, the payment is refused, so Auto Rescue makes retry attempts. All retry attempts fail, so a <a href=\"\/online-payments\/auto-rescue\/cards\/#send-a-payment-link\">Pay By Link payment link is sent<\/a>.<\/p>\n<ol>\n<li>Make a  <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> request including <code>merchantReference<\/code>: <span translate=\"no\"><strong>AutoRescueFailed<\/strong><\/span>.<\/li>\n<li>Get the <span translate=\"no\"><strong>AUTORESCUE<\/strong><\/span> webhook on your server.<\/li>\n<li>Go to the payment link URL from <code>paymentLink.url<\/code> from the webhook.<\/li>\n<li>Complete the Pay by Link test payment.<\/li>\n<li>Get the <a href=\"\/development-resources\/webhooks\/webhook-types\/#default-event-codes\"><strong>AUTHORISATION<\/strong> webhook<\/a> on your server. It includes the status of the payment.<\/li>\n<\/ol>","url":"https:\/\/docs.adyen.com\/development-resources\/testing\/risk-features","articleFields":{"description":"Test risk features with your integration and troubleshoot issues before it goes live.","cache_enable":false},"algolia":{"url":"https:\/\/docs.adyen.com\/development-resources\/testing\/risk-features","title":"Testing risk features","content":"Chargebacks\nIf a shopper disputes a transaction, it can become a chargeback.\nTo test the dispute flow, you can simulate a chargeback to test chargeback scenarios.\nYou can then use your Customer Area or the Disputes API to handle the simulated dispute.\nRisk management\nWhen you use RevenueProtect, and have turned on and configured risk rules, you can test if the risk rule triggers.\nAddress Verification System (AVS)\nYou have to include billing address details in the payment request to enable and test AVS.\nTo test AVS, you can use the following AVS test cards and billing addresses:\n\n\n\nCard Number\nCard Type\nHouse Number\nAddress\nZIP Code\nCountry\/region\nExpiry Date\nSecurity Code (CVV\/CVC\/CID)\n\n\n\n\n5555555555554444\nMastercard\n10\nDowning Street, London.\nSW1A 2AA\nGB\n03\/2030\n737\n\n\n374251018720018\nAmex\n1600\nPennsylvania Ave NW Washington, DC.\n20500\nUS\n03\/2030\n7373\n\n\n374251021090003\nAmex\n1\nInfinite Loop Cupertino, CA.\n95014\nUS\n03\/2030\n7373\n\n\n374101012180018\nAmex\n10\nDowning Street, London.\nSW1A 2AA\nGB\n03\/2030\n7373\n\n\n374251033270007\nAmex\n8-10\nBroadway, Westminster, London.\nSW1H 0BG\nGB\n03\/2030\n7373\n\n\n4400000000000008\nVisa\n1\nInfinite Loop Cupertino, CA.\n95014\nUS\n03\/2030\n737\n\n\n4444333322221111\nVisa\n8-10\nBroadway, Westminster, London.\nSW1H 0BG\nGB\n03\/2030\n737\n\n\n\n\nMake a test card payment.\nGet the AVS result in your API response or webhook for the corresponding PSP reference.\nFor an overview of the different AVS responses and codes, see:\n\nAVS responses for online payments.\nAVS responses for in-person payments.\n\n\nAuto Rescue\nFor shopper-not-present transactions, like subscription renewal payments, the Auto Rescue feature determines when to automatically retry failed payments. Test it by enabling it in your test Customer Area and triggering the following scenarios.\nRetry attempts\nIn these test scenarios, the payment is refused, so Auto Rescue makes retry attempts. To trigger specific retry scenarios, include the following values in the merchantReference field when making a test  \/payments request:\n\n\n\nScenario\nMerchant order reference value\n\n\n\n\nThe first retry attempt succeeds.\nAutoRescueSuccessfulFirst\n\n\nThe first retry attempt fails. The second retry attempt is successful.\nAutoRescueSuccessfulSecond\n\n\nAll retry attempts fail.\nAutoRescueFailed\n\n\nThe payment is refused because of fraud, so there's no retry attempt.\nAutoRescueFraud\n\n\n\nFor scenarios where Auto Rescue is triggered, you get an AUTHORISATION webhook for each payment retry. The success field in the webhook shows if the retry was successful.\nFailed retry attempt that sends a payment link\nIf you enabled sending a Pay by Link payment link if Auto Rescue retry attempts fail.\nIn this scenario, the payment is refused, so Auto Rescue makes retry attempts. All retry attempts fail, so a Pay By Link payment link is sent.\n\nMake a  \/payments request including merchantReference: AutoRescueFailed.\nGet the AUTORESCUE webhook on your server.\nGo to the payment link URL from paymentLink.url from the webhook.\nComplete the Pay by Link test payment.\nGet the AUTHORISATION webhook on your server. It includes the status of the payment.\n","type":"page","locale":"en","boost":17,"hierarchy":{"lvl0":"Home","lvl1":"Development resources","lvl2":"Testing your online payments integration","lvl3":"Testing risk features"},"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\/risk-features"},"levels":4,"category":"Development Resources","category_color":"green","tags":["Testing","features"]}}
