Skip to content

Worldpay test cards

Every card number in Access Worldpay's testing docs for the Payments API, Card Payments API, and 3DS API, with the cardholder name magic values that force each refusal and the CVC, AVS, and refund values.
Verified against official documentationReviewed Send a correction (opens in a new tab)

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.

ScenarioWorldpayFlint
Successful payment4444 3333 2222 1111cardholder name AUTHORISED4242 4242 4242 4242any future expiry, any CVC, any ZIP
Generic declineCardholder name REFUSED4000 0000 0000 0002
Insufficient fundsCardholder name REFUSED514000 0000 0000 9995
Lost or stolen cardCardholder name REFUSED41 (lost) or REFUSED43 (stolen)4000 0000 0000 99874000 0000 0000 9979lost, stolen
Expired cardCardholder name REFUSED334000 0000 0000 0069
Incorrect CVCCardholder name REFUSED554000 0000 0000 0127
3D Secure challenge4000 0000 0000 2503Payments API4000 0025 0000 3155
3D Secure authentication fails4000 0000 0000 2370Payments API4000 0000 0000 3220fail the challenge
Card saves, then charges failNot documented4000 0000 0000 0341
Dispute or chargebackNot documented4000 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.

Look up a Worldpay test card

Paste with or without spaces or dashes. Matching runs in your browser, and the URL never holds a full card number unless it's a documented test card.

71 cards and 39 trigger values from Worldpay

Comparing processors? The full test card lookup checks a number against Flint, Stripe, Adyen, Braintree, PayPal, Square, Checkout.com, and Authorize.net at once.

Every Worldpay test card#

71 cards, 39 triggers

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.

Expiry
Any date up to seven years ahead
CVC
Not required; magic values set the CVC result
Postal code
Not required; magic values set the AVS result
  • The cards work only in Worldpay's Try environment.
  • AUTHORISED or any unknown cardholder name, such as Bob, authorizes; REFUSED refuses; REFUSED plus a code, such as REFUSED33, returns that refusal code.
  • For 3D Secure, use the 3D Secure test cards, or the challenge display fails to load.
  • A token holding a test card number blocks a second token for the same number: delete the first token, or change the token namespace.
  • Raw response and refusal advice values need a card from the matching scheme, such as a Mastercard for refusal advice.

Payments API: payment and FraudSight cards

7 cardsWorldpay docs
  • Visa

    Success3DS frictionless
    #

    Authorizes with cardholder name AUTHORISED and refuses with REFUSED. With 3D Secure enabled, authentication is frictionless and succeeds.

  • Mastercard

    Success3DS frictionless
    #

    Authorizes with cardholder name AUTHORISED and refuses with REFUSED. With 3D Secure enabled, authentication is frictionless and succeeds.

  • American Express

    Success3DS frictionless
    #

    Authorizes with cardholder name AUTHORISED and refuses with REFUSED. With 3D Secure enabled, authentication is frictionless and succeeds.

  • Discover, also Diners

    Success3DS frictionless
    #

    Authorizes with cardholder name AUTHORISED and refuses with REFUSED. With 3D Secure enabled, authentication is frictionless and succeeds.

  • JCB

    Success3DS frictionless
    #

    Authorizes with cardholder name AUTHORISED and refuses with REFUSED. With 3D Secure enabled, authentication is frictionless and succeeds.

  • UnionPay, ExpressPay

    Success3DS frictionless
    #

    Authorizes with cardholder name AUTHORISED and refuses with REFUSED. With 3D Secure enabled, authentication is frictionless and succeeds.

  • Cartes Bancaires, Co-branded with Visa

    Success
    #

    Authorizes with cardholder name AUTHORISED and refuses with REFUSED. Worldpay lists Cartes Bancaires 3D Secure as supported but not yet testable.

Payments API: 3D Secure challenge succeeds

