Test Cards
Generic and Custom Test Cards will not hit the gateway.
Approved Test Card orders will generate a fulfillment record but will not send to a fulfillment plugin. Be cautious if your operation utilizes the System Fulfillment option (except Shopify orders being sent back to Shopify).
Approved Test Card orders will fire affiliate pixels but these sales will not display on the Affiliate Report.
Custom Test Cards
Under the Admin tab navigate to the Test Cards page.
Click on the Green + Button to add a new Test Card.
Here you can enter your own test card or randomly generate one. Once you have created your Test Card hit the Green Submit Button.
To Delete a Test Card, simply hit the Trash Can icon next to the Test Card you want to delete.
Generic Test Cards
Click on the Generic Test Cards tab to view the default CheckoutChamp Test Cards
To disable the Generic Test Card, hover over the hamburger menu in the top right corner of the CRM. Click on Account Scroll down to the Additional Options section and click on checkbox next to “Disable Generic Test Cards”. Click the Blue Save Button to Save.
Using Test Cards
Generic and Custom Test Cards will not hit the gateway.
Approved Test Card orders will generate a fulfillment record but will not send to a fulfillment plugin. Be cautious if your operation utilizes the System Fulfillment option.
Approved Test Card orders will fire affiliate pixels but these sales will not display on the Affiliate Report.
Generic Test Card Number | 0000000000000000 |
Generic Test CVV (Also applies to custom test cards) | Any not listed below: Approved 9xx: Declined 7xx: Simulate Debit Card 8xx: Simulate Prepaid Card |
3DS Test Card with URL Response | 0000000001111111 |
3DS Test Card with JavaScript Response | 7111111111100000 |
3DS Test CVV | 111: Approved (Frictionless) 199: Declined (Frictionless) 555: Challenge |
Card Expiry Date | Any Month and Year not expired |
To test with a created or generic test card, process an order with the normal order flow. Use the table provided above to simulate certain card types and outcomes.
Simulate Debit Cards
You can simulate a debit card by using the test card as normal and a CVV of 7xx. To decline a debit card, set the gateway you are using to block debit cards. View Adding a Gateway for details on how to block debit cards.
Simulate Prepaid Cards
You can simulate a prepaid card by using the test card as normal and a CVV of 8xx. To decline a prepaid card, set the gateway you are using to block prepaid cards. View Adding a Gateway for details on how to block prepaid cards.
Simulate 3DS
In order to simulate 3DS, you must handle the 3DS process flow. Please view Basic 3DS Instructions for instructions on how to handle the 3DS process flow.
You can simulate 3DS by using either the 0000000001111111 (3DS URL response) or the 7111111111100000 (3DS JavaScript response) test cards. Aside from the response, the cards will function identically.
Challenge Flow
Typically, in a 3DS transaction, the customer is redirected or a window is displayed in which the customer is asked to verify their identity. This is typically a called a “challenge.” To simulate a 3DS challenge, use one of the 3DS cards and a CVV of 555.
If you have correctly handled the 3DS process flow, you will be redirected to a page that looks like this.
When you are redirected to the 3DS Response Tester page, you can see that a transaction is created in the CRM.
Select the desired Test Result and hit the Submit button. If the test was successful, you will see the transaction marked as *3DSecure in the CRM.
You can also simulate a customer quitting the 3DS process flow by leaving the page. In this case, the transaction will remain with a Redirect Pending response for 3-6 hours before being reprocessed. If it has been reprocessed, the transaction will be updated.
Frictionless Flow
Occasionally, a customer is able to go through the 3DS process flow without being shown a challenge. This is typically called a “frictionless flow.” To simulate a frictionless 3DS flow, use one of the 3DS test cards and a CVV of 111 (for a Success response) or 199 (for a Decline response).
If you have correctly handled the 3DS process flow, you will see the transaction marked as *3D Secure in the CRM.
Last updated
