Skip to content

Authorize.net test cards

Every card number in Authorize.net's testing guide, with the billing ZIP codes and card codes that decide declines, AVS results, and partial authorizations.
Verified against official documentationReviewed Send a correction (opens in a new tab)

Authorize.net test cards by scenario

ZIP-code-driven: every test card approves, and the billing ZIP code decides declines, AVS results, and partial authorizations. Amount triggers were phased out in 2011. Where a cell names a trigger, use it with any of Authorize.net's cards below. On Flint, each scenario is one card number with any future expiry, any 3-digit CVC, and any ZIP.

ScenarioAuthorize.netFlint
Successful payment4111 1111 1111 11114242 4242 4242 4242any future expiry, any CVC, any ZIP
Generic declineZIP code 462824000 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 CVCCard code 901 (response N, no decline)4000 0000 0000 0127
3D Secure challengeNot documented4000 0025 0000 3155
3D Secure authentication failsNot documented4000 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 Authorize.net triggers declines

Every Authorize.net test card approves; the billing ZIP code decides the result. ZIP 46282 declines with response code 2, and other ZIP codes set AVS responses and partial authorizations. Card code 901 returns a card code mismatch without declining. Amount triggers were phased out in 2011.

How Authorize.net tests 3D Secure

Authorize.net's testing guide lists no 3D Secure test cards.

How Authorize.net simulates disputes

Authorize.net's testing guide documents no dispute or chargeback simulation.

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

13 cards and 20 trigger values from Authorize.net

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 Authorize.net test card#

13 cards, 20 triggers

ZIP-code-driven: every test card approves, and the billing ZIP code decides declines, AVS results, and partial authorizations. Amount triggers were phased out in 2011.

Expiry
Any date after today
CVC
Any 3 digits; trigger values set the card code response; any 4 digits for American Express
Postal code
Any; trigger ZIP codes set the response
  • The cards only work in the sandbox, and the sandbox should stay in Live Mode: transactions in test mode are not stored and return a transaction ID of zero.
  • Production credentials in the sandbox, or sandbox credentials in production, always return response reason code 13.

Test cards

Show all 13 cards

Authorize.net docs

  • American Express

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • UnionPay

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • UnionPay

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • UnionPay

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • Discover

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • JCB

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • Diners Club, Diners Club / Carte Blanche

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • Visa, 13 digits

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • Visa, 13 digits

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • Visa

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • Mastercard

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • Mastercard, 2-series

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

  • Mastercard, 2-series

    Success
    #

    Approves. Declines and AVS results come from the billing ZIP code.

Trigger values

Show all 20 values

Send these billing ZIP codes and card codes with any test card.

  • ZIP code

    Generic decline#

    Response code 2: This transaction has been declined (general bank decline), with any test card.

  • ZIP code

    CVC or address check#

    AVS N: address and ZIP code don't match.

  • ZIP code

    CVC or address check#

    AVS A: address matches, ZIP code doesn't.

  • ZIP code

    CVC or address check#

    AVS Z: ZIP code matches, address doesn't.

  • ZIP code

    CVC or address check#

    AVS W: address doesn't match, ZIP matched 9 digits. Not for American Express.

  • ZIP code

    CVC or address check#

    AVS X: address matches, ZIP matched 9 digits. Not for Visa or American Express.

  • ZIP code

    CVC or address check#

    AVS E: AVS data invalid, or AVS not allowed for the card type.

  • ZIP code

    CVC or address check#

    AVS R: the AVS system was unavailable.

  • ZIP code

    CVC or address check#

    AVS G: non-US issuing bank that doesn't support AVS. Not for American Express.

  • ZIP code

    CVC or address check#

    AVS U: the cardholder's address information is unavailable.

  • ZIP code

    CVC or address check#

    AVS S: the US issuing bank doesn't support AVS.

  • ZIP code

    Other#

    Partial authorization: $1.23 authorized.

  • ZIP code

    Other#

    Prepaid authorization: full amount authorized, remaining balance $1.23.

  • ZIP code

    Other#

    Prepaid authorization: full amount authorized, remaining balance -$1.23.

  • ZIP code

    Other#

    Prepaid authorization: full amount authorized, remaining balance $0.

  • Card code

    Incorrect CVC#

    Card code response N: does not match.

  • Card code

    CVC or address check#

    Card code response M: successful match.

  • Card code

    CVC or address check#

    Card code response S: should be on the card, but is not indicated.

  • Card code

    CVC or address check#

    Card code response U: issuer not certified or has not provided an encryption key.

  • Card code

    CVC or address check#

    Card code response P: not processed.

Not in Authorize.net's docs

  • Declines for specific reasons such as insufficient funds, expired, lost, or stolen cards.
  • 3D Secure test cards.
  • Dispute or chargeback simulation.

The same tests on Flint

On Flint, each decline reason has its own card number, and 3D Secure and dispute cards are documented too: 4000 0025 0000 3155 opens a challenge, 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 Authorize.net number and outcome comes from Authorize.net's own docs, read on November 11, 2026. Each card group links to the page that lists it.

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