Sandbox Validation
All clients must successfully execute specific scenarios in the Sandbox environment validating the integration. Upon successfully completing specific scenarios, the implementation team will generate and provide Production environment credentials.
The below scenarios must be successfully executed in the Sandbox environment to validate the integration through the client's application or user interface; not a code development tool. Prior to validation, all required and optional fields desired by the business users must be integrated. Validation in the Sandbox environment may utilize the card information below:
Sample Test Cards (for credit card sales)
Card Type | Card Number | Security Code | Zip Code |
---|---|---|---|
Visa | 4012000098765439 | 999 | 85284 |
MasterCard | 5499740000000057 | 998 | 85284 |
MasterCard | 2223000048400011 | 998 | 85284 |
Amex | 371449635392376 | 9997 | 85284 |
Discover | 6011000993026909 | 996 | 85284 |
Card Scenarios and Actions
Scenario | Actions | Expected Results |
---|---|---|
Sale & Purchase - Basic |
| A virtual card that corresponds with the ITC that was returned in the sales call is created. |
Sale - Risk Decline |
| Sale fails with an auth decline response. “status”:”Transaction – Declined” |
Sale – Declined Authorization | Submit a sale transaction with CVV values that do not match. | Sales submitted with CVV codes that do not match the above sample values will return an auth decline response |
Sale - Void |
| Sale is voided and customer not charged for transaction. API response includes 201 code (created.) |
Purchases – Exceed Virtual Card Issuing Limit |
| Request to issue more virtual cards than defined in the “ExpectedPayments” parameter fails. {"message": "This incoming transaction code is not registered in the Issue Card database or it's already closed or voided: 01ZZZTAS66904111900003500"} |
Purchases - Exceed Virtual Card Amount Limit |
| Request to issue a virtual card for more than the original sale will fail. {"message": "Amount requested ($xx.xx) is greater than authorized amount ($xx.xx)"} |
Cash Scenarios and Actions##
Scenario | Actions | Expected Results |
---|---|---|
Cash Sale | Submit a cash sale transaction (Tender Type: "TenderType": "cash" | The Sale is processed and an ITC is created. |
Purchase | Request a virtual card from the sale. | A virtual card that corresponds with the ITC that was returned in the sales call is created. |
Purchases – Exceed Virtual Card Issuing Limit |
| Request to issue more virtual cards than defined in the “ExpectedPayments” parameter fails. {"message": "This incoming transaction code is not registered in the Issue Card database or it's already closed or voided: 01ZZZTAS66904111900003500"} |
Purchases - Exceed Virtual Card Amount Limit |
| Request to issue a virtual card for more than the original sale will fail. {"message": "Amount requested ($xx.xx) is greater than authorized amount ($xx.xx)"} |
Return a Cash Sale |
| The return is processed and the virtual card is deactivated. |
ACH Sales Scenarios and Actions
Scenario | Actions | Expected Results |
---|---|---|
ACH sale - success |
Routing number: 042000314 | No error |
ACH sale transaction where routing number fails |
Routing number: 042000313 | “Routing number validation error” |
ACH sale transaction where account number fails |
Routing number: 042000314 | “AccountNumber cannot be greater than 17 characters” |
ACH Purchase Scenarios and Actions
Scenario | Actions | Expected Results |
---|---|---|
Issue ACH success |
Routing number: 042000314 | No error |
Issue ACH where routing number fails |
Routing number: 042000313 | “Routing number validation error” |
Issue ACH where account number fails |
Routing number: 042000314 | “AccountNumber cannot be greater than 17 characters” |
For questions on Solution Validation in the Sandbox environment contact the CXP implementation team.
Updated 11 months ago