Refunds
Let support staff or customers return money with the exact amount, destination, timing and consequences stated before it's irreversible.
8 states7 edge casesDesktop + Mobile
01The problem
Refunds move real money and can't be taken back. Support agents need to refund quickly, but a wrong amount, a duplicate refund or an unexpected loss of access creates a second support problem. Customers need to know when the money arrives, because “refunded” in your product isn't money in their account for days.
02When to use
Use when
- Support tools where staff issue full or partial refunds
- Self-serve refund requests within a refund policy window
- Order or invoice detail pages for one-time purchases
- Subscription cancellations that include a refund of unused time
Avoid when
- The customer wants credit for a future purchase, not money back — use account credit, which is reversible.
- The payment is disputed. The card network now owns the process; a refund can double-pay the customer.
- The refund requires approval above a threshold. Combine with an approval workflow first.
03Recommended UX
Statecraft recommendation
Make the refund a dedicated step with the amount pre-filled to the maximum refundable value, an editable partial amount, a required reason, and a confirmation that names the exact amount, the destination card and what happens to access.
04Desktop behaviour
On desktop the refund opens as a side panel over the payment, so the agent can see the original charge, previous refunds and the customer's history while deciding.
Desktop rules
- Show paid, refunded so far, and refundable remaining as three separate numbers above the amount field.
- Offer quick choices — Full remaining, Last invoice, Custom amount — instead of only a free text field.
- Put the amount in the confirm button: “Refund $49.00”.
- List refunds under the payment as their own rows with status and who issued them.
05Mobile behaviour
Customer-facing refunds on mobile are usually requests, not instant refunds. Keep the flow short and set expectations about timing.
Mobile rules
4 mobile rules are included in Pro.
Statecraft Pro
Unlock the full pattern
Get the complete interaction flow, states, edge cases, mobile rules and implementation prompt.
- Interaction flow · 6 steps
- 4 mobile rules
- 8 states
- 7 edge cases with recommendations
- 5 microcopy comparisons
- Accessibility notes
- Developer notes
- Claude Code / Codex implementation prompt
Edge cases covered in this pattern
- Double submission
- Refunding more than remains
- Refund on a disputed payment
- Access after refund
- Card no longer valid
- Currency and fees
- Customer asks “where is my money?”