Sandbox

Are there Test Card Numbers to use in the Sandbox Environment?

PCI requires us and you to use test card numbers when testing. You should never use a real Card Number in the Sandbox Environment. We provide various test cards for various scenarios for your use.

How to generate an error in the Sandbox Environment? (Create Transaction)

For Create Transaction, the Amount is used to trigger various errors while processing the Create Transaction request in the Sandbox Environment (Accel uses a 3-digit Network Response Code):

Amount Response Code Actual Response Error Description
Status Code Network Response Code Resource Status Network Response Code Resource Status
0.01 200 ZZ (or 999) ERROR ZZ (or 999) ERROR Transaction Error
11
0.02 207   UNKNOWN   UNKNOWN Transaction Processing Failed
12
0.03 200 00 (or 000) COMPLETED 00 (or 000) COMPLETED Transaction Successful, but upstream processing was delayed for 30 seconds
13
0.04 207   UNKNOWN 00 (or 000) COMPLETED Transaction Successful, but upstream processing was delayed for 40 seconds
14

How to generate an error in the Sandbox Environment? (Delete Transaction)

For Delete Transaction, the Create Transaction Amount is used to trigger various errors while processing the Delete Transaction request in the Sandbox Environment (Accel uses a 3-digit Network Response Code):

Amount Create Transaction Response Delete Transaction Response Error Description
Status Code Network Response Code Resource Status Network Response Code Reversal Network Response Code Resource Status
0.07 200 00 (or 000) COMPLETED 200 ZZ (or 999) UNKNOWN Reversal Request failed
0.08 200 00 (or 000) COMPLETED 200 21 UNKNOWN Reversal Request failed, the Reversal was too late.
Not available when routed to any Regional Network: Currently only STAR and Accel.

How to generate an error in the Sandbox Environment? (AVS, CVV2)

For AVS, Query Card, the Zip Code, Address, and Security Code are used to trigger various conditions while processing an AVS request in the Sandbox Environment:

Request Response Comments
Zip Code Address Security Code Response Text Network Response Code Code
AVS Results Security Code Results
Any* Any* None NOT DECLINED 85 Y   Zip Code and Address were matched
Any* None None NOT DECLINED 85 Z   Zip Code was matched
Any* Any or None Any* DEPENDS DEPENDS DEPENDS M Depends upon if Zip Code and Address matches or not, but Security Code was matched
Any* Any or None 999 DECLINE 5 DEPENDS N Depends upon if Zip Code and Address matches or not, but Security Code was not matched
99990 Any or None Any or None DECLINE 5 U   Information not available
99991 Any or None Any or None DECLINE 5 R   AVS unavailable, retry
99992 Any* None DECLINE 5 A   Zip Code was not matched, but Address was matched
99992 None or 999 Bad None DECLINE 5 N   Zip Code and Address were not matched
99993 Any or None Any or None DEPENDS DEPENDS DEPENDS DEPENDS AVS Request delayed for 30 seconds
99994 Any or None Any or None UNKNOWN UNKNOWN UNKNOWN UNKNOWN AVS Request timed out
  • Any* - Any Zip Code that is not explicitly used to trigger a condition (99990-99994)
  • Any* - Any Address that is not explicitly used to trigger a condition (999...) - Address only checks the Street Number
  • Any* - Any Security Code that is not explicitly used to trigger a condition (999)

How to generate a RTP error in the Sandbox Environment?

For Create Transaction, the Account Number for RTP is used to trigger various errors while processing the Create Transaction request in the Sandbox Environment (RTP uses a 3-character Network Response Code):

Account Number Create Transaction Response Error Description
Status Code Network Response Code Resource Status
100000000...111111111 200 0 COMPLETED N/A
111111112 200 P04 ERROR Invalid Account
111111113 200 P11 ERROR Sender not authorized
111111114 200 P07 ERROR Participant blocked
111111115 200 P02 ERROR Invalid Account
111111116 200 P11 ERROR Transaction forbidden on this account
111111117 200 P23 ERROR Amount received is not the amount agreed or expected
111111118 200 P23 ERROR Amount exceeds limits
111111120 200 P21 ERROR Incorrect routing number
111111121 200 P14 ERROR Participant deceased

-

Is the Sandbox Environment PCI Compliant?

No. You should be using Test Card Numbers when testing in the Sandbox Environment. You should never use a real Card Number in the Sandbox Environment. We provide various Test Card numbers for various scenarios.

What is the Sandbox Environment SLA?

There should be no expectations on the Sandbox Environment.

Running Performance Test?

You can not run a Performance Test in the Sandbox Environment. The Sandbox Environment is a very small fraction of the Production Environment. It would be a waste of everyone's resources to do a Performance Test using the Sandbox Environment.

What happens if someone decides to run a Performance Test?

Your IPs will be blocked.

How quickly can we do a change (configuration) on the Sandbox Environment?

We are PCI Level 1 and SOC1 Type 1 and SOC2 Type 2 Compliant. So, what does that mean? We are procedure and process controlled.

Some companies require us to be PCI Level 1 and SOC Compliant (SOC1 Type 2 and SOC2 Type 2). And then some of those same companies still expect us to do things for them immediately (and even on Production).

Here is a real life example that recently occurred:

  • A Client demanded to change their limit on a weekend night immediately
  • After changing their Limit, the same Client later demanded to change their limit again and again on a weekend night immediately
  • After changing their Limit again, we see they never reached the Limits they demanded, in fact, they never even reached their original Limit
    Not everything is or can be an emergency!

Schedule for Sandbox changes:
(1) Have your request by Friday morning
(2) Changes will be implemented by end of day Monday (or Tuesday, if Monday is a Holiday)

So please plan ahead. This includes boarding new clients, changing limits, allowlisting IPs, etc.