Error codes
In the world of payment processing, errors can occur during transactions. When a transaction fails, it’s essential to understand the associated error code and message to troubleshoot and resolve the issue. The IXOPAY platform provides comprehensive error code documentation to assist you in handling errors effectively. This article focuses on the IXOPAY platform’s errorCode and errorMessage.
If the error is produced by any subsequent system (bank, PSP, PayPal, etc.), the error element will also contain the adapterCode and adapterMessage, reflecting directly the response of those systems.
Structure
The error codes in the IXOPAY platform documentation are organized into different groups, reflecting the phase in which an error occurred. These groups include:
- General errors and validation errors
- Payment errors
- Network errors
- Post-processing errors
- Schedule API errors
- Status API errors
By categorizing errors, you can quickly identify the nature of the issue and take appropriate action to resolve it.
While there can be thousands of different adapter error codes depending on the configured connectors, this documentation focuses on the consolidated error codes provided by IXOPAY platform. These consolidated error codes are typically the ones you’ll want to consider for effective error handling.
Within each group, you will find detailed information about specific error codes, including their meanings, potential causes, and recommended actions.
Please note that the “Default message” column provides the standard error message associated with each error code. However, in some cases, the actual message returned in the API response may be expanded with additional information or entirely changed based on specific circumstances. For reliable error handling in your application, always depend on the error code rather than the error message.