Transaction errors are issues that occur during the payment process, preventing a transaction from being completed successfully. These errors can result from a variety of factors, including technical issues, user actions, and external dependencies. Properly identifying and handling these errors is essential to ensure a smooth transaction process, provide users with clear feedback, and improve overall system reliability.
Provider inaccesible: this error occurs when the payment provider is unavailable. This can be due to maintenance, connectivity issues, or outages with the provider, preventing the transaction from being processed.
Insufficient funds: this indicates that the customer’s account doesn’t have enough funds to cover the transaction amount. This is common with bank accounts or debit card payments and can sometimes be resolved by retrying once funds are available.
No longer valid: this error occurs when a transaction has been invalidated, often due to an expired authorization, canceled card, or outdated customer account information.
Customer canceled: this error occurs when the customer associated to the payment method no longer exist. It is typically a voluntary action by the user.
Insufficient data: this error means that the necessary information required to complete the transaction is missing or incomplete. Missing details can include card numbers, expiration dates, or account identifiers, preventing the transaction from proceeding.
Provider bad configuration: this error occurs when there’s an incorrect setup or misconfiguration on the payment provider’s side, such as wrong API keys, settings, or permissions. It may require adjustment on the provider’s system or in the integration configuration.
Unknown error: this is a general error that signifies an unexpected or undefined issue that wasn’t categorised specifically. It can arise from unhandled exceptions, unknown issues with the provider, or system glitches, and requires investigation for a specific resolution.