Who may refund what—before macros invent policy.
If a support macro can say "we'll refund that," it's already making policy. Decide who can approve which amounts and reasons, and what the payment record has to show, before anyone promises money back.
Before a macro or an agent talks about money back, decide who may approve which refund amount and reason, what the payment record must already show, and which phrases stay off-limits until a named person decides. Writing that down as a simple authority ladder keeps sympathy from quietly turning into policy.
Sympathy is not a refund policy
A customer is upset. The agent—or the macro the agent fires—wants to make it right. The sentence names money. The payment record does not show a refund. Finance hears about it from the customer, or from a chargeback, or from a screenshot in a thread that has no owner.
Refunds are not a tone problem. They are an authority problem. Someone may approve a range for a reason against a record state. Everyone else may quote what the record already shows, or escalate. When that ladder is missing, macros invent policy one kind paragraph at a time.
This note is the TWIMCO Refund Authority Ladder: one page that ranks who may do what with money-back decisions before templates, chatbots, or agents are allowed to speak. There is no live ladder tool. Copy the rungs. Fill them with support, finance, and the people who reverse payments.
Commerce teams often treat refunds as a support detail and checkout as the product. The product includes who may move money after the sale. If that is the work you are scoping, start with ecommerce.
On marketplace work shaped like Paddle8, the public lesson is that the winning bid was only the beginning: the platform had to carry obligation into fulfillment knowledge, not stop at the exciting transaction. This note does not claim Paddle8's refund macros or approval practice—those are not on the public case. The case is the standard that post-sale money and movement need named authority before anyone speaks them as commitments.
What the ladder forces you to name
Fill one ladder for the refund paths you actually run. Full refunds, partials, store credit, and chargeback responses are different rungs when different people may approve them.
Refund type. Full, partial, item-level, shipping-only, goodwill credit. Split rows when authority differs.
Reason codes. Damaged, not received, changed mind, duplicate charge, fraud review. A ladder with one "other" bucket is how sympathy becomes unlimited.
Amount bands. Write currency bands your roles already use, or "any amount" for a role that truly has it. Do not invent a percentile of order value as if it were measured policy. Write the rule you will stand behind in a dispute.
Preconditions in the ledger. What must already be true: capture state, settlement state, return received, inspection complete. A macro may confirm a refund only when the record shows the state you named—including submitted versus settled if those differ.
Role per band. Who may approve, who may execute, who may reverse an erroneous refund. Approval and execution can differ. "Support" without a band is not a role line.
Macro / agent permission. May state only, may request, may approve within band, or forbidden. Most templates should be may state or may request. Approval inside a template needs the same preconditions as a human in that band.
Forbidden phrases. Sentences that approve money, invent timing ("back on your card today"), or widen amount without a field. Ban them on the ladder so they are not pasted back next quarter.
Evidence on the decision. What must be attached: order id, payment id, photo policy pointer, prior approval id. A refund without a trail is a future argument.
That field set is the TWIMCO Refund Authority Ladder. Another studio can say "empower support." They do not have your bands, your ledger preconditions, or your forbidden list.
How the work moves
Bind refund speech to a rung
- Name the refund type
Full, partial, credit, or shipping-only—split when authority differs.
- Set amount bands
Currency limits per role; no invented percentile theater.
- Require ledger state
Preconditions the payment record must already show.
- Assign roles
Who may request, approve, execute, or reverse.
- Bind macros
Quote, request, approve-in-band, or forbidden—plus banned phrases.
A refund macro without an authority ladder is a policy written in sympathy.
Climb authority on purpose
Treat the ladder as ordered trust, not as a suggestion box.
Rung A — Quote only. Anyone with ticket access may repeat a refund already present on the payment record, including the state labels you use. They may not add timing the processor has not provided.
Rung B — Request. Frontline may open a refund request in the system with reason code and evidence checklist. They do not move money.
Rung C — Approve within band. Named roles approve inside amount and reason limits when preconditions are met. Outside the band, escalate—do not "just this once" in chat.
Rung D — Approve unrestricted or reverse. Finance or an equivalent role for amounts, reasons, or reversals outside normal bands. Write who covers after-hours if commerce does not sleep.
Advance / exception rule. Temporary widenings get an expiry and an owner. Permanent widenings edit the ladder and re-train macros the same week. A Slack exception that outlives the thread is how the ladder dies.
Agents and chatbots get the same rungs as macros. Fluency does not add authority. If the model can sound like finance, it still gets Rung A or B until the record and the role say otherwise.
Walk one real ticket type up the ladder before you ship a refund macro. If the happy path requires Rung C but the macro speaks like Rung A while executing like Rung C, you have already invented policy.
How refunds escape the ladder
Composites—not client refund rates and not Paddle8 ticket data.
The sympathy confirm. The agent says the refund is on the way. The record shows a request or nothing. The ladder would have forced "request submitted" language or silence.
The band blind spot. Partials are treated like fulls because the template has one button. Amount bands were never split.
The processor timing myth. "You'll see it in 3–5 days" as company voice when the processor's timeline was never a field. Forbidden phrases exist for this.
The chatbot goodwill. An agent grants store credit because the prompt said to delight. Delight spent money nobody authorized.
The reverse without a role. Two people refund; one reverses; nobody owns the mismatch. Rung D was empty.
When you see these, do not add a softer macro. Close the ladder: type, reason, band, precondition, role, macro permission, forbidden phrases. The unreproducible asset is your filled TWIMCO Refund Authority Ladder—your bands, your ledger checks, your escalate roles, and the sentences you removed from the library. A returns policy PDF does not name who may speak. Your ladder does.
Use it beside the returns policy, not instead of one. Policy says what the company may do. The ladder says who may decide and what a template may say before that decision. Collapsing them is how a saved reply becomes an unauthorized offer.
Decision guide
Sympathy versus authority
| Consideration | Sounds helpful | Ladder is filled |
|---|---|---|
| Confirming money | Agent says it is on the way. | Only when the payment record shows the state. |
| Amount | Whatever calms the thread. | Band and reason code with a named approver. |
| Timing language | "Today" or "a few days." | Processor fields only, or no timing sentence. |
| Bot or macro | Delight prompt spends money. | Same rung limits as a human in that seat. |
Put this into practice
- List the refund paths agents already promise: full, partial, credit, shipping-only.
- Fill the TWIMCO Refund Authority Ladder for each: reasons, bands, ledger preconditions, roles, macro permissions, forbidden phrases.
- Rewrite or delete templates that approve money or invent processor timing. Keep quote-only language bound to fields.
- Name owners for Rung C and Rung D, including after-hours coverage if you take money around the clock.
- If the gap is post-sale money and obligation inside the commerce system—not another tone guide—bring the ladder into a scoping conversation for ecommerce. Ground the standard in Paddle8 only as far as the public case goes: after the sale, authority and operational knowledge have to live in the product, not in an improvised sentence.
A kind refund promise without a rung is not service. It is an offer with no owner.
We build alongside the people doing the work.
Bring us the problem you’re thinking about.