Skip to content

Cybersource test cards

Every card number in Cybersource's testing docs, with the Xs replaced by zeros, the order amounts that force each decline on Visa Platform Connect, and the 3-D Secure 2 cards for each payer authentication test case.
Verified against official documentationReviewed Send a correction (opens in a new tab)

Cybersource test cards by scenario

Amount-driven: the order total decides the processor response, and the trigger amounts depend on the processor your sandbox account uses. The amounts here are Cybersource's table for Visa Platform Connect. 3D Secure has its own cards. Where a cell names a trigger, use it with any of Cybersource's cards below. On Flint, each scenario is one card number with any future expiry, any 3-digit CVC, and any ZIP.

ScenarioCybersourceFlint
Successful payment4111 1111 1111 11114242 4242 4242 4242any future expiry, any CVC, any ZIP
Generic declineAmount 4005.00 on Visa Platform Connect4000 0000 0000 0002
Insufficient fundsAmount 4051.004000 0000 0000 9995
Lost or stolen cardAmount 4041.00 or 4043.004000 0000 0000 99874000 0000 0000 9979lost, stolen
Expired cardAmount 4054.004000 0000 0000 0069
Incorrect CVCAmount 4106.004000 0000 0000 0127
3D Secure challenge4000 0000 0000 2503expiry January, current year plus 34000 0025 0000 3155
3D Secure authentication fails4000 0000 0000 23704000 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 Cybersource triggers declines

Cybersource's declines come from the order amount, and the amounts depend on the processor your sandbox uses. On Visa Platform Connect, 4005.00 declines with 05, 4051.00 with insufficient funds, 4054.00 with an expired card, and 4041.00 with a lost card. An amount below zero or a number that fails the Luhn check returns INVALID_DATA.

How Cybersource tests 3D Secure

Each payer authentication test case has its own card per brand, such as 4000 0000 0000 2503 for a challenge that succeeds and 4000 0000 0000 2370 for one that fails. Set the expiry to January of the current year plus 3.

How Cybersource simulates disputes

Cybersource's testing docs document no dispute or chargeback simulation in the sandbox.

Look up a Cybersource 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.

37 cards and 25 trigger values from Cybersource

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 Cybersource test card#

37 cards, 25 triggers

Amount-driven: the order total decides the processor response, and the trigger amounts depend on the processor your sandbox account uses. The amounts here are Cybersource's table for Visa Platform Connect. 3D Secure has its own cards.

Expiry
Any date after today
CVC
Any 3 digits; any 4 digits for American Express
Postal code
Not specified
  • The cards work only in the sandbox, which needs its own credentials: production credentials there return HTTP 401.
  • Cybersource prints its test numbers with an X for each zero. The numbers here have the zeros filled in.
  • 3D Secure 2 test cards need an expiry of January in the current year plus 3.
  • Trigger amounts differ by processor. Cybersource publishes a table for each of 14 processors; the amounts here are Visa Platform Connect's.
  • To test a card type with no number here, Cybersource says to use an account number in that card's BIN range.

Test card numbers

12 cardsCybersource docs
  • Visa

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses.

  • Mastercard

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses.

  • Mastercard, 2-series

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses.

  • Mastercard, 2-series

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses.

  • American Express

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses.

  • Discover

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses.

  • JCB

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses.

  • Maestro, International, 14-digit card

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses.

  • Maestro, International, 18-digit card

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses.

  • Maestro, UK Domestic

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses. No issue number needed.

  • Maestro, UK Domestic, 19-digit card

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses. No issue number needed.

  • Maestro, UK Domestic

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses. No issue number needed.

More cards from the testing guide

