Skip to content

NMI test cards

Every card number in NMI's testing docs, with expiry 10/29, the values that force a decline and AVS and CVV matches, and the 3D Secure cards for a sandbox account and for test mode.
Verified against official documentationReviewed Send a correction (opens in a new tab)

NMI test cards by scenario

Amount-driven with little decline coverage: every valid card approves, any amount under 1.00 declines, and an invalid card number returns a fatal error. 3D Secure has its own cards, which differ between a sandbox account and test mode. Where a cell names a trigger, use it with any of NMI's cards below. On Flint, each scenario is one card number with any future expiry, any 3-digit CVC, and any ZIP.

ScenarioNMIFlint
Successful payment4111 1111 1111 1111expiry 10/294242 4242 4242 4242any future expiry, any CVC, any ZIP
Generic declineAmount under 1.004000 0000 0000 0002
Insufficient fundsNot documented4000 0000 0000 9995
Lost or stolen cardNot documented4000 0000 0000 99874000 0000 0000 9979lost, stolen
Expired cardNot documented4000 0000 0000 0069
Incorrect CVCNot documented4000 0000 0000 0127
3D Secure challenge4100 0000 0000 5000sandbox, code 123454000 0025 0000 3155
3D Secure authentication fails4000 0000 0000 2370test mode4000 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 NMI triggers declines

NMI's test cards approve. Any amount under 1.00 declines, and an invalid card number returns a fatal error. NMI documents no values for specific decline reasons, such as insufficient funds or an expired card.

How NMI tests 3D Secure

A sandbox account and test mode use different cards. In a sandbox, 4100 0000 0000 5000 opens a mock challenge that passes with code 12345. In test mode, the payer authentication cards simulate each result, such as 4000 0000 0000 2503 for a challenge that succeeds.

How NMI simulates disputes

NMI's testing docs document no dispute or chargeback simulation.

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

26 cards and 4 trigger values from NMI

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

26 cards, 4 triggers

Amount-driven with little decline coverage: every valid card approves, any amount under 1.00 declines, and an invalid card number returns a fatal error. 3D Secure has its own cards, which differ between a sandbox account and test mode.

Expiry
10/29
CVC
Any; 999 returns a CVV match
Postal code
Any; 77777 with address 888 returns an AVS match
  • Test in a sandbox account from guide.nmi.com, with test_mode set to enabled on one transaction of a live account, or with a merchant account switched into test mode.
  • In test mode every valid card is approved without charges. Never use real card details.
  • A single test transaction on a live account shows in reporting only while the account is toggled into test mode.
  • The sandbox and test mode use different 3D Secure test cards: the sandbox cards below come from NMI's testing methods, and the payer authentication cards need the account in test mode.

Test cards

7 cardsNMI docs
  • Visa

    SuccessOther 3DS result
    #

    Approves in a sandbox or in test mode. In the sandbox's 3D Secure flow it isn't enrolled, so authentication is skipped: cardholder_auth attempted and ECI 07.

  • Mastercard

    SuccessOther 3DS result
    #

    Approves in a sandbox or in test mode. In the sandbox's 3D Secure flow it isn't enrolled, so authentication is skipped: cardholder_auth attempted and ECI 07.

  • American Express

    SuccessOther 3DS result
    #

    Approves in a sandbox or in test mode. In the sandbox's 3D Secure flow it isn't enrolled, so authentication is skipped: cardholder_auth attempted and ECI 07.

  • Discover

    Success
    #

    Approves in a sandbox or in test mode.

  • Diners Club, 14-digit card

    Success
    #

    Approves in a sandbox or in test mode.

  • JCB

    Success
    #

    Approves in a sandbox or in test mode.

  • Maestro, 19-digit card

    SuccessOther 3DS result
    #

    Approves in a sandbox or in test mode. NMI's sandbox 3D Secure table lists it as a not-enrolled Discover card: authentication is skipped with ECI 07.

3D Secure in a sandbox: frictionless

4 cardsNMI docs
  • Visa

    3DS frictionless
    #

    Enrolled; authenticates without a challenge: cardholder_auth verified and ECI 05.

  • Mastercard

    3DS frictionless
    #

    Enrolled; authenticates without a challenge: cardholder_auth verified and ECI 05.

  • American Express

    3DS frictionless
    #

    Enrolled; authenticates without a challenge: cardholder_auth verified and ECI 05.

  • Discover

    3DS frictionless
    #

    Enrolled; authenticates without a challenge: cardholder_auth verified and ECI 05.

3D Secure in a sandbox: challenge

4 cardsNMI docs
  • Visa

    3DS challenge3DS fails
    #

    A mock challenge opens: enter 12345 to pass, any other code to fail, or close it to cancel.

  • Mastercard

    3DS challenge3DS fails
    #

    A mock challenge opens: enter 12345 to pass, any other code to fail, or close it to cancel.

  • American Express

    3DS challenge3DS fails
    #

    A mock challenge opens: enter 12345 to pass, any other code to fail, or close it to cancel.

  • Discover

    3DS challenge3DS fails
    #

    A mock challenge opens: enter 12345 to pass, any other code to fail, or close it to cancel.

3D Secure in test mode: payer authentication

11 cardsNMI docs
  • Visa

    3DS frictionless
    #

    Frictionless authentication succeeds: ThreeDSecureUI emits a complete event with cardHolderAuth verified and ECI 05.

  • Visa

    3DS fails
    #

    Frictionless authentication fails: ThreeDSecureUI emits a failure event, TRANSACTION_STATUS_N.

  • Visa

    Other 3DS result
    #

    Attempted: the cardholder is enrolled but the issuer doesn't support 3D Secure. A complete event with cardHolderAuth attempted and ECI 06.

  • Visa

    Other 3DS result
    #

    Authentication is unavailable: a failure event, TRANSACTION_STATUS_U.

  • Visa

    3DS fails
    #

    The issuer rejects authentication without a challenge: a failure event, TRANSACTION_STATUS_R.

  • Visa

    Other 3DS result
    #

    An unknown technical error: an error event of type gatewayError.

  • Visa

    Other 3DS result
    #

    A timeout: an error event of type gatewayError, Transaction Timed Out.

  • Visa

    3DS challenge
    #

    Step-up succeeds: ThreeDSecureUI prompts for a password, then emits a complete event with cardHolderAuth verified and ECI 05.

  • Visa

    3DS fails
    #

    Step-up fails: after the password prompt, a failure event, TRANSACTION_STATUS_N.

  • Visa

    Other 3DS result
    #

    Step-up is unavailable: after the password prompt, a failure event, TRANSACTION_STATUS_U.

  • Visa

    Other 3DS result
    #

    An error during authentication: after the password prompt, an error event of type gatewayError, Error Processing PARes.

Trigger values

4 values

Send these on the transaction with any test card and expiry 10/29. NMI documents only matches for CVV and AVS, not mismatches.

  • Amount

    Generic decline#

    Any amount under 1.00 declines.

  • CVV

    CVC or address check#

    Returns a CVV match.

  • Address 1

    CVC or address check#

    With zip 77777, returns an AVS match.

  • ZIP code

    CVC or address check#

    With address1 888, returns an AVS match.

Not in NMI's docs

  • Declines for specific reasons, such as insufficient funds, expired, lost, or stolen cards.
  • Dispute or chargeback simulation.
  • A card that saves, then fails on later charges.

The same tests on Flint

On Flint, insufficient funds, expired cards, lost or stolen cards, and incorrect CVCs each have their own card number, 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 NMI number and outcome comes from NMI'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, Cybersource.