Worldpay test cards by scenario
Name-driven: the cardholder name decides the issuer response, from AUTHORISED and REFUSED to coded refusals such as REFUSED51. In the Payments API, the card number decides the 3D Secure outcome. Where a cell names a trigger, use it with any of Worldpay's cards below. On Flint, each scenario is one card number with any future expiry, any 3-digit CVC, and any ZIP.
| Scenario | Worldpay | Flint |
|---|---|---|
| Successful payment | 4444 3333 2222 1111cardholder name AUTHORISED | 4242 4242 4242 4242any future expiry, any CVC, any ZIP |
| Generic decline | Cardholder name REFUSED | 4000 0000 0000 0002 |
| Insufficient funds | Cardholder name REFUSED51 | 4000 0000 0000 9995 |
| Lost or stolen card | Cardholder name REFUSED41 (lost) or REFUSED43 (stolen) | 4000 0000 0000 99874000 0000 0000 9979lost, stolen |
| Expired card | Cardholder name REFUSED33 | 4000 0000 0000 0069 |
| Incorrect CVC | Cardholder name REFUSED55 | 4000 0000 0000 0127 |
| 3D Secure challenge | 4000 0000 0000 2503Payments API | 4000 0025 0000 3155 |
| 3D Secure authentication fails | 4000 0000 0000 2370Payments API | 4000 0000 0000 3220fail the challenge |
| Card saves, then charges fail | Not documented | 4000 0000 0000 0341 |
| Dispute or chargeback | Not documented | 4000 0000 0000 02594000 0000 0000 1976fraudulent, inquiry |
Declines, 3D Secure, and disputes
How Worldpay triggers declines
Worldpay's cards authorize; the cardholder name decides the issuer response. REFUSED refuses, ERROR returns an error, and REFUSED plus a code returns that refusal: REFUSED51 for limit exceeded, REFUSED33 for an expired card, REFUSED41 for a lost card, and REFUSED55 for an invalid security code. Any unknown name authorizes.
How Worldpay tests 3D Secure
In the Payments API, the card number decides the 3D Secure outcome: 4000 0000 0000 2503 passes a challenge, 4000 0000 0000 2370 fails one, and 4000 0000 0000 2925 fails without a challenge, with a card per scheme for each. In the 3DS API, the cardholder name decides it, such as 3ds2-challenge-identified.
How Worldpay simulates disputes
Worldpay's testing docs document no dispute or chargeback simulation in the Try environment.