6 cardsCybersource docs
  • Visa

    Success
    #

    A Visa test card listed with its own CVV.

    CVC: 838

  • Visa

    Success
    #

    A Visa test card listed with its own CVV.

    CVC: 043

  • Visa

    Success
    #

    A Visa test card listed with its own CVV.

    CVC: 258

  • Visa

    Success
    #

    A Visa test card listed with its own CVV.

    CVC: 942

  • Visa

    Success
    #

    A Visa test card listed with its own CVV.

    CVC: 370

  • UATP

    Success
    #

    Authorizes in the sandbox. The order amount sets other responses.

3D Secure: frictionless authentication succeeds

4 cardsCybersource docs
  • Visa

    3DS frictionless
    #

    Test case 2.1: the issuer authenticates the cardholder without a challenge.

    Expiry: January of the current year plus 3

  • American Express

    3DS frictionless
    #

    Test case 2.1: the issuer authenticates the cardholder without a challenge.

    Expiry: January of the current year plus 3

  • Discover, also listed for Diners Club

    3DS frictionless
    #

    Test case 2.1: the issuer authenticates the cardholder without a challenge.

    Expiry: January of the current year plus 3

  • JCB

    3DS frictionless
    #

    Test case 2.1: the issuer authenticates the cardholder without a challenge.

    Expiry: January of the current year plus 3

3D Secure: frictionless authentication fails

5 cardsCybersource docs
  • Visa

    3DS fails
    #

    Test case 2.2: authentication without a challenge fails.

    Expiry: January of the current year plus 3

  • Mastercard

    3DS fails
    #

    Test case 2.2: authentication without a challenge fails.

    Expiry: January of the current year plus 3

  • American Express

    3DS fails
    #

    Test case 2.2: authentication without a challenge fails.

    Expiry: January of the current year plus 3

  • Discover, also listed for Diners Club

    3DS fails
    #

    Test case 2.2: authentication without a challenge fails.

    Expiry: January of the current year plus 3

  • JCB

    3DS fails
    #

    Test case 2.2: authentication without a challenge fails.

    Expiry: January of the current year plus 3

3D Secure: challenge succeeds

5 cardsCybersource docs
  • Visa

    3DS challenge
    #

    Test case 2.9: the issuer challenges the cardholder, and the step-up authentication succeeds.

    Expiry: January of the current year plus 3

  • Mastercard

    3DS challenge
    #

    Test case 2.9: the issuer challenges the cardholder, and the step-up authentication succeeds.

    Expiry: January of the current year plus 3

  • American Express

    3DS challenge
    #

    Test case 2.9: the issuer challenges the cardholder, and the step-up authentication succeeds.

    Expiry: January of the current year plus 3

  • Discover, also listed for Diners Club

    3DS challenge
    #

    Test case 2.9: the issuer challenges the cardholder, and the step-up authentication succeeds.

    Expiry: January of the current year plus 3

  • JCB

    3DS challenge
    #

    Test case 2.9: the issuer challenges the cardholder, and the step-up authentication succeeds.

    Expiry: January of the current year plus 3

3D Secure: challenge fails

5 cardsCybersource docs
  • Visa

    3DS fails
    #

    Test case 2.10: the issuer challenges the cardholder, and the challenge fails.

    Expiry: January of the current year plus 3

  • Mastercard

    3DS fails
    #

    Test case 2.10: the issuer challenges the cardholder, and the challenge fails.

    Expiry: January of the current year plus 3

  • American Express

    3DS fails
    #

    Test case 2.10: the issuer challenges the cardholder, and the challenge fails.

    Expiry: January of the current year plus 3

  • Discover, also listed for Diners Club

    3DS fails
    #

    Test case 2.10: the issuer challenges the cardholder, and the challenge fails.

    Expiry: January of the current year plus 3

  • JCB

    3DS fails
    #

    Test case 2.10: the issuer challenges the cardholder, and the challenge fails.

    Expiry: January of the current year plus 3

Trigger values

Show all 25 values

