Use the testing guide to trigger specific transaction response while testing in the sandbox.
Testing in the Sandbox
The sandbox environment is separate from the live production environment and requires separate credentials. Using your production credentials in the sandbox or your sandbox credentials in the production environment returns Response Reason Code 13. Sign up for a sandbox account at https://developer.authorize.net/hello_world/sandbox/.
Our sandbox functions like the live payment gateway. However, sandbox transactions do not process live payments. The response from the sandbox varies depending on the card type, ZIP code, and amount.
Test Card Numbers
The following test credit card numbers will only work in the sandbox. Use an expiration date after today’s date. If the card code is required, please use any 3-digit combination for Visa, Mastercard, Discover, Diners Club, EnRoute, and JCB; use a 4-digit combination for American Express.
|Test Card Brand||Number|
|Diners Club/ Carte Blanche||38000000000006|
Testing Solution ID
The following test solution IDs should be used in the sandbox environment:
Note: Production solution IDs cannot be used in the sandbox. See the Solution ID Integration Guide for more details.
Generating Card Responses
In all of the tables, the first column shows the value to use to trigger the response shown in the second column.
Use the ZIP code below to generate declined transactions.
|46282||2||This transaction has been declined.||General bank decline.
When testing AVS, use the ZIP codes below to generate specific AVS responses. See the Support Center article, "What Are the Different Address Verification Service (AVS) Response Codes?", for an explanation of AVS responses.
||Mastercard Response||Discover Response||American Express Response||Discover Response||JCB Response|
When testing CVV, use the card codes below to generate specific CVV responses.
||CVV Response||CVV Status|
|901||N||Does not match.
|902||S||Should be on the card, but is not indicated.|
|903||U||The issuer is not certified for CVV processing or has not provided an encryption key.|
|904||P||Is not processed.|
PARTIAL AUTHORIZATION RESPONSES
When testing partial authorization, use zip codes (card not present transactions) and amounts (card present transactions) to produce specific responses.
(if card not present)
(if card present)
||-$1.23 (see below for explanation)||Full Amount|
|46228||$462.28||Prepaid Authorization||$0||Full Amount
In what circumstances would a card have a negative balance?
A prepaid card has a negative balance if it is a reloadable card that is linked to a bank account and has a monthly fee. If the customer uses the complete balance and the bank charges the monthly fee, the card would have a negative balance until the customer reloads the card.
Transaction Amount Triggers (Deprecated)
The following tables list current correspondences between transaction amounts and specific responses.
Note: These values are deprecated in favor of the ZIP code values listed above, and may be removed from the sandbox without advance notice.
|AMOUNT||RESPONSE CODE||RESPONSE TEXT||NOTES|
|$70.02||2||This transaction has been declined.||General bank decline.
|$70.03||3||This transaction has been declined.||Referral to voice authorization center.|
|$70.05||35||An error occurred during processing. Call Merchant Service Provider.
||An unknown error occurred during processing.|
||CVV RESPONSE||CVV STATUS|
|$70.71||N||Does not match.
||Is not processed.
|$70.73||S||Should be on the card, but is not indicated.|
|$70.74||U||The issuer is not certified for CVV processing or has not provided an encryption key.|