How Worldpay test cards work
These numbers are for the Try (test) environment of the Access Worldpay Card Payments API. You can use any expiry date up to seven years ahead. The cards have no CVC, issue number or registered address of their own; the values you send decide the CVC and AVS results.
Worldpay simulates outcomes with magic values. Put REFUSED51 in paymentInstrument.cardHolderName to get refusal code 51 (limit exceeded), 444 in the cvc field for a failed CVC check, or CCCC in postalCode for an address mismatch. Magic values can be combined, but a CVC value on its own never produces an issuer refusal.
For 3-D Secure flows (the 3DS API together with the Card Payments API), Worldpay asks you to use the cards on its separate 3DS testing page; with the cards below, the challenge display fails to load. Older Worldpay platforms such as the Worldpay Corporate Gateway (WPG) have their own test values, so check which platform your account is on.
Issuer responses: magic values in cardHolderName
Send one of these values as paymentInstrument.cardHolderName with any test card to get that issuer response. Worldpay documents more codes, including raw scheme codes and Mastercard refusal advice.
| cardHolderName | Code | Result |
|---|---|---|
| AUTHORISED | – | Authorized |
| REFUSED | – | Refused |
| ERROR | – | Error |
| REFUSED5 | 5 | Refused |
| REFUSED13 | 13 | Invalid amount |
| REFUSED33 | 33 | Card expired |
| REFUSED34 | 34 | Fraud suspicion |
| REFUSED41 | 41 | Lost card |
| REFUSED43 | 43 | Stolen card, pick up |
| REFUSED51 | 51 | Limit exceeded |
| REFUSED55 | 55 | Invalid security code |
| REFUSED62 | 62 | Restricted card |
| REFUSED76 | 76 | Card blocked |
| SOFT_DECLINED | 65 | Authentication requested (soft decline) |
CVC and AVS magic values
Put these values in the cvc field (or postalCode for AVS). The result appears in the riskFactors object; nothing is returned when the check passes.
| Value | Result |
|---|---|
| (empty) | CVC not supplied by shopper |
| 111 | CVC not sent to acquirer |
| 222 | No response from acquirer |
| 333 | Not checked by acquirer |
| 444 | CVC failed (not_matched) |
| 555 | Approved, no riskFactors |
| 1111 – 6666 | Same cases for American Express (6666 = approved, 5555 = unknown) |
| AAAA | AVS: postcode and address matched |
| CCCC | AVS: postcode matched, address not matched |
| FFFF | AVS: address matched, postcode not matched |
| JJJJ | AVS: neither postcode nor address matched |
Testing Worldpay payments step by step
- Get Try credentials for Access Worldpay and point your integration at the Try environment.
- Authorize a payment with
4444 3333 2222 1111and check the outcome. - Send cardHolderName values from the issuer table to cover refusals such as 51 (limit exceeded) and 33 (card expired).
- Test CVC handling with
444and address checks with the AVS postal-code values. - Use the cards from Worldpay’s 3DS testing page for authentication flows.
Common errors and fixes
- 3DS challenge doesn’t load
- You used a normal test card. 3DS flows need the cards from the 3DS testing page.
- CVC value doesn’t refuse the payment
- CVC magic values only change the riskFactors result. Add an issuer magic value in cardHolderName.
- Raw scheme code doesn’t match
- Raw response codes are scheme-specific: use a Visa card for Visa codes and a Mastercard card for Mastercard codes.
Sources
Every number on this page was copied from Worldpay’s official documentation and passes the Luhn check. Checked October 2026; gateways change their test data from time to time, so if a number stops working, check the source:
Frequently asked questions
What is the Worldpay test card number?
4444 3333 2222 1111 (Visa) or 5555 5555 5555 4444 (Mastercard) in the Try environment, with any expiry date up to seven years ahead.
How do I simulate a refused payment in Worldpay?
Send a magic value as the cardholder name, for example REFUSED, REFUSED51 (limit exceeded) or REFUSED33 (card expired).
Which CVC fails in the Worldpay Try environment?
444 (or 4444 for American Express) returns a failed CVC check; 555 passes.
Can I use these test cards on another gateway?
Usually not. Each gateway only recognises its own documented test numbers in its own sandbox. Some numbers, such as 4111 1111 1111 1111, appear in several lists, but the results they trigger differ. For format-only testing on your own forms, use our card generator.