Course contentsShow
← System Design
Lesson 1002 of 1,91926. Idempotency and RetriesFree lesson

The Double-Charge Problem

Explore the classic example of duplicate payments illustrating why non-idempotent operations are risky.

The Double-Charge Problem

What You'll Learn

You'll understand the classic duplicate payment scenario that demonstrates why non-idempotent operations can cause serious real-world harm.


The Classic Nightmare Scenario

Imagine you're buying concert tickets online. You click "Purchase" for $100. The request travels to the payment service, which charges your card successfully. But just as the server tries to send back a "success" response, a network hiccup occurs—the connection drops. Your browser never receives confirmation.

What do you do? You click "Purchase" again. The same payment service receives what looks like a brand-new request and charges your card a second time. You've now paid $200 for the same ticket.

This is the double-charge problem, and it's a textbook example of why non-idempotent operations are dangerous in distributed systems.

Why It Happens

Payment processing is inherently non-idempotent if implemented naively. Each time the payment service receives a charge request, it executes the charge operation without checking if it's already been processed. Network failures, client retries, load balancer retries, and timeout-triggered re-attempts can all trigger duplicate requests.

The service doesn't know that the second request is actually a retry of the first. From its perspective, they look identical—same user, same amount, same card—but it treats them as separate transactions.

The Real-World Impact

  • Financial losses for customers
  • Chargebacks and refunds burden for the business
  • Loss of customer trust and potential legal liability
  • Operational overhead handling support tickets

Key Takeaway: The double-charge problem illustrates that non-idempotent operations like payment processing become hazardous in distributed systems with unreliable networks and automatic retries—making idempotency not optional, but essential for financial and critical operations.