Testing in-person declined transactions

When a transaction attempt is declined by the issuing bank, the Helcim Smart Terminal API will return a declined payment via the Card Transaction webhook events.

Declined card transactions can be simulated in a test environment through the Smart Terminal when using a Helcim test account. This is done by sending final transaction amounts (inclusive of taxes, tips, fee saver amount) with specific decimal ranges to simulate possible decline reasons. The table below shows some of the decline codes that you can generate.

🚧

Developer Test Accounts

If you do not currently have access to a Helcim developer test account for your Smart Terminal API integration, please review our documentation here to get started.

Decline codes

Decline responses can be triggered by processing a payment with a specific transaction decimal amount.

We suggest a general catch all function for the majority of potential decline reasons, with a recommendation to the user of trying a different card or payment method. Many transaction declines can only reasonably be resolved by the end user connecting with their issuing bank for more information.

Showing more granular decline reasoning is only recommended where a change in user behaviour may result in a different transaction outcome if attempted a second time, such as incorrect PIN.