Notes on engineering, billing & payments

A payment retry silently double-charges a customer, and the standard fix — an idempotency key — only works if you're precise about when it's minted and who owns it. This walks a charge flow from a naive retry through a client-owned key, a durable request-status table, and a reconciliation job that closes the gap when a worker dies mid-flight.