Design your integration to send only the requests it needs and to retry safely.
Best practices
- Use unique references for collections and transfers.
- Do not retry a request immediately in a tight loop.
- Reuse the transaction reference to check status.
- Cache rates briefly in your interface, but request a fresh quote before confirming.
- Treat duplicate reference errors as a sign that the original request may already exist.
Safe retry pattern
- Send the request with a unique reference.
- If the network fails, check the transaction endpoint with the same reference.
- Retry only when you are sure the original request was not accepted.
- Store the final transaction status in your own system.
Last modified on July 7, 2026