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.
| Scenario | Authorize.net | Flint |
|---|---|---|
| Successful payment | 4111 1111 1111 1111 | 4242 4242 4242 4242any future expiry, any CVC, any ZIP |
| Generic decline | ZIP code 46282 | 4000 0000 0000 0002 |
| Insufficient funds | Not documented | 4000 0000 0000 9995 |
| Lost or stolen card | Not documented | 4000 0000 0000 99874000 0000 0000 9979lost, stolen |
| Expired card | Not documented | 4000 0000 0000 0069 |
| Incorrect CVC | Card code 901 (response N, no decline) | 4000 0000 0000 0127 |
| 3D Secure challenge | Not documented | 4000 0025 0000 3155 |
| 3D Secure authentication fails | Not documented | 4000 0000 0000 3220fail the challenge |
| Card saves, then charges fail | Not documented | 4000 0000 0000 0341 |
| Dispute or chargeback | Not documented | 4000 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.