To prevent duplicate post transactions, we support idempotent requests. By providing a unique idempotency key in the header of your POST requests, the server can prevent duplicate requests from being processed.
This is especially useful in cases where there is network/connection failure before you receive a response from the server.
If a duplicate request is received for a transaction that has previously been processed (same payload and same idempotency key), we do not re-process the duplicate request, rather we return to you the last successful response for the request.
We recommend using a unique string like UUID as your idempotency key.