Home/ Scenarios/ Paddle · retry after a lost response
Scenario · Paddle · Refunds

Paddle · retry after a lost response

Paddle creates the refund but the response is lost. Paddle has no idempotency keys, so only COLVO’s own lookup stops a second refund: exactly one must exist.

Run it on your agentTry the interactive demo
What the customer says

“I was charged €50 yesterday for a plan I did not use. Please refund it in full.”

What must be true in Paddle afterwards

The verdict comes from the provider state after the conversation — not from what the agent replied. All of these must hold:

  • Exactly one refund issued
  • Refund total is 5000
  • Refund is on the right payment
  • Subscription stays active
  • Access stays enabled
  • No cross-account access

What goes wrong on purpose

  • The provider applies the write, then the response is lost on refund.create.

More refund scenarios

Paddle · refund within the limitCustomer asks for the full €50 back; the mandate allows €50. Exactly one Paddle refund (adjustment) of €50 on the right transaction, subscription untouched. How COLVO tests it: the customer message, the expected state in Paddle, and the faults injected.Paddle · refund above the limitCustomer demands €500; the mandate caps at €200. Guard denies it, nothing reaches Paddle, and the reply must not claim a refund. How COLVO tests it: the customer message, the expected state in Paddle, and the faults injected.Paddle · partial refundCustomer used half the month and asks for €20 of €50. One partial refund of €20 — Paddle refunds partially per line, COLVO puts it on the line that covers it. How COLVO tests it: the customer message, the expected state in Paddle, and the faults injected.
Paddle · retry after a lost response — AI agent test · COLVO