Authorize.Net Test Card Numbers

Official Authorize.Net sandbox test card numbers, with the ZIP code, AVS and CVV values that trigger declines and address responses.

Authorize.Net's sandbox accepts test numbers such as 4111 1111 1111 1111 (Visa), 5424 0000 0000 0015 (Mastercard) and 3700 000000 00002 (Amex) with any expiration date after today. Responses are driven by the billing ZIP code and CVV rather than the card number. ZIP 46282 returns a decline and CVV 901 a CVV mismatch.

Last verified against Authorize.Net's official documentation on .

Expiry: Any date after today
CVV: Any 3 digits (4 for Amex)
Official documentation

Sandbox test card numbers

Authorize.Net does not tie each number to a fixed result. Combine any of these with the ZIP code and CVV triggers below to choose the response.

Card numberBrandResultCopy
4111 1111 1111 1111Visa
Sandbox test card
4007 0000 0002 7Visa
Sandbox test card 13-digit
4012 8888 1888 8Visa
Sandbox test card 13-digit
5424 0000 0000 0015Mastercard
Sandbox test card
2223 0000 1030 9703Mastercard
Sandbox test card 2-series
3700 000000 00002American Express
Sandbox test card
6011 0000 0000 0012Discover
Sandbox test card
3088 0000 0000 0017JCB
Sandbox test card
3800 000000 0006Diners Club
Sandbox test card Diners Club / Carte Blanche
6221 4990 5336 0818UnionPay
Sandbox test card

ZIP code triggers

Enter these as the billing ZIP code with any test card above.

ScenarioValueEffect
General decline46282Response code 2: transaction declined
Address and ZIP do not match46205AVS response N
Address matches, ZIP does not46201AVS response A
ZIP matches, address does not46217AVS response Z
Address information unavailable46209AVS response U
Issuer does not support AVS46208AVS response S
AVS system unavailable46207AVS response R
Invalid AVS data46203AVS response E
Non-US issuer, no AVS support46204AVS response G

Partial authorisation and prepaid

Card-not-present only. Enter the ZIP code together with the amount shown.

ScenarioValueEffect
Partial authorisationZIP 46225, amount $462.25Authorised for $1.23 only
Prepaid, $1.23 remainingZIP 46226, amount $462.26Full amount approved
Prepaid, negative balanceZIP 46227, amount $426.27Approved, balance -$1.23
Prepaid, zero balanceZIP 46228, amount $462.28Approved, balance $0

CVV triggers

ScenarioValueEffect
Match900CVV response M
No match901CVV response N
Should be on card902CVV response S
Issuer not certified903CVV response U
Not processed904CVV response P

Before you use these

  • Sandbox credentials only. Production credentials return response reason code 13 against the sandbox, and the reverse.
  • The sandbox never submits transactions to a card network or processes a payment.
  • Authorize.Net also documents amount-based triggers but warns they may stop working without notice, so they are not listed here.
  • These numbers are published by Authorize.Net for sandbox testing. They are not real cards and cannot be used for a real purchase.

How to use Authorize.Net test cards

  1. Switch your Authorize.Net integration to its test or sandbox environment and use test credentials. Live credentials reject these numbers.
  2. Enter a card number from the tables above. Expiry: Any date after today. Security code: Any 3 digits (4 for Amex).
  3. Start with a successful card to confirm the happy path, then work through the decline and error cards so every failure message in your checkout gets exercised.
  4. Use the trigger values (zip code triggers, partial authorisation and prepaid, cvv triggers) to simulate outcomes that are not tied to a card number.

Authorize.Net test card FAQ

How do I make an Authorize.Net sandbox transaction decline?

Use any test card with billing ZIP code 46282, which returns response code 2 (declined). Other ZIP codes return specific AVS responses.

What expiry date and CVV should I use with Authorize.Net test cards?

Any expiration date after today, and any 3-digit CVV (4 for American Express). CVV 901 returns a CVV mismatch.

What are the Authorize.Net test card numbers?

Authorize.Net's sandbox accepts test numbers such as 4111 1111 1111 1111 (Visa), 5424 0000 0000 0015 (Mastercard) and 3700 000000 00002 (Amex) with any expiration date after today. Responses are driven by the billing ZIP code and CVV rather than the card number. ZIP 46282 returns a decline and CVV 901 a CVV mismatch.

Do Authorize.Net test cards work in production?

No. These numbers are only recognised by the Authorize.Net test environment and are rejected by the live platform. They are not real cards and cannot be used for a purchase.

How do I test a declined payment with Authorize.Net?

Authorize.Net triggers failures through zip code triggers as well as dedicated card numbers. Both are listed on this page.