Web Development
Bug Report
Same idempotency key, different payment amount: our API returned the old charge as success
A partner reused one idempotency key for two different charges. Our API matched the key, replayed the first response and reported success for a payment that never happened. We now store a fingerprint of the request, reject mismatches with 422 and scope keys properly.