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.

This is a Pro question

Sign in, then upgrade to Pro or Power to unlock this question and the full Interview Prep bank.

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?

Next Step

Continue to What is chaos engineering, and how would you apply it to actually test resilience patterns in production?← Back to all Company Round Scenarios questions