Worldpay Access test cards

Use these details to try payments in a Worldpay Access sandbox (test) account. They work only in the sandbox: never use them in live, and never put real card or bank details into a sandbox.

Worldpay’s sandbox is called the Try environment. Most results are set by “magic values”: special text that reaches Worldpay as the cardholder name, the CVC or the postcode.

How to choose a test result

The card number sets the card brand and, with 3D Secure, the authentication result. The cardholder name, the CVC and the postcode set the rest (Card payment testing).
The cardholder name: we send Worldpay the name on the card if one is given, otherwise the customer’s first and last name joined with a space, and in both cases remove every character that isn’t a letter or a space. Enter the value, for example REFUSED, as the customer’s first name and leave the last name empty (or the other way round): if both are filled in, Worldpay receives both and the value won’t match. Worldpay’s coded values, such as REFUSED51 and SOFT_DECLINED, can’t be used here, because Worldpay receives them as REFUSED and SOFTDECLINED (Issuer response test values).
The CVC you enter sets the CVC check result (CVC test values).
The postcode sets the address check result (AVS test values). Set Address Verification to Zip Only or Full Address in the Worldpay Access connection settings: with Disabled, the default, the checkout doesn’t ask for a postcode and we send no address.
For 3D Secure, switch on Enable 3DS in the connection settings (3D Secure must also be enabled on your Worldpay account), and use the 3D Secure card numbers with an ordinary customer name (3DS Testing).

Cards

Use any expiry date up to seven years in the future. The test cards have no registered address or CVC: use the CVC and postcode values under Address and CVC checks to test those checks.

Successful payments

Worldpay lists AUTHORISED as the name for an approved payment: enter it as the customer’s first name, with the last name empty.

Card	Number	Notes
Visa	`4444 3333 2222 1111`
Visa	`4911 8300 0000 0`	Used in our own tests
Visa (debit)	`4462 0300 0000 0000`
Mastercard	`5555 5555 5555 4444`
Mastercard	`2221 0000 0000 0009`
Mastercard (debit)	`5163 6136 1361 3613`
Maestro	`6759 6498 2643 8453`
American Express	`3434 343434 34343`
Discover / Diners Club	`6011 0004 0000 0000`
JCB	`3528 0007 0000 0000`

Worldpay’s page doesn’t say what an ordinary name gives. Our own tests with Worldpay’s sandbox are approved with an ordinary customer name, and with no name at all, using card 4911 8300 0000 0, CVC 555 and postcode AAAA.

Declines and errors

Enter one of these values as the customer’s first name, with the last name empty, and use any test card above.

Number or trigger	Result
Name `REFUSED`	Refused
Name `ERROR`	Error

Worldpay lists more values on its Card payment testing page, including refusals with a reason code, such as REFUSED51 (limit exceeded), REFUSED33 (card expired) and SOFT_DECLINED (authentication requested). These can’t be used here: we remove digits and underscores from the name, so Worldpay receives REFUSED (a plain refusal) or SOFTDECLINED.

3D Secure

For 3D Secure tests use these card numbers, not the ones above: Worldpay says any other number makes the challenge fail to load. Use an ordinary customer name, such as Bob Smith, not a magic value, and switch on Enable 3DS in the connection settings. Each row gives the Visa and Mastercard numbers; Worldpay lists the matching American Express, Discover / Diners Club and JCB numbers on its 3DS Testing page.

Number	Result
`4000 0000 0000 2701` or `5200 0000 0000 2235`	Frictionless: authenticated
`4000 0000 0000 2925` or `5200 0000 0000 2276`	Frictionless: authentication failed, no challenge offered
`4000 0000 0000 2719` or `5200 0000 0000 2482`	Frictionless: issuer doesn’t support 3D Secure, so authentication is stood in for
`4000 0000 0000 2313` or `5200 0000 0000 2268`	Authentication unavailable at the issuer
`4000 0000 0000 2537` or `5200 0000 0000 2185`	Authentication rejected by the issuer, no challenge offered
`4000 0000 0000 2990` or `5200 0000 0000 2409`	Authentication unavailable: system error
`4000 0000 0000 2446` or `5200 0000 0000 2037`	Error while attempting authentication
`4000 0000 0000 2354` or `5200 0000 0000 2326`	Authentication timeout
`4000 0000 0000 2503` or `5200 0000 0000 2151`	Challenge, answered correctly: authenticated
`4000 0000 0000 2370` or `5200 0000 0000 2490`	Challenge, answered incorrectly: authentication failed
`4000 0000 0000 2420` or `5200 0000 0000 2664`	Challenge, then the authentication result can’t be retrieved
`4000 0000 0000 2644` or `5200 0000 0000 2656`	Challenge, then an error during verification
`4000 0000 0000 2560` or `5200 0000 0000 2508`	Authentication bypassed

Address and CVC checks

CVC: enter one of these as the CVC. Worldpay returns a CVC result only when the check finds a problem.

Value	Result
`555` (`6666` for American Express)	CVC matched: approved
`444` (`4444` for American Express)	CVC not matched: failed
`111` (`1111` for American Express)	Not sent to the acquirer
`222` (`2222` for American Express)	No response from the acquirer
`333` (`3333` for American Express)	Not checked by the acquirer
Left blank	Not supplied by the shopper

Address (AVS): enter one of these as the postcode. The checkout asks for a postcode only when Address Verification is set to Zip Only or Full Address in the connection settings. Worldpay returns an AVS result only when the check finds a problem.

Value	Result
`AAAA`	Postcode and address matched
`BBBB`	Postcode matched; address not checked
`CCCC`	Postcode matched; address not matched
`DDDD`	Address matched; postcode not checked
`FFFF`	Address matched; postcode not matched
`GGGG`	Postcode not checked; address not matched
`IIII`	Address not checked; postcode not matched
`JJJJ`	Postcode and address not matched
`EEEE`	Postcode and address not checked
`HHHH`	Postcode and address not supplied

Was this page helpful?