Timeouts

In payments processing, various systems for different parties are involved. When a request surpasses the expected duration, it may be attributed to a loss of connection or other network errors, but it does not necessarily indicate a processing failure.

This underscores the importance of setting a recommended read timeout of 30 seconds for all our services. It is crucial to proceed with available mechanisms to recover from this state and prevent inconsistencies.

Recovery measures

To mitigate undesirable repercussions when requests exceed the timeout, consider implementing the following actions on your end:

• Use getpaid's notification webhooks to monitor missing responses.
• Use getpaid's idempotency mechanism to securely retry the request.