Demo: tracing a double charge to its root cause
On This Lesson 3 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
trace a customer's double charge through telemetry and data to a systemic cause; prepares SRC-014-LAB1.
Draft outline details
Step by step
- Start from the complaint: two charges for order 123; pull audit rows and provider references.
- Follow the correlation ID through logs and traces to two payment calls.
- Find the cause: the first call timed out client-side but succeeded at the provider, and the retry used a new idempotency key.
- Planned mistake: blame the customer double-clicking. Fix: test the hypothesis from timestamps and traces before concluding.
- Fix by deriving the key from the order and attempt and persisting it before the call.
- Add a reconciliation rule to detect this class and a regression test; refund through the audited path.
Check your understanding
What was the root cause?
Show answer
A retry with a new idempotency key after a timeout that actually succeeded.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.