Why Your Payment Got Charged Twice: Idempotency Keys Explained

When you use a payment app, like Maya tapping Pay for a $20 ride, there's a risk the request can time out and be retried. This can sometimes lead to being charged twice. Stripe's solution involves using idempotency keys. An idempotent operation is one that can be performed multiple times without changing the outcome beyond the initial application.

For payments, this means if a request is retried, it should have the same effect as the first request. To achieve this, a unique string called an idempotency key is included in the request. The client creates this key, which becomes the identifier for the request. Stripe then stores the server's response to this key. If the same key is sent again, the server returns the saved response, ensuring the transaction isn't duplicated.

If a request fails in the middle and crashes, the server will remember the progress thanks to the idempotency key. This ensures the client isn't charged twice. However, this system has its challenges. For instance, if two retries occur simultaneously with the same key, one will wait while the other completes its task, preventing duplication.

To avoid hammering the system with retries, Stripe uses an exponential backoff strategy, which involves waiting longer between retries. Additionally, random delays or 'jitter' are added to the wait times to prevent all retries from occurring at the same time.

In summary, idempotency keys play a crucial role in ensuring that payment requests are safe to retry without causing double charges. This mechanism allows the server to remember the result of a request and return it on subsequent retries, ensuring consistency and reliability in the payment process.