Refund an eligible paid order
The domain decides whether the order and action are valid. The card adds a daily authority ceiling for this holder.
kiff.dev Cards at work · customer support
Support agents already research the case. Give one agent separate cards for refunds, credits, and plan changes so routine requests can move immediately while exceptions still reach a person.
Three jobs. Three balances. Revoke one without stopping the others.
01 · verified on production · 21 Sep 2026
The domain decides whether the order and action are valid. The card adds a daily authority ceiling for this holder.
REFUND_ORDERPaid or partially refunded orders. €5,000 starting daily ceiling, raised once by the owner to €8,000.
Three requests were authorized against the card. The caller's system can continue its refund flow without another pre-approval.
No card, a request larger than the remaining balance, and a revoked card were all refused before the caller ran the action.
The recorded result
7 decisions3 authorized · 4 blocked · 7 signed receipts
no_mandate_issued, twice mandate_limit_reached, then mandate_expiredWhat KIFF verified: the decisions and authority draws. “Authorized” does not mean “executed”; the customer's system runs the action afterwards and does not report execution back to KIFF.
The rest of the portfolio
Store Credit Card
ISSUE_STORE_CREDITExceptions still reach a person. This card gets a verified label only after its own production run.
Plan Change Card
CHANGE_PLANIts count is independent of refunds and credits. This card gets a verified label only after its own production run.
Why three cards
Each card has one holder, one domain, its own balance, revision history, and revocation. A single broad pool would couple unrelated work and hide which authority changed.
Under every card
The card narrows authority. The domain still decides whether the action, state, permissions, and parameters are valid. These six runnable proofs show that state machine; they are not card evidence.