Test card numbers

Merchants can use the following card numbers to trigger specific scenarios at the gateway, such as declines and partial transactions. A gateway will need to be setup with a Rapid Connect processor, which must be the default setting. Verify this setting by calling the GET v3/merchants/{mid}/gateway endpoint and confirm that the paymentGatewayApi value begins with fdcrcip. If the value is blackhole, email [email protected] to request this be changed to Rapid Connect.

You may use any three digits for the CVV and any future date for the expiration.

📘

NOTE

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

Simulating successful transactions

In test mode, you can use the following test cards to simulate a successful transaction.

📘

NOTE

By default, passing address or CVC data with the card number will cause the address and CVC checks to succeed. If not specified, the value of the checks will be null. Any expiration date in the future will be considered valid.

Ecomm test cards for AVS success scenarios

To test Address Verification Service (AVS) success scenarios, use one of the following test card numbers with any U.S. zip code:

Simulating declines

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

Testing specific error codes

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

Ad hoc testing

In addition to the Unit and Certification test scripts in your SDK, Clover has established functionality that allows you to create your own test cases. The following test card examples are provided for this purpose and should only be used with the "Test Merchants" generated as part of their developer account on Clover's Sandbox.

For all cards

Transactions in the amount of $45.67 will receive a "No Host Response" to simulate time-out reversal testing. Therefore:

• Transactions below $100.00 will receive an Approved response.
• Transactions above $100.00 will receive a specific Error response.

The transaction amount sent in the transaction request message is used to determine which error response code will be received in your response. To request an error response code, the last three digits of the transaction amount should be the response code you want to receive. For example, if you need to receive a response message with a 116 response code, then the request message could contain a transaction amount of $101.16. Likewise, if you need to receive a response message with a 318 response code, then the request message could contain a transaction amount of $403.18.