Amounts go in orderInformation.amountDetails.totalAmount and CVVs in paymentInformation.card.securityCode, with any test card. The card number, expiry month, and expiry year values go in paymentInformation.card. The Visa Platform Connect values apply when your sandbox uses that processor; Cybersource's testing guide has the table for each other processor.

  • Amount

    Invalid card details#

    INVALID_REQUEST with reason INVALID_DATA: an amount below zero.

  • Card number

    Invalid card details#

    DECLINE with reason INVALID_DATA: the number fails the Luhn check.

  • Expiry month

    Invalid card details#

    INVALID_REQUEST with reason INVALID_DATA.

  • Expiry year

    Invalid card details#

    DECLINE with reason INVALID_DATA.

  • Amount (Visa Platform Connect)

    Success#

    AUTHORIZED, with AVS code Y.

  • Amount (Visa Platform Connect)

    Generic decline#

    DECLINED with response code 05 and reason PROCESSOR_DECLINED.

  • Amount (Visa Platform Connect)

    Generic decline#

    DECLINED with response code 03 and reason PROCESSOR_DECLINED.

  • Amount (Visa Platform Connect)

    Generic decline#

    DECLINED with response code 13 and reason GENERAL_DECLINE.

  • Amount (Visa Platform Connect)

    Insufficient funds#

    DECLINED with response code 51 and reason INSUFFICIENT_FUND.

  • Amount (Visa Platform Connect)

    Other decline#

    DECLINED with response code 61 and reason EXCEEDS_CREDIT_LIMIT.

  • Amount (Visa Platform Connect)

    Lost or stolen#

    DECLINED with response code 04 and reason STOLEN_LOST_CARD.

  • Amount (Visa Platform Connect)

    Lost or stolen#

    DECLINED with response code 41 and reason STOLEN_LOST_CARD.

  • Amount (Visa Platform Connect)

    Lost or stolen#

    DECLINED with response code 43 and reason STOLEN_LOST_CARD.

  • Amount (Visa Platform Connect)

    Expired card#

    DECLINED with response code 54 and reason EXPIRED_CARD.

  • Amount (Visa Platform Connect)

    Incorrect CVC#

    DECLINED with response code N7 and reason INVALID_CVN.

  • Amount (Visa Platform Connect)

    Other decline#

    DECLINED with response code 12 and reason UNAUTHORIZED_CARD.

  • Amount (Visa Platform Connect)

    Other decline#

    DECLINED with response code 57 and reason UNAUTHORIZED_CARD.

  • Amount (Visa Platform Connect)

    Invalid card details#

    DECLINED with response code 14 and reason INVALID_ACCOUNT.

  • Amount (Visa Platform Connect)

    Processing error#

    SERVER_ERROR with response code 06 and reason PROCESSOR_ERROR.

  • Amount (Visa Platform Connect)

    Processing error#

    SERVER_ERROR with response code 96 and reason PROCESSOR_ERROR.

  • Amount (Visa Platform Connect)

    Other decline#

    AUTHORIZED_PENDING_REVIEW with response code 01 and reason CONTACT_PROCESSOR.

  • Amount (Visa Platform Connect)

    CVC or address check#

    AUTHORIZED_PENDING_REVIEW with AVS code N and reason AVS_FAILED.

  • Amount (Visa Platform Connect)

    CVC or address check#

    AUTHORIZED_PENDING_REVIEW with CVV result N and reason CV_FAILED.

  • Amount (Visa Platform Connect)

    Other#

    With partialAuthIndicator set to true: PARTIAL_AUTHORIZED with response code 10.

  • CVV (Visa Platform Connect)

    CVC or address check#

    On a zero-amount authorization: AUTHORIZED_PENDING_REVIEW with CVV result N and reason CV_FAILED.

Not in Cybersource's docs

  • Dispute or chargeback simulation in the sandbox.
  • Card numbers that decline: declines come from the amount.
  • 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 at any amount, the same on every account, 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 Cybersource number and outcome comes from Cybersource'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, Worldpay, NMI.