Documentation Index
Fetch the complete documentation index at: https://docs.ecrypt.com/llms.txt
Use this file to discover all available pages before exploring further.
Testing your implementation will ensure your integration will successfully run transactions for common payment flows and prepare you for certification before going live. Failure to run these basic test cases will result in your integration potentially not working correctly and creating issues down the road.
Basic Test Cases
- Authorization
- Authorization, capture
- Authorization, partial capture
- Sale
- Refund
- Credit
- Void
Test Cards (U.S.)
| Card Type | Value |
|---|
| Visa | 4111111111111111 |
| MasterCard | 5431111111111111 |
| Discover | 6011000991300009 |
| American Express | 341111111111111 |
Test Cards (Canada)
| Card Type | Value |
|---|
| Visa | 4242424242424242 |
| MasterCard | 5454545454545454 |
| Discover | 6011000992927602 |
| American Express | 373599005095005 |
Guidelines for Testing U.S. Credit Cards
- Credit card expiration dates should be any month and year in the future.
- To cause a declined message, pass an amount less than
1.00.
- To trigger a fatal error message, pass an invalid card number.
- To simulate an AVS match, pass
888 in the address1 field and 77777 for zip.
- To simulate a CVV match, pass
999 in the cvv field.
Guidelines for Testing Canadian Credit Cards
- Credit card expiration dates should be any month and year in the future.
- Transactions in the test environment must not exceed
$11.00.
- To cause a declined message, pass a transaction amount of
$0.05.
- To trigger a fatal error message, pass an invalid card number.
Test ACH (U.S. Only)
| Account Data | Value |
|---|
| ACH Direct Deposit Account | 123123123 |
| ACH Routing Number | 123123123 |
Triggering Errors in Test Mode for ACH
- To cause a declined message, pass an amount less than
1.00.
- To trigger a fatal error message, pass an invalid card number.
Test Credit Card Terminal Transactions
There are two methods of testing terminal transactions: using a physical terminal and using the Virtual Payment Terminal (VPT).
Physical Terminal
You can initiate a terminal transaction with ECRYPT’s POS modal. Your device must be registered to your ECRYPT account before initiating a sale. Follow the steps below to run your first test transaction:
- Navigate to the quick action button on the top left of the ECRYPT dashboard.
- Select +POS.
- Select Sale for transaction type and complete the rest of the form fields.
- Click Send to Terminal.
- Your terminal device will display a request for the transaction and sale amount. Complete the transaction by following the steps on the device.
- Once the transaction is complete, navigate to Open Transactions in the ECRYPT dashboard — your transaction will appear at the top of the table.
Virtual Payment Terminal (VPT)
VPT is a fully functioning virtual payment terminal designed to expedite integration times and remove the requirement for “beta” payment terminals. VPT registration and transaction processing simulates physical payment terminal interactions for auditing, reporting, and testing.
Note: VPT is currently limited to VISA EMV. VPT does not support handling “prompts” at this time, though sending the variables in your request will not cause errors. Visit the terminal reference page to access the API endpoint for creating terminals.
Test Data
Registration requests can be submitted using the following information:
- Registration Code:
T00001 — Successful
- Registration Code:
T00002 — Failed
- Amount:
1.00 (amounts under 1.00 generate a failure)
Triggering Errors in Test Mode
- To cause a declined response, pass an amount less than
1.00.
- To trigger a fatal error message in processing, pass an invalid Payment Terminal ID.
