Ensuring Consistency, Idempotency, and Reliable Retries in Payment Systems

1 Document Association

In payment systems, documents such as payment orders and refund orders often need to be linked, similar to relationships in order domains. Linking serves two main purposes:

Status Consistency

A refund can only be created if the original payment succeeded; when the original payment is successful, any associated refund or related payment must also be considered successful.

Amount Consistency

Refund amounts must never exceed the original payment. When supporting multiple partial refunds, the system records the cumulative refunded amount and validates that each new refund does not cause an over‑refund.

2 Idempotency

Idempotency is achieved by defining unique keys for different sides of the transaction:

Order side: use the order number together with PaymentNo to detect duplicate payments or refunds.

Payment side: combine external order number and merchant ID as a unique key; payment orders use transaction ID plus operation code as a unique key.

Idempotent handling also covers re‑entry scenarios, such as when an upstream system retries a refund request after a timeout; the payment service should return success instead of a business error.

3 Retry Mechanism

Maximum‑effort notification is a common fault‑tolerance technique in distributed payment flows. Requests that fail due to network glitches or temporary service unavailability are placed into a message queue for asynchronous retry, with intervals that increase progressively.

If the retry succeeds, the transaction callback is executed.

If it fails or remains in progress, further retries continue; therefore idempotent interfaces are essential.

For example, after receiving a payment success callback, the order service may need to lock inventory and deduct resources. If resource deduction fails, the order is closed and a refund is issued. After a configurable number of retries without reaching a final state, the order is persisted for manual handling.

Reference: Programming Selection Network (www.javaedge.cn).