Response handling is an important aspect of processing callbacks in the IXOPAY platform payment processing workflow. Ensuring that your system responds with the appropriate status code and content not only acknowledges the receipt of the notification but also helps avoid potential delays or duplicate notifications.
To further enhance your understanding of callback handling in IXOPAY platform, explore the following articles:
- Callback data: Detailed information on the structure and format of callback data.
- Notification types: Learn about the different types of notifications sent by IXOPAY platform.
To handle callbacks effectively, follow these general steps:
- Implement a callback endpoint in your system to receive notifications from IXOPAY platform.
- Ensure that a
callbackUrlfield is set on the transaction to specify the callback endpoint where notifications should be sent. Alternatively, you can enable callbacks on the connector settings.
- Optionally, validate the authenticity of the received notification using the provided request signature.
- Process the received notification data according to your business logic.
- Acknowledge the receipt of the callback.
For detailed step-by-step instructions on implementing callback handling, refer to the Guides: Callbacks article in the Guides section. It provides comprehensive guidance on setting up and implementing callbacks in your integration.
Acknowledging callback receipt
When your system receives a callback from IXOPAY platform, it is essential to acknowledge the receipt of the notification by responding with an HTTP status code
200 and a response body of
HTTP/1.1 200 OK
Content-Type: text/plain; charset=UTF-8
The initial callback from IXOPAY has a timeout of 10 seconds, which means your system's response should not take longer than this. Subsequent callbacks have a timeout of 30 seconds. Please note that these timeout durations might change in the future, and this page will be updated if that happens.
If your system does not provide a confirmation response with an HTTP status code
200 and content
OK, IXOPAY will continue to retry sending the notification at increasing intervals according to the following schedule:
|First retry||1 minute|
|Second retry||5 minutes|
|Third retry||15 minutes|
|Fourth retry||1 hour|
|Fifth retry||2 hours|
|Sixth retry||3 hours|
|Seventh retry||12 hours|
|Final retry||Once every 24 hours for 7 days|
During these retries, IXOPAY platform will continue attempting to send the notification to your callback endpoint. It is important to ensure that your system responds with the appropriate status code and content to acknowledge the receipt of the notification and avoid any potential delays or duplicate notifications.
The IXOPAY platform signs every callback request it sends to the merchant, providing an additional layer of security and ensuring the authenticity of the data. While signature verification is optional, it is highly recommended to verify the signature for enhanced security.
To verify the signature of a callback request, follow these steps:
- Compute the signature on your system using the provided shared secret and the appropriate hashing algorithm.
- Compare the computed signature with the signature included in the callback request.
- If the signatures match, you can trust the authenticity of the data.
For more detailed instructions on how to compute and validate signatures, refer to the Guides: Additional security article. The article provides comprehensive information on signature computation, validation, and other security measures you can implement.
Notification delivery times
Upon reaching a final status (either successful or erroneous), the IXOPAY platform promptly sends a notification to the callback URL specified in the transaction request. However, delivery times for these notifications may vary depending on the payment method used. In some cases, the notification may be instantaneous, while in others, it may take several days.
Processing callback data
The callback data received from the IXOPAY platform contains important information about the transaction's status and other relevant details. Ensure that your system processes this data according to your business logic.
Refer to the Callback Data article for detailed information on the structure of callback data, including how to include additional data and verify its authenticity.