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.
| Scenario | NMI | Flint |
|---|---|---|
| Successful payment | 4111 1111 1111 1111expiry 10/29 | 4242 4242 4242 4242any future expiry, any CVC, any ZIP |
| Generic decline | Amount under 1.00 | 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 | Not documented | 4000 0000 0000 0127 |
| 3D Secure challenge | 4100 0000 0000 5000sandbox, code 12345 | 4000 0025 0000 3155 |
| 3D Secure authentication fails | 4000 0000 0000 2370test mode | 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 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.