Testing 'decline' responses in Demo Mode

Most gateways allow you to test various 'decline' responses in their sandbox environments. This is typically done by using reserved card numbers, specific CVV codes or processing transactions with certain amounts.

This guide will contain detailed information on how to simulate some common 'declined' responses for each gateway.

Trust Payments (Secure Trading)

Trust Payments (Secure Trading) allows you to test declines by using reserved card numbers. The table below shows a list of card numbers for various card types for both 'Authorized' and 'Declined' responses.

Further information can be found in the test documentation

Authorize.Net

Authorize.Net allows you to test declines by submitting a reserved zip code when entering the card. Below you'll find a list of testing cards for Authorize.Net as well as the zip code used to test declines. 

Further information can be found in the Authorize.Net testing guide

Cybersource

Cybersource allows you to test declines by submitting specific transaction amounts. Below you'll see a list of testing cards as well as a transaction amount to use for a 'declined' response.

Further information can be found here

Eway

Eway does not allow you to test declines in the sandbox environment. If you use the demo-cards listed below in the Live environment, you will get a 'declined' 

Moneris

Moneris allows you to simulate responses based on the cent-value of the amount as described below. There's also a list of credit cards that can be used on the sandbox environment.

Further details can be found here

Cayan

Cayan allows you to simulate declines by submitting specific amounts for certain credit cards as seen below.

For further information, refer to the Cayan test guide

Further information can be found here

ProPay

For ProPay it is possible to simulate specific response codes based on card numbers and specific amounts.

For further information, refer to the ProPay API Appendix