The ACHQ API supports sandbox, development and production modes through a single API endpoint. Please note the following methods for differentiating and controlling your integration mode for the ACHQ SpeedChex API:
Sandbox Mode - ACH payments are sent to a Sandbox account where they are captured, stored and show up in status tracking reports and queries - but they are never sent to the Federal Reserve for processing. You must use the following credentials for sending payments to the Sandbox account
Development Mode - In Development mode, ACH payments are submitted to the ACHQ API using your production credentials with a TestMode parameter set to "On". Payments submitted in this mode will receive a valid success or failure response, but unlike Sandbox and Production modes - these ACH payments are never stored on the ACHQ platform for processing or made available for reporting and status tracking queries.
The following sandbox credentials and bank account rules may be helpful for testing your integration:
One number to rule them all
Use a value of "123123123" as the routing number for all testing scenarios
|Test Bank Account
|Sandbox Testing Scenarios
|Transaction status marked as Returned NSF on the next banking business day
|Transaction status marked as Returned Other (administrative return) on the next banking business day
|Transaction status gets marked Cleared and then it gets marked to Charged Back on the next business day
|Transaction fails Express Verify and is immediately rejected
|Fails bank account ownership authentication on the Echeck.VerifyPlus command
|All other account numbers
|Passes all bank account verifications.
Don't use sensitive data when testing
Merchant ID 2001 is a public test account. Any information you transmit may be viewed by users running the ACHQ demo. This includes payment accounts, names, addresses, phone numbers, and email addresses. Please always use fabricated test information.
Updated 8 months ago