Chargebacks
If a shopper disputes a transaction, it can become a chargeback.
To test the dispute flow, you can simulate a chargeback to test chargeback scenarios.
You can then use your Customer Area or the Disputes API to handle the simulated dispute.
Risk management
When you use RevenueProtect, and have turned on and configured risk rules, you can test if the risk rule triggers.
Address Verification System (AVS)
You have to include billing address details in the payment request to enable and test AVS.
To test AVS, you can use the following AVS test cards and billing addresses:
| Card Number | Card Type | House Number | Address | ZIP Code | Country | Expiry Date | Security Code (CVV/CVC/CID) |
|---|---|---|---|---|---|---|---|
| 5555555555554444 | Mastercard | 10 | Downing Street, London. | SW1A 2AA | GB | 03/2030 | 737 |
| 374251018720018 | Amex | 1600 | Pennsylvania Ave NW Washington, DC. | 20500 | US | 03/2030 | 7373 |
| 374251021090003 | Amex | 1 | Infinite Loop Cupertino, CA. | 95014 | US | 03/2030 | 7373 |
| 374101012180018 | Amex | 10 | Downing Street, London. | SW1A 2AA | GB | 03/2030 | 7373 |
| 374251033270007 | Amex | 8-10 | Broadway, Westminster, London. | SW1H 0BG | GB | 03/2030 | 7373 |
| 4400000000000008 | Visa | 1 | Infinite Loop Cupertino, CA. | 95014 | US | 03/2030 | 737 |
| 4444333322221111 | Visa | 8-10 | Broadway, Westminster, London. | SW1H 0BG | GB | 03/2030 | 737 |
- Make a test card payment.
- Get the AVS result in your API response or webhook for the corresponding PSP reference.
For an overview of the different AVS responses and codes, see:- AVS responses for online payments.
- AVS responses for in-person payments.
Auto Rescue
For 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.
Retry attempts
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 merchantReference field when making a test /payments request:
| Scenario | Merchant order reference value |
|---|---|
| The first retry attempt succeeds. | AutoRescueSuccessfulFirst |
| The first retry attempt fails. The second retry attempt is successful. | AutoRescueSuccessfulSecond |
| All retry attempts fail. | AutoRescueFailed |
| The payment is refused because of fraud, so there's no retry attempt. | AutoRescueFraud |
For 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.
Failed retry attempt that sends a payment link
If you enabled sending a Pay by Link payment link if Auto Rescue retry attempts fail.
In 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.
- Make a /payments request including
merchantReference: AutoRescueFailed. - Get the AUTORESCUE webhook on your server.
- Go to the payment link URL from
paymentLink.urlfrom the webhook. - Complete the Pay by Link test payment.
- Get the AUTHORISATION webhook.