Test card numbers

Clover provides you with test card numbers to trigger specific scenarios at the payment gateway, such as declines and partial transactions. You can:

• Use the test card details to test each payment flow and ensure your application processes the payment as expected.
• Use any three digits for the card verification value (CVV)/card verification code (CVC). For example: 123
• Use any future date for the expiration date.

📘

NOTE

The Ecommerce API declines partial auth transactions. Hence, the Visa test card number for partial amount approvals will be declined.

Scenario-specific card details

You can simulate transactions for any root cause analysis with scenario-specific card details. For example, if you want to analyze a transaction failure status, use card details to simulate transaction decline in the Simulate declines section.

Simulate successful transactions

Use the following test card details to simulate a successful transaction in the test mode.

📘

NOTE

Use the address and CVV/CVC data with any card numbers listed above to complete the address and CVV/CVC checks. If you do not set the address and CVV/CVC data, the value address and CVV/CVC are null.

Ecommerce test cards for AVS success scenarios

To test the Address Verification Service (AVS) success scenarios, use any of the following test card numbers with any United States postal or ZIP code.

Simulate declines

Use the following test cards to have the payment gateway return a declined response.

Test specific error codes

The following table gives suggestions for testing some specific error codes:

Ad hoc tests

In addition to the Unit and Certification test scripts in your software development kit (SDK), Clover lets you create test cases. Use the following test card details to create test cases that you can use with your test merchants accounts in the Clover sandbox environment.

Testing tips valid for all cards

For testing purposes, specific payment values are aligned for various test scenarios. For example:

• Transactions for $45.67 receive a No Host Response to simulate time-out reversal testing.
• Transactions below $100.00 receive an Approved response.
• Transactions above $100.00 receive a specific Error response.
• Transaction amount sent in the transaction request message determines which error response code is received in your response. To request an error response code, the last three digits of the transaction amount are the response code you want to receive. For example:
  • To receive a response message with a 116 response code, then the request message could contain a transaction amount of $101.16.
  • To receive a response message with a 318 response code, then the request message could contain a transaction amount of $403.18.