What is the Sandbox?

The Sandbox functions as a simulator of our production environment. You send your transactions to our 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!

For now the Sandbox only supports online transactions and needs at least version 8. 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 prelive 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, the last 3 digits of the credit card will be used for the response reason code. Some sample numbers/responses include:

Desired Response	Credit Card Number
000: Approved	4470330769941000
010: Partially Approved	4658512425423010
100: Processing Network Unavailable	4886883711815100
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 2-4 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 red are the three feature identifiers.

A simple example is the following card number:

Characters: 01 234 567 89012 345
            41 002 801 90123 000
                

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.

Available Features

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 what are 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
4100322311199000	003	Enhanced Authorizations	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	Card validation result 0 - 'M' 1 - 'N' 2 - 'P' 3 - 'S' 4 - 'U'
4100811234567000	008	Merchant Category Code Validation	MCC validation result is in message tag 0 - Approved 1 - Submitted MCC not allowed

eCheck

Use 3-digit amount, or last 3 of the amount, to specify the desired responses, Some sample numbers/responses include:

Desired Response	Credit Card Number
000: Approved	12000
368: Invalid Check Number	12368
900: Invalid Bank Routing Number	12900

Applepay

Use 3-digit amount to specify the desired responses, Some sample numbers/responses include:

Desired Response	Transaction Amount
000: Approved	000
010: Partially Approved	010
100: Processing Network Unavailable	100
101: Issuer Unavailable	101
110: Insufficient Funds	110

For Applepay, when the amount is not in this table or not a 3-digit number, the transaction will automatically be approved and return '000' as the response code, 'Approved' as the response message.

Androidpay

Use 3-digit amount to specify the desired responses, Some sample numbers/responses include:

Desired Response	Transaction Amount
000: Approved	000
010: Partially Approved	010
100: Processing Network Unavailable	100
101: Issuer Unavailable	101
110: Insufficient Funds	110

For Androidpay, when the amount is not in this table or not a 3-digit number, the transaction will automatically be approved and return '000' as the response code, 'Approved' as the response message.

Standalone Fraud Check

Use the first three customAttribute tags to dictate the desired responses.

Response Attribute	Desired Response	Custom Attribute Number	Attribute Value
deviceReviewStatus	pass	customAttribute1	pass
deviceReputationScore	42	customAttribute2	42
triggeredRule	1 to 11	customAttribute3	number of triggeredRule tags returned

For standalone fraud checks the customAttribute3 tag is used to dictate the number of triggeredRule tags returned in the response. One triggeredRule tag will always be returned by default from the Sandbox and a maximum of 11 triggeredRule tags will be returned.

eProtect

Use 3-digit amount to specify the desired responses, Some sample numbers/responses include:

Desired Response	Transaction Amount
000: Approved	000
010: Partially Approved	010
100: Processing Network Unavailable	100
101: Issuer Unavailable	101
110: Insufficient Funds	110

Getting started

The URL to send your transactions to our Sandbox is the following:

NOTE: Requests made to the Sandbox environment require the connection be TLS 1.2

You can test with any tool that can generate HTTP requests, curl is one example. To start you can save the following in an xml file:

And then send the file to Sandbox using your HTTP tool. You need to add the header Content-Type: text/xml so that we know you're requesting an XML. The following would be the curl command to submit the previous XML:

Please check that you don't have a proxy setup. If you do have a proxy setup, the command to submit the previous XML with Proxy: