The eCommerce Sandbox functions as a simulator of our production environment. You send your transactions to the sandbox environment the exact same way you’d send them to our certification or production systems. The sandbox validates the transaction format and approves it if it matches our requirements. The Sandbox server makes it easy to get started using our SDKs. There are no forms to fill out, no credentials required, and no special access needed!
You can register for an account here. All you need is your e-mail address and organization name.
The eCommerce Sandbox supports online transactions only and needs at least version 8 of LitleXML. It has no state and doesn't actually tie the transactions with one another, but it does simulate responses for tied transactions. To test your batch transactions, you'll need access to our pre-live environment.
How does it work?
The Sandbox uses the request to calculate the response. This is done so that any response that our systems can generate can be retrieved through the Sandbox as well. For Sale and Auth transactions, the last three digits of the credit card will be used for the response reason code. Some sample numbers/responses include:
|Desired response||Credit card number|
|010: Partially Approved||4658512425423010|
|100: Processing Network Unavailable||4215176886320101|
|101: Issuer Unavailable||4215176886320101|
|110: Insufficient Funds||4488282659650110|
Other numbers in the credit card can be used to simulate a variety of features, including AVS, CVV, Auto AU, etc. To identify the feature, characters two to four are used and depending on the feature, other characters will be used. The following shows how we count the characters from the card number and highlighted in green are the three character feature identifiers.
A simple example is the following card number:
The green characters specify the feature (in this case Vault). The red characters specify the token response code. The blue digits specify the response reason code, as explained above.
The following table shows all the features available and the meaning for the special characters. You can try with different values for each one of them and check the responses that you get back.
|Example Card Number||Feature Identification||Feature||Other characters|
|4100117890123000||001||Account Updater||Nothing needed, new randomly generated card number will be returned|
|4100280140123000||002||Vault/Tokenization||5-7 - Token response code|
5 - Funding Source Type
6 - Reloadable
7 - Prepaid card type
8 - Affluence
9 - Issuer Country
|4200410886320101||004||Address Verification (AVS)||5-7 - AVS response code|
|4100521234567000||005||Card Security Code Validation||5 - Card validation result|
Use a three-digit amount to specify the desired responses, Some sample numbers/responses include:
|Desired response||Transaction amount|
|010||Partially Approved 010|
|100||Processing Network Unavailable 100|
|101||Issuer Unavailable 101|
|110||Insufficient Funds 110|
For Apple Pay, when the amount is not in this table or not a three digit number, the transaction will automatically be approved and return '000' as the response code, 'Approved' as the response message.
The URL to send your transactions to our Sandbox is the following:
Sample XML transactions and command lines using curl are provided on the eCommerce GitHub site that exercise the Sandbox.