Payment Retry

Overview

What it means

A payment retry is another attempt to complete an operation that did not produce a trustworthy success result. In crypto payments, retrying a network transfer is different from retrying an API call that may already have succeeded.

How it works

Before repeating an action, the system must identify the operation and inspect its latest authoritative state. For API invoice creation, an idempotency key can prevent a duplicate invoice if the response was lost. For blockchain payouts, the service checks the transaction hash, nonce or spent outputs and whether a replacement or rebroadcast is appropriate.

Understanding the technical details

Represent retry state with original operation ID, number of attempts, last known result and next permitted action. A retry after a genuine validation error should not reuse unchanged invalid input. A retry after timeout should first query the authoritative payment status and avoid new transaction signing if the first may have executed. Use capped exponential backoff for transient API failures and route persistent uncertainty to a human exception queue.

Common failures and limitations

Network congestion is not proof of failure. Repeatedly constructing fresh transfers can send money twice, while resubmitting an expired quote can change the amount. Retries need limits, backoff, logging and escalation for uncertain outcomes.

Related concepts

Crypto Payment Status, Payment Finality Threshold, Reconciliation.

Further reading

OxaPay — Developer documentation.