Access Worldpay
/
Testing

Last Updated: 21 November 2024 | Change Log

Testing

Test your Payments integration in the Try environment using a combination of cardholder and card number test values. Send requests and see simulated responses.

As you can enable features such as 3DS, FraudSight or auto settlement, the outcome of the scenarios below changes based on the configuration you have in place.

Using Worldpay Tokens

If you're creating tokens containing the test card numbers, you must delete the token before creating another with the same PAN. You are prevented from creating another token using the same PAN. As an alternative, you can also change the tokenCreation.namespace used as part of the token creation.

Test Scenarios

  • To simulate the different values (e.g. cvc, avs, response code) the issuer can return in the payment response see Isser Response Test Values
  • All unknown cardHolderName values (e.g. Bob) treat the payment as authorized by default
Test ScenarioDescriptioncardHolderNamecardNumber
Outcomes
AuthorizedAuthorized by IssuerAUTHORISEDSchemes:
  • Visa: 4000000000002701
  • Mastercard: 5200000000002235
  • AMEX: 340000000002708
  • Discover/Diners: 6011000000002117
  • JCB: 3338000000000296
authorized or sentForSettlement (if settlement.auto is enabled)
RefusedRefused by IssuerREFUSEDSchemes:
  • Visa: 4000000000002701
  • Mastercard: 5200000000002235
  • AMEX: 340000000002708
  • Discover/Diners: 6011000000002117
  • JCB: 3338000000000296
refused

Issuer Response Test Values

Input these magic values in your paymentInstrument.cardHolderName parameter.

Magic valueResult codeResult description
AUTHORISEDN/AAUTHORISED
ERRORN/AERROR
REFUSEDN/AREFUSED
REFUSED44HOLD CARD
REFUSED55REFUSED
REFUSED88APPROVE AFTER IDENTIFICATION
REFUSED1313INVALID AMOUNT
REFUSED1515INVALID CARD ISSUER
REFUSED1717ANNULATION BY CLIENT
REFUSED2828ACCESS DENIED
REFUSED2929IMPOSSIBLE REFERENCE NUMBER
REFUSED3333CARD EXPIRED
REFUSED3434FRAUD SUSPICION
REFUSED3838SECURITY CODE EXPIRED
REFUSED4141LOST CARD
REFUSED4343STOLEN CARD, PICK UP
REFUSED5151LIMIT EXCEEDED
REFUSED5555INVALID SECURITY CODE
REFUSED5656UNKNOWN CARD
REFUSED5757ILLEGAL TRANSACTION
REFUSED6262RESTRICTED CARD
REFUSED6363SECURITY RULES VIOLATED
REFUSED7575SECURITY CODE INVALID
REFUSED7676CARD BLOCKED
REFUSED8585REJECTED BY CARD ISSUER
SOFT_DECLINED65AUTHENTICATION REQUESTED

3DS Test Forms

Quickly test the frontend/clientside steps in the 3DS integration using the forms below:

Test device data form

The form below allows you to submit the 3DS device data details provided in the API response and receive the sessionId/collectionReference back for use in the /3dsDeviceData request. This is useful if using tools such as postman/insomnia to test your integration.

Test challenge form

The form below allows you to submit the 3DS challenge details provided in the API response and display the issuer challenge. This is useful if using tools such as postman/insomnia to test your integration.