Timeouts

Payment processing involves many systems, when a request takes longer than expected, it could be due to loss of connection or other network errors, and does not necessarily mean that the processing has failed.

That is why we strongly recommend setting a read timeout of 30 seconds for all our services, and continuing with the available mechanisms to recover from this state and avoid inconsistencies.

Recovery actions

To avoid unwanted side effects when your requests have exceeded the timeout, you can take the following actions on your end:

• By using asynchronous server-to-server notification webhooks, keep track of missing responses.
• By using the idempotency mechanism, safely retry the same payment call to the API or determine the status of the operation using the endpoint to get the response by idempotency key.