advancedConsistency & Transactions

You're designing a payment API that clients might retry after a timeout. How do you make sure a retried request never charges the customer twice?

Tests whether you can actually design an idempotency-key mechanism end to end, not just name the pattern.

Ready to master this question?

Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.

Next Step

Continue to You need to rate-limit an API both per-user and per-IP, at scale, across multiple instances. How do you implement it? →← Back to all Company Round Scenarios questions