Testing Guide

Use the testing guide to trigger specific transaction response while testing in the sandbox.


Testing in the Sandbox

The sandbox environment is completely separate from the live production environment and requires separate credentials.  Using your production credentials in the sandbox or vice versa will always return Response Reason Code 13.  Sign up for a sandbox account at https://developer.authorize.net/hello_world/sandbox/

Our sandbox functions similar to the live payment gateway. However, sandbox transactions are not submitted to financial institutions for processing.  Sandbox transactions will never actually process a payment.

Your sandbox should always be set to Live Mode. Transactions submitted in test mode are not stored and will return a transaction ID of zero.


Test Card Numbers

The following test credit card numbers will only work in the sandbox. Use any 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
American Express  370000000000002
Discover 6011000000000012
JCB 3088000000000017
Diners Club/ Carte Blanche 38000000000006
Visa 4007000000027
Mastercard 5424000000000015

Test Checking Account Numbers

Testing eCheck.Net® transactions requires using a valid routing number and any random number for checking account.

Routing Numbers can be found at the Federal Reserve website.

Please Note: For testing purposes, eCheck.Net transactions under $100 will be accepted.  To generate a decline, submit a transactions over $100.  A monthly limit of $5000 is also configured in the sandbox.  If you exceed this amount, your eCheck transactions will receive a response code 2. You can request an increase by using the contact us form.


Testing Solution ID

The following test Solution IDs should be used in Sandbox environment: AAA100302, AAA100303, AAA100304

IMPORTANT NOTE: Production Solution IDs cannot be used in the Sandbox.  Refer to 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 following zip code to generate declined transactions.

Zip Code
Response Code
Response Text
46282 2 This Transaction has been declined. General bank decline


When testing AVS, use the following zip codes to generate specific AVS responses.

Zip Code
AVS Status
AVS Response Notes
46203 E AVS data provided is invalid or AVS is not allowed for the card type that was used.  
46207 R The AVS system was unavailable at the time of processing.  
46204 G
The card issuing bank is of non-U.S. origin and does not support AVS. Not applicable to American Express
46209 U The address information for the cardholder is unavailable.  
46208 S The U.S. card issuing bank does not support AVS.  
46205 N Address: No Match
ZIP Code: No Match
46201 A Address: Match
ZIP Code: No Match
46217 Z Address: No Match
ZIP Code: Match
46211 W Address: No Match
ZIP Code: Matched 9 digits
Not applicable to American Express
46214 X Address: Match
ZIP Code: Matched 9 digits
Not applicable to Visa or American Express



When testing CVV, use the following card codes to generate specific CVV responses.

Card Code
CVV Response CVV Status
900 M Successful Match
901 N Does NOT Match
904 P Is NOT Processed
902 S Should be on card, but is not indicated
903 U Issuer is not certified or has not provided encryption key



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)
$462.25 Partial Authorization
n/a $1.23
46226 $462.26 Prepaid Authorization
$1.23 Full Amount
46227 $426.27 Prepaid Authorization
-$1.23(negative balance; see below) Full Amount
46228 $462.28 Prepaid Authorization $0 Full Amount


In what circumstances would a card have a negative balance?

A prepaid card would have a negative balance if, for example, it was a reloadable card, which is typically linked to a bank account; such a card often has a monthly fee. If the consumer has used the complete balance and a fee is assessed, there would be a negative balance prior to the card being reloaded.



Generating eCheck.Net NOC and Return Codes

Important: Use a valid routing number and account number for a checking account when testing eCheck.Net transactions.


When testing eCheck.Net transactions, use the following amounts to generate specific NOC Codes.

Bank Code Description
$13.01 C01 Incorrect Account Number
$13.02 C02 Incorrect Routing Number
$13.03 C03 Incorrect Routing Number and Incorrect Account Number
$13.04 C04 Incorrect Individual Name
$13.05 C05 Incorrect Transaction Code
$13.06 C06 Incorrect Account Number and Incorrect Transaction Code
$13.07 C07 Incorrect Routing Number, Incorrect Account Number and Incorrect Transaction Code


When testing eCheck.Net transactions, use the following amounts to generate specific Return Codes.

