Adapted from my LinkedIn writing and related technical material. Read original on LinkedIn ↗

A provider request times out. The application retries with another partner. Later, both partners report success. A missing response has become a duplicate payout and a financial exception.

Unknown is a real state

A timeout does not prove that money did not move. Keep the outcome unresolved until provider checks and reconciliation establish the evidence.

Keep attempts under one payment

Track every provider request, reference, result, and retry decision against the original business payment. Idempotency at one provider is not a shared guarantee across a second provider.

Distinguish a request that was never submitted, a confirmed failure that cannot later complete, and an outcome that remains uncertain.

Give the case an owner

Engineering protects execution. Treasury checks liquidity and exposure. Operations manages the case and customer updates. Finance reconciles the evidence. Those responsibilities should use one shared history.

Before a corridor launch, simulate a successful payout with a lost response, duplicate callbacks, and late updates. Prove that a second payment remains blocked until it is safe.

Continue exploring

More from the blog.

All articles