Payment methods for testing
Use these test cards and accounts to simulate transactions in your sandbox. You can use these example cards and accounts to make test transactions via the API or any of Payabli’s hosted payment solutions, like the virtual terminal or payment pages.
Simulate a successful transaction
Use these test cards and accounts for transactions in sandbox.
Cards
Use these with any future expiration date.
ACH
Use this with any account type.
Simulate a decline
You can use test cards to simulate card declines. For questions about ACH decline testing, contact your Payabli solutions engineer.
How a decline is returned depends on the API version. The v2 endpoints return HTTP 402 with a response code that starts with D, and v1 endpoints return HTTP 200 with isSuccess set to false. For the full response, see Make a transaction. For the v2 codes, see unified response codes.
Decline rate limiting
Using a test card repeatedly in a short period can sometimes cause it to be blocked. As a best practice, Payabli recommends adhering to the fraud control limits. See fraud control for more information. Reach out to your Payabli solutions engineer with any questions or issues related to testing declines.
Transaction declines
You can simulate a transaction decline by using the following card in a transaction request with any future date for the expiration date:
Stored method declines
To simulate a decline when charging a stored payment method, you can store a payment method with any of the following test cards and a future expiration date. The stored payment method can be charged with an amount of $0.20 (20 cents) to cause a declined transaction.
Invalid CVV declines
To simulate a decline due to an invalid CVV, you can use any of the following test cards with an incorrect CVV:
Related resources
See these related resources to help you get the most out of Payabli.
References
- Pay In schemas - Learn about Pay In (money in) transaction schemas
- Pay In statuses - Learn about Pay In (money in) statuses