Bank Code Description
$12.01 R01 Insufficient Funds
$12.02 R02 Account Closed
$12.03 R03 No account/unable to locate account
$12.04 R04 Invalid Account Number
$12.05 R05 Unauthorized Debit to Consumer Account Using Corporate SEC Code
$12.06 R06 Returned per ODFI’s Request
$12.07 R07 Auth Revoked by Customer
$12.08 R08 Payment Stopped by Customer
$12.09 R09 Uncollected Funds
$12.10 R10 Customer Advises Not Authorized, Not Authorized, Notice Not Provided, Improper Source Document, or Amount of Entry not Accurately Obtained from Source Document
$12.11 R11 Check Truncation Return Entry
$12.12 R12 Invalid ABA Code due to Branch Sold to another RDFI
$12.13 R13 Invalid ACH Routing Number
$12.14 R14 Representative Payee Deceased or No Longer Authorized
$12.15 R15 Beneficiary or Account Holder Deceased
$12.16 R16 Account Frozen
$12.17 R17 File Record Edit Criteria
$12.18 R18 Improper Effective Entry Date
$12.19 R19 Amount Field Error
$12.20 R20 Non Transaction Account
$12.21 R21 Invalid Company Identification
$12.22 R22 Invalid Individual ID Number
$12.23 R23 Credit Entry refused by receiver
$12.24 R24 Duplicate Entry
$12.25 R25 Addenda Error
$12.26 R26 Mandatory Field Error
$12.27 R27 Trace Number Error
$12.28 R28 Routing Number Check-digit Error
$12.29 R29 Corporate Customer Advises not authorized
$12.30 R30 RDFI Not Participant in Check Truncation Program
$12.31 R31 Permissible Return Entry
$12.32 R32 RDFI Non-Settlement
$12.33 R33 Return of XCK Entry
$12.34 R34 Limited Participate DFI
$12.35 R35 Return of Improper Debit Entry
$12.36 R36 Return of Improper Credit Entry
$12.37 R37 Source Document Presented for Payment
$12.38 R38 Stop Payment Improper Source Document
$12.39 R39 Improper Source Document
$12.40 R40 Return of ENR Entry by Federal Government
$12.41 R41 Invalid transaction Code (ENR)
$12.42 R42 Routing Number Check Digit Error (ENR only)
$12.43 R43 Invalid DFI Account Number (ENR only)
$12.44 R44 Invalid Individual ID Number/Identification Number (ENR only)
$12.45 R45 Invalid Individual Name/Company Name (ENR only)
$12.46 R46 Invalid Representative Payee Indicator (ENR only)
$12.47 R47 Duplicate Enrollment (ENR only)
$12.50 R50 RDFI Not Qualified to Participate
$12.51 R51 Item ineligible, Notice Not Provided, or Item not Authorized
$12.52 R52 Payment Stopped
$12.53 R53 Item and ACH Entry Presented for Payment
$12.67 R67 Duplicate Return
$12.68 R68 Untimely Return
$12.69 R69 Field Error(s)
$12.70 R70 Permissible Entry Not Accepted/Return not Requested by ODFI
$12.71 R71 Misrouted Dishonored Return
$12.72 R72 Untimely Dishonored Return
$12.73 R73 Timely Original Return
$12.74 R74 Corrected Return
$12.75 R75 Original Return Not a Duplicate
$12.76 R76 No Errors Found
$12.80 R80 Cross border coding Error
$12.81 R81 System is Not a Participate in Cross border program
$12.82 R82 Invalid Foreign RDFI
$12.83 R83 Foreign RDFI unable to settle
$12.84 R84 Entry not Processed by OGO
$12.99 R99 WFB Deposit System Return or Reject. This item could not be processed with the Wells Fargo Bank account number provided.



Transaction Amount Triggers (deprecated)

These triggers may cease to function without notice. The following tables list current correspondences between transaction amounts and specific responses.

Note: These values were phased out in 2011 in favor of the ZIP code values.



$70.02 2 This transaction has been declined. General bank decline
$70.03 3 This transaction has been declined. Referral to voice authorization
$70.05 35 An error occured during processing.Call Merchant Service Provider
Unkown error occured during processing



AMOUNT Visa Mastercard American Express Discover
$70.40 E X E X
$70.42 A A A A
$70.43 Z Z Z Z
$70.44 N N N N
$70.45 U U U U
$70.46 S S S S
$70.47 R R R R
$70.48 E W N W
$70.49 P E Y E
$70.50 G E E E
$70.51 E E Z E
$70.52 Y E Y E
$70.53 E E A E
$70.54 E E U E
$70.55 Y E Z E
$70.56 E E Y E
$70.57 Y E A E
$70.60 A E E E
$70.61 G E
$70.62 Y E Z E
$70.63 Y E
$70.64 G E E E
$70.65 N E E E
$70.66 Y E Y E
$70.67 Z E E E
$70.94 P P P P



$70.70 M Successful Match
$70.71 N Does NOT Match
$70.72 P
Is NOT Processed
$70.73 S Should be on card, but is not indicated
$70.74 U Issuer not certified or has not provided encryption key  

Testing Account Updater

You can use the following card numbers to test the Account Updater service. If you create a customer payment profile in the developer sandbox using one of these numbers, that customer payment profile will receive the expected response when the Account Updater process runs. The payment profile itself will then be updated or deleted as appropriate for the specific response.

The Account Updater process in the developer sandbox runs at the same frequency as in production (once per month). Results are available the following month. There is no function to manually trigger an update.

Card Number Expected Result Profile Action Taken
Card number updated
Expiration date updated
Payment profile disabled
Payment profile deleted
Card number updated
Expiration date updated
Payment profile disabled
Payment profile deleted
XXXX7183 ACL Payment profile deleted