02 / A morning at Pied Piper
One double charge, from the ticket to the audit trail.
Endframe was charged twice. Here is how Pied Piper handled it, screen by screen.
- 01
The ticket lands on the customer page
“Invoice charged twice this month.” Richard opens Endframe in the back-office: invoices, subscription and tickets on one page, read live from Pied Piper’s database.

- 02
Claude Code looks into it
Through MCP, Claude Code lists Endframe’s invoices, finds PP-1062 and PP-1063 charged one second apart, and asks to refund the second one. Each call is part of the run.

- 03
The refund waits for a human
Refunds by AI agents go through the risk check. The action is held with its form values until someone with the right role approves it, with a comment.

- 04
Approved, run, recorded
Richard approves. The refund runs with his identity, and the audit log keeps every step: the AI agent’s reads, the request, the approval, the refund.

