Authorize.net Test Cards — Sandbox Reference
Verified Authorize.net sandbox test cards for Visa, Mastercard, Amex, and Discover payment testing.
Authorize.net (owned by Visa) uses a sandbox environment for payment testing. The sandbox mirrors most production behavior. Use your Authorize.net sandbox API Login ID and Transaction Key for test transactions.
Showing 8 of 8 test cards
| Card Number | Network | Scenario | Code | Copy |
|---|---|---|---|---|
4111 1111 1111 1111TEST ONLY | Visa | Successful payment — approvedUS | — | |
4007 0000 0002 7TEST ONLY | Visa | Successful payment (13-digit Visa)US | — | |
4012 8888 1888 8TEST ONLY | Visa | Successful payment (13-digit alternate)US | — | |
5424 0000 0000 0015TEST ONLY | Mastercard | Successful paymentUS | — | |
2223 0000 4840 0011TEST ONLY | Mastercard (2-series) | Successful paymentUS | — | |
6011 0000 0000 0012TEST ONLY | Discover | Successful paymentUS | — | |
3700 000000 00002TEST ONLY | Amex | Successful paymentUS | — | |
4111 1111 1111 1111TEST ONLY | Visa | Declined — use amount $0.01 or test decline triggerUS | 2 |
TEST ONLY. These numbers will not process real transactions. Use only in Authorize.net's sandbox environment with test API credentials.
What it does
13-digit Visa support
Authorize.net accepts 13-digit Visa numbers in addition to standard 16-digit — useful for testing legacy format handling.
Multi-network cards
Test cards for Visa (16 and 13 digit), Mastercard, Mastercard 2-series, Amex, and Discover.
Amount-based decline simulation
Authorize.net simulates declines using specific amounts ($0.02, $0.21, etc.) rather than separate card numbers.
Legacy US payment gateway
Authorize.net is widely used in US legacy integrations and enterprise systems.
How to use Authorize.net Test Cards — Sandbox Reference
- 1Get sandbox credentials
Create an Authorize.net sandbox account at developer.authorize.net and get your API Login ID and Transaction Key.
- 2Use standard test values
Any future expiry date and any CVV work with these test cards in sandbox mode.
- 3Simulate declines with amounts
To simulate declines in Authorize.net sandbox, use $0.02 (generic decline), $0.08 (do not honor), or $0.21 (insufficient funds) instead of a specific card number.
- 4Check the response code
Authorize.net returns a response_code (1=Approved, 2=Declined, 3=Error) and a response_reason_code.
Authorize.net's amount-based decline simulation
Unlike Stripe, Adyen, and Braintree which use specific card numbers to trigger declines, Authorize.net's sandbox primarily uses transaction amounts. You submit the success card (4111 1111 1111 1111) but with a specific dollar amount like $0.02 to get a decline response. This is Authorize.net's documented approach for sandbox testing and reflects the older design of their test environment.
Frequently Asked Questions
How do I trigger a decline in Authorize.net sandbox?
- Authorize.net sandbox uses transaction amounts to trigger declines, not separate card numbers. Use $0.02 for generic decline, $0.08 for do not honor, $0.21 for insufficient funds, $0.41 for expired card. The success card (4111...) with $0.01 or any normal amount returns an approval.
Does Authorize.net support 3DS?
- Authorize.net supports cardAuthentication for 3DS, but the sandbox implementation is limited compared to providers like Stripe or Adyen. Consult the Authorize.net developer docs for their current 3DS testing guidance.
Is Authorize.net still widely used?
- Authorize.net is still used by a large number of US businesses, particularly in enterprise and legacy systems. It processes a significant volume of US transactions, especially through integrations built in the 2000s-2010s that haven't migrated to newer providers.
Related Tools
UUID Generator
Generate random UUID v4 identifiers. Bulk generate up to 100 UUIDs, toggle uppercase/lowercase and hyphen formatting.
JSON Formatter
Clean, minify, and validate JSON data structures.
JWT Decoder
Decode and inspect JWT tokens — header, payload, timestamps.
Regex Tester
Real-time expression matching and testing.