6 cardsWorldpay docs
  • Visa

    3DS challenge
    #

    The issuer challenges and the customer passes: 3dsDeviceDataRequired, then 3dsChallenged, then authorized with cardholder name AUTHORISED.

  • Mastercard

    3DS challenge
    #

    The issuer challenges and the customer passes: 3dsDeviceDataRequired, then 3dsChallenged, then authorized with cardholder name AUTHORISED.

  • American Express

    3DS challenge
    #

    The issuer challenges and the customer passes: 3dsDeviceDataRequired, then 3dsChallenged, then authorized with cardholder name AUTHORISED.

  • Discover, also Diners

    3DS challenge
    #

    The issuer challenges and the customer passes: 3dsDeviceDataRequired, then 3dsChallenged, then authorized with cardholder name AUTHORISED.

  • JCB

    3DS challenge
    #

    The issuer challenges and the customer passes: 3dsDeviceDataRequired, then 3dsChallenged, then authorized with cardholder name AUTHORISED.

  • UnionPay, ExpressPay

    3DS challenge
    #

    The issuer challenges and the customer passes: 3dsDeviceDataRequired, then 3dsChallenged, then authorized with cardholder name AUTHORISED.

Payments API: 3D Secure fails without a challenge

8 cardsWorldpay docs
  • Visa

    3DS fails
    #

    The issuer fails authentication without a challenge: 3dsDeviceDataRequired, then 3dsAuthenticationFailed. Any cardholder name.

  • Mastercard

    3DS fails
    #

    The issuer fails authentication without a challenge: 3dsDeviceDataRequired, then 3dsAuthenticationFailed. Any cardholder name.

  • American Express

    3DS fails
    #

    The issuer fails authentication without a challenge: 3dsDeviceDataRequired, then 3dsAuthenticationFailed. Any cardholder name.

  • Discover, also Diners

    3DS fails
    #

    The issuer fails authentication without a challenge: 3dsDeviceDataRequired, then 3dsAuthenticationFailed. Any cardholder name.

  • JCB

    3DS fails
    #

    The issuer fails authentication without a challenge: 3dsDeviceDataRequired, then 3dsAuthenticationFailed. Any cardholder name.

  • Cartes Bancaires, Co-branded with Visa

    3DS fails
    #

    The issuer fails authentication without a challenge: 3dsDeviceDataRequired, then 3dsAuthenticationFailed. Any cardholder name.

  • Cartes Bancaires, Co-branded with Mastercard

    3DS fails
    #

    The issuer fails authentication without a challenge: 3dsDeviceDataRequired, then 3dsAuthenticationFailed. Any cardholder name.

  • UnionPay, ExpressPay

    3DS fails
    #

    The issuer fails authentication without a challenge: 3dsDeviceDataRequired, then 3dsAuthenticationFailed. Any cardholder name.

Payments API: 3D Secure challenge fails

8 cardsWorldpay docs
  • Visa

    3DS fails
    #

    The issuer challenges and the customer fails: 3dsChallenged, then 3dsAuthenticationFailed. Any cardholder name.

  • Mastercard

    3DS fails
    #

    The issuer challenges and the customer fails: 3dsChallenged, then 3dsAuthenticationFailed. Any cardholder name.

  • American Express

    3DS fails
    #

    The issuer challenges and the customer fails: 3dsChallenged, then 3dsAuthenticationFailed. Any cardholder name.

  • Discover, also Diners

    3DS fails
    #

    The issuer challenges and the customer fails: 3dsChallenged, then 3dsAuthenticationFailed. Any cardholder name.

  • JCB

    3DS fails
    #

    The issuer challenges and the customer fails: 3dsChallenged, then 3dsAuthenticationFailed. Any cardholder name.

  • Cartes Bancaires, Co-branded with Visa

    3DS fails
    #

    The issuer challenges and the customer fails: 3dsChallenged, then 3dsAuthenticationFailed. Any cardholder name.

  • Cartes Bancaires, Co-branded with Mastercard

    3DS fails
    #

    The issuer challenges and the customer fails: 3dsChallenged, then 3dsAuthenticationFailed. Any cardholder name.

  • UnionPay, ExpressPay

    3DS fails
    #

    The issuer challenges and the customer fails: 3dsChallenged, then 3dsAuthenticationFailed. Any cardholder name.

Payments API: 3D Secure unavailable

8 cardsWorldpay docs
  • Visa

    Other 3DS result
    #

    Authentication is unavailable because of a downstream error: 3dsUnavailable.

  • Mastercard

    Other 3DS result
    #

    Authentication is unavailable because of a downstream error: 3dsUnavailable.

  • American Express

    Other 3DS result
    #

    Authentication is unavailable because of a downstream error: 3dsUnavailable.

  • Discover, also Diners

    Other 3DS result
    #

    Authentication is unavailable because of a downstream error: 3dsUnavailable.

  • JCB

    Other 3DS result
    #

    Authentication is unavailable because of a downstream error: 3dsUnavailable.

  • Cartes Bancaires, Co-branded with Visa

    Other 3DS result
    #

    Authentication is unavailable because of a downstream error: 3dsUnavailable.

  • Cartes Bancaires, Co-branded with Mastercard

    Other 3DS result
    #

    Authentication is unavailable because of a downstream error: 3dsUnavailable.

  • UnionPay, ExpressPay

    Other 3DS result
    #

    Authentication is unavailable because of a downstream error: 3dsUnavailable.

Payments API: 3D Secure timeout

6 cardsWorldpay docs
  • Visa

    Other 3DS result
    #

    Authentication times out downstream: 3dsUnavailable, or authorized when authenticationOutage is enabled.

  • Mastercard

    Other 3DS result
    #

    Authentication times out downstream: 3dsUnavailable, or authorized when authenticationOutage is enabled.

  • American Express

    Other 3DS result
    #

    Authentication times out downstream: 3dsUnavailable, or authorized when authenticationOutage is enabled.

  • Discover, also Diners

    Other 3DS result
    #

    Authentication times out downstream: 3dsUnavailable, or authorized when authenticationOutage is enabled.

  • JCB

    Other 3DS result
    #

    Authentication times out downstream: 3dsUnavailable, or authorized when authenticationOutage is enabled.

  • UnionPay, ExpressPay

    Other 3DS result
    #

    Authentication times out downstream: 3dsUnavailable, or authorized when authenticationOutage is enabled.

Payments API: 3D Secure bypassed

8 cardsWorldpay docs
  • Visa

    Other 3DS result
    #

    Cardinal Rules Engine configuration bypasses 3D Secure, which needs 3DS premium, and the payment authorizes.

  • Mastercard

    Other 3DS result
    #

    Cardinal Rules Engine configuration bypasses 3D Secure, which needs 3DS premium, and the payment authorizes.

  • American Express

    Other 3DS result
    #

    Cardinal Rules Engine configuration bypasses 3D Secure, which needs 3DS premium, and the payment authorizes.

  • Discover, also Diners

    Other 3DS result
    #

    Cardinal Rules Engine configuration bypasses 3D Secure, which needs 3DS premium, and the payment authorizes.

  • JCB

    Other 3DS result
    #

    Cardinal Rules Engine configuration bypasses 3D Secure, which needs 3DS premium, and the payment authorizes.

  • Cartes Bancaires, Co-branded with Visa

    Other 3DS result
    #

    Cardinal Rules Engine configuration bypasses 3D Secure, which needs 3DS premium, and the payment authorizes.

  • Cartes Bancaires, Co-branded with Mastercard

    Other 3DS result
    #

    Cardinal Rules Engine configuration bypasses 3D Secure, which needs 3DS premium, and the payment authorizes.

  • UnionPay, ExpressPay

    Other 3DS result
    #

    Cardinal Rules Engine configuration bypasses 3D Secure, which needs 3DS premium, and the payment authorizes.

Card Payments API test cards

Show all 19 cards

Worldpay docs

  • Visa

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Visa, 13-digit card

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Visa

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Visa, Debit

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Visa, Debit, 19-digit card

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Visa, Visa Electron, UK only

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Mastercard

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Mastercard

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Mastercard, 2-series

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Mastercard, Debit

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • American Express

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Discover, also Diners

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • JCB

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Maestro

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Cartes Bancaires, Co-branded with Visa

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Cartes Bancaires, Co-branded with Mastercard

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • Cartes Bancaires, Co-branded with Maestro

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • eftpos, Co-branded with Visa

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

  • eftpos, Co-branded with Mastercard

    Success
    #

    Authorizes by default. The cardholder name sets the issuer response, such as REFUSED or REFUSED51.

3DS API test cards

1 cardWorldpay docs
  • Visa, Visa Purchasing

    Other 3DS result
    #

    Listed for the 3DS API with the Card Payments API cards above. The cardholder name sets the 3D Secure outcome, such as 3ds2-challenge-identified.

Trigger values

Show all 39 values

Cardholder names go in paymentInstrument.cardHolderName with any test card; 3D Secure names apply in the 3DS API and FraudSight names in the Payments API. CVC values go in cvc, postal codes in postalCode, and amounts in the payment or partial refund request.

  • Cardholder name

    Success#

    Authorized.

  • Cardholder name

    Generic decline#

    Refused.

  • Cardholder name

    Processing error#

    Returns an error response.

  • Cardholder name

    Generic decline#

    Refused with code 5, REFUSED.

  • Cardholder name

    Insufficient funds#

    Refused with code 51, LIMIT EXCEEDED.

  • Cardholder name

    Expired card#

    Refused with code 33, CARD EXPIRED.

  • Cardholder name

    Lost or stolen#

    Refused with code 41, LOST CARD.

  • Cardholder name

    Lost or stolen#

    Refused with code 43, STOLEN CARD, PICK UP.

  • Cardholder name

    Incorrect CVC#

    Refused with code 55, INVALID SECURITY CODE.

  • Cardholder name

    Incorrect CVC#

    Refused with code 75, SECURITY CODE INVALID.

  • Cardholder name

    Fraud block or review#

    Refused with code 34, FRAUD SUSPICION.

  • Cardholder name

    Other decline#

    Refused with code 4, HOLD CARD.

  • Cardholder name

    Invalid card details#

    Refused with code 13, INVALID AMOUNT.

  • Cardholder name

    Invalid card details#

    Refused with code 15, INVALID CARD ISSUER.

  • Cardholder name

    Invalid card details#

    Refused with code 56, UNKNOWN CARD.

  • Cardholder name

    Other decline#

    Refused with code 57, ILLEGAL TRANSACTION.

  • Cardholder name

    Other decline#

    Refused with code 62, RESTRICTED CARD.

  • Cardholder name

    Other decline#

    Refused with code 63, SECURITY RULES VIOLATED.

  • Cardholder name

    Other decline#

    Refused with code 76, CARD BLOCKED.

  • Cardholder name

    Other decline#

    Refused with code 85, REJECTED BY CARD ISSUER.

  • Cardholder name

    Other decline#

    Refused with code 65, AUTHENTICATION REQUESTED: a soft decline that asks for 3D Secure.

  • Cardholder name (3DS)

    3DS frictionless#

    Frictionless authentication succeeds, with liability shift.

  • Cardholder name (3DS)

    3DS fails#

    Frictionless authentication fails. Don't proceed to authorization.

  • Cardholder name (3DS)

    3DS fails#

    The issuer rejects frictionless authentication. Don't proceed to authorization.

  • Cardholder name (3DS)

    3DS challenge#

    The customer completes the challenge and is authenticated, with liability shift. Any unrecognized name, such as Bob Smith, behaves the same.

  • Cardholder name (3DS)

    3DS fails#

    The customer enters incorrect challenge details: authenticationFailed.

  • Cardholder name (3DS)

    Other 3DS result#

    Authentication is unavailable, with no liability shift.

  • Cardholder name (3DS)

    Other 3DS result#

    The 3D Secure check is bypassed.

  • Cardholder name (FraudSight)

    Fraud block or review#

    FraudSight rates the payment highRisk and stops it: fraudHighRisk, unless fraud.silentMode is true.

  • Cardholder name (FraudSight)

    Fraud block or review#

    FraudSight flags the payment for review, and the payment proceeds.

  • CVC

    CVC or address check#

    The CVC check fails: riskFactors returns cvc not_matched. Use 4444 for American Express.

  • CVC

    CVC or address check#

    The CVC check is approved, so no riskFactors return. Use 6666 for American Express.

  • Postal code

    CVC or address check#

    Postal code and address match, so no riskFactors return.

  • Postal code

    CVC or address check#

    Postal code matches; address doesn't: avs not_matched for the address.

  • Postal code

    CVC or address check#

    Address matches; postal code doesn't: avs not_matched for the postal code.

  • Postal code

    CVC or address check#

    Neither postal code nor address matches.

  • Partial refund amount

    Refund behavior#

    The refund request returns 202, then a refundFailed event arrives with refusal code 5, Do not honor.

  • Partial refund amount

    Refund behavior#

    An offline refund: the event is sentForRefund with no refund object.

  • Amount

    Other#

    Partially authorized: totalAuthorized is 123 of the 1706 requested.

Not in Worldpay's docs

  • Dispute or chargeback simulation in the Try environment.
  • A card that saves, then fails on later charges.

The same tests on Flint

On Flint, each decline reason is a card number of its own, so tests need no magic names, and dispute cards open a dispute after the payment, and POST /v1/disputes/{dispute_id}/simulate rules on it.

Flint test cards#

16 cards, 5 triggers

One rule for every card: any future expiry, any 3-digit CVC, any ZIP. Flint processes cards on Stripe, so every Stripe test card also works in a Flint sandbox, with no Stripe account to set up.

Expiry
Any future date
CVC
Any 3 digits
Postal code
Any ZIP code, such as 44444
  • The sandbox is free and needs no credit card. Every test key is bound to its own sandbox, and test and live traffic share one host: the key prefix decides the mode.
  • A decline never ends a checkout session. The buyer sees the failure inline and retries, and the order keeps its outstanding balance until a payment succeeds.
  • From a test suite, pay an order with a test token such as pm_card_visa instead of a card number; a declined token still returns 200 with the attempt failed.

Test cards

9 cardsFlint guide
  • Visa

    Success
    #

    Payment succeeds and the order becomes paid. Use it for card setup and renewals that succeed.

  • Visa

    3DS challenge3DS fails
    #

    Checkout opens a 3D Secure challenge. Complete it and the payment succeeds; fail it and the payment declines. The pay API returns requires_action until the browser finishes the challenge.

  • Visa

    3DS challenge3DS fails
    #

    3D Secure challenge. Complete it and resume, and the attempt succeeds; fail it and resume, and the attempt ends failed with authentication_required.

  • Visa

    Insufficient funds
    #

    Declined with insufficient_funds. Checkout shows the failure and the buyer can retry; the order stays open and unpaid.

  • Visa

    Generic decline
    #

    Declined with card_declined. The order stays open, and the buyer can retry in place.

  • Visa

    Expired card
    #

    Declined with expired_card. The order stays open.

  • Visa

    Incorrect CVC
    #

    Declined with incorrect_cvc. The order stays open.

  • Visa

    Processing error
    #

    Fails with processing_error. The order stays open.

  • Visa

    Saves, then charges fail
    #

    Saves to a customer, then every charge fails: point a subscription at it and the next renewal sends subscription.past_due. Subscribing with it from the start fails the first payment, which moves the subscription from incomplete to past_due.

Lost and stolen cards

2 cardsFlint guide
  • Visa

    Lost or stolen
    #

    The attempt ends failed with lost_card.

  • Visa

    Lost or stolen
    #

    The attempt ends failed with stolen_card.

Risk and fraud

3 cardsFlint guide
  • Visa

    Fraud block or review
    #

    Elevated risk: Flint's default rule opens a review, except on invoice and subscription renewal payments.

  • Visa

    Fraud block or review
    #

    Highest risk, blocked by the card processor's fraud screening. The attempt fails with payment_blocked.

  • Visa

    Dispute or fraud warning
    #

    Payment succeeds, then receives an early fraud warning.

Disputes

2 cardsFlint guide
  • Visa

    Dispute or fraud warning
    #

    Payment succeeds, then is disputed as fraudulent and waits in needs_response. Rule on it with POST /v1/disputes/{dispute_id}/simulate.

  • Visa

    Dispute or fraud warning
    #

    Payment succeeds, then is disputed as an inquiry and waits in inquiry_needs_response. Rule on it with POST /v1/disputes/{dispute_id}/simulate.

Test tokens

5 values

Pass one as payment_source.stripe.payment_method, with credential_type: stripe_payment_method, to pay an order from code with no card form. The reader outcomes go in the body of POST /v1/readers/{reader_id}/simulate, and the amounts apply to a payment presented on a physical reader. See the in-person payments guide.

  • Payment token

    Success#

    The payment succeeds and the order becomes paid.

  • Payment token

    Generic decline#

    The attempt fails with last_payment_error.code of card_declined.

  • Payment token

    Insufficient funds#

    The attempt fails with insufficient_funds.

  • Payment token

    3DS challenge#

    The attempt stops at requires_action with a 3D Secure step for the browser to complete.

  • Payment token

    3DS challenge#

    The attempt stops at requires_action, using 3D Secure 2.

Sources

Every Worldpay number and outcome comes from Worldpay's own docs, read on November 17, 2026. Each card group links to the page that lists it.

Test cards for other processors: Stripe, Adyen, PayPal, Braintree, Authorize.net, Square, Checkout.com, Cybersource, NMI.