Please test your integration before going live. Whether you are using the hosted payment pages or our Remote XML API, you need to verify your setup through real usage, both so you’ll know that your configuration options are correct, and so you’ll know more about what your customers will experience.
To send a test Sale or Authorize payment request you will need to send in the request the tag test set to the value true and you will need to use a valid payment method test data as shown below.
Do not forget to ask our support to disable test mode after you are finished with the integration.
Card numbers to process Sale and Authorize transactions with verification value
| Credit Card Brand | Credit Card Number |
|---|---|
| VISA | 4012888888881881 |
| Mastercard | 5105105105105100 |
| American Express | 378282246310005 |
| Discover | 6011000990139424 |
| Diners Club | 30569309025904 |
| JCB | 5105105105105100 |
Card numbers to process Sale and Authorize transactions without verification value
| Credit Card Brand | Credit Card Number |
|---|---|
| VISA | 4111111111111111 |
| Mastercard | 5555555555554444 |
| American Express | 371449635398431 |
| Discover | 6011111111111117 |
| Diners Club | 38520000023237 |
| JCB | 3530111333300000 |
The table below shows an expiration month you should use to get the desired transaction status.
| Expiration Month | Expiration Year | Transaction Status | Batched ? |
|---|---|---|---|
| 01, 08, 09, 10, 11, 12 | 2016 | success | no |
| 02, 05 | 2016 | fail | no |
| 03, 06 | 2016 | error | no |
| 04, 07 | 2016 | success | yes |
The table below shows card numbers you should use to get a desired 3-D Secure enrollment status.
| Credit Card Number | 3-D Secure Enrollment Status | 3-D Secure Enrollment message |
|---|---|---|
| 4012001038443335 | N | Cardholder Not Enrolled |
| 4012001038488884 | U | Unable to Authenticate |
| Credit Card Number | 3-D Secure Authentication Status | 3-D Secure Authentication message |
|---|---|---|
| 4222222222222 | Y | Authentication Successful |
| 4012001036273338 | A | Attempts Processing Performed |
| 4012001037141369 | U | Authentication Could Not Be Performed |
| 4012001037461114 | N | Authentication Failed |
All Capture, Void, Refund transactions return status success. You must send them on previously created Sale or Authorize transactions.
Account and Routing numbers to process Sale transaction
| Account Number | Routing Number | Transaction Status | Batched ? |
|---|---|---|---|
| 000000001 | 123456789 | success | no |
| 000000002 | 123456789 | fail | no |
| 000000003 | 123456789 | success | yes |
Account and Routing numbers to process Sale transaction
| Account Number | Routing Number | Transaction Status | Batched ? |
|---|---|---|---|
| 000000011 | 123456789 | success | no |
| 000000012 | 123456789 | fail | no |
If you plan to work with acquirer that work in scheme of deferred transaction processing you can test your codebase using our test mechanism. To do this you should use payment method data to get transaction in batched state, and then emulate notification from a real acquirer by using notification url for test acquirer.
The application receives only POST requests on this url and check for only one parameter id which should be id of transaction you want to process.
Notification URL for Credit Card:
https://secure.certodirect.com/notifications/dummy_card
https://secure.certodirect.com/notifications/dummy_check