An Authorize.net test card is a publicly documented card number used only in the Authorize.net sandbox to simulate payments without moving real money. It works only when the account is in test mode, and it should never be used with live credentials.
What an Authorize.net test card is for
Use an Authorize.net test card to check payment form behavior, API requests, response handling, and checkout flows before a live launch. The goal is to confirm that your integration sends the expected fields and handles approvals, declines, and errors in a controlled sandbox.
- Verify card number validation and expiration handling
- Confirm API login ID and transaction key setup
- Test approval and decline response paths
- Check receipt, order, and failure messages
Common Authorize.net test card numbers
These sandbox numbers are widely used for Authorize.net payment testing. Confirm current values in the Authorize.net developer documentation because sandbox rules can change.
- Visa: 4111111111111111
- Mastercard: 5424000000000015
- American Express: 370000000000002
- Discover: 6011000000000012
- JCB: 3566000000000000
Use a future expiration date. For the card code, use 123 for three-digit cards and 1234 for American Express unless your test case requires a specific value. Test card numbers have no value outside a sandbox and are not real cardholder data.
How to test an Authorize.net payment
- Use a sandbox account, not a production account.
- Copy the sandbox API login ID and transaction key into your test configuration.
- Submit a transaction with a documented Authorize.net test card and a future expiration date.
- Review the response code, response reason, and transaction record in the sandbox.
- Repeat the test for the approval, decline, and error cases your checkout must handle.
What test cards do not do
- They do not move real money.
- They do not prove that a live account is configured correctly.
- They do not reproduce real issuer behavior.
- They do not replace PCI DSS controls for production payments.
Safety rules for payment testing
Never enter real cardholder data into a test environment. Use only vendor-documented test numbers, keep sandbox credentials separate from production credentials, and remove test settings before launch. Do not use an Authorize.net test card in a live checkout, and do not treat test results as proof that a production payment will be approved.
An Authorize.net test card helps verify integration logic, but it is not a live payment method. Treat test card data as public test data and keep all production card handling within PCI DSS requirements.