Implement idempotency key lifecycle management for high-throughput Stripe payment requests including key expiry, recycling, and collision detection

Steps

1. Generate idempotency keys as UUID v4 strings tied to the logical payment attempt identity (e.g., hash of order_id + attempt_number) rather than random values
2. Store the idempotency key alongside the payment attempt record in your database before making the Stripe API call
3. On a network timeout or 5xx response, retry the exact same API call with the same idempotency key; do not generate a new key until you have confirmed the previous attempt's outcome
4. Handle the case where Stripe returns a 409 Conflict with error code idempotency_key_in_use, indicating a concurrent request with the same key is in flight; back off and retry after a short delay
5. After a successful response, do not reuse the idempotency key for a different payment even if the parameters are different; Stripe returns the cached result for 24 hours
6. After 24 hours, Stripe considers the key expired; use a new key for a retry on the following day