Guide // MandateGuard
How do refunds, adjustments and chargeback events work on an intent?
By the Ingenious AI team · Published 2026-11-14 · Reviewed 2026-11-14
▸ Run the free live demo See pricing
Free covers 1 agent and 1 policy with the full authorize flow, signed receipts and the approval inbox — no card required to start.
Short answer
Refunds, adjustments and chargeback notes are appended to an intent as events in its own hash-chained log, keeping the shared budget truthful after purchase. A refund event restores budget when money comes back; an adjustment corrects a recorded amount with a factual note; a chargeback_note records that a dispute exists while its outcome is pending. Only issuer-side authority can append events; merchants verify the results with read-only keys. Append events the week the underlying fact is confirmed — in a shared mandate, a stale budget is not just your error, it is every party's planning error.
What is an intent event?
Intent events are post-transaction records appended to an intent's own hash-chained log: refund (money returned, budget restored), adjustment (a correction to the recorded spend, with effect on the budget) and chargeback_note (a recorded note about a dispute, preserving context). Events are appended by authorised issuers through the API or MCP tools; each event extends the intent chain and updates the intent's spent and remaining figures for every party reading them.
Why purchases are only half the ledger
A mandate system that records only purchases will drift from the truth at the speed of commerce. Goods come back. Prices get corrected. Charges get disputed. If none of that is recorded against the intent, its spent figure becomes a ceiling the agent hits while holding unspent real money, and every party's copy of the budget quietly diverges from reality — and from each other. Intent events exist to keep the shared record shared: the same mechanism that logs authorisations also logs their corrections, in the same chain, with the same visibility. The intent's budget then means what it says at any moment a party reads it.
The three event kinds
A refund event records money returned to the buyer and restores that amount to the intent's available budget — the natural companion of a returned order. An adjustment event records a correction: a price fixed after the fact, a partial credit, an amount that should have been recorded differently, with the budget adjusted by the amount involved; its note should say plainly what was corrected and why. A chargeback_note records that a dispute exists, with its reference; it is deliberately a note rather than a budget movement, because a chargeback's outcome is not known at filing time — when it resolves, a refund or adjustment event records the financial truth. The three kinds cover the realistic post-transaction vocabulary without pretending disputes resolve instantly.
Chained, like everything else
Events are appended to the intent's hash-chained event log, in sequence, alongside the authorisation events that receipts created. Chaining gives the corrections the same tamper-evidence as the purchases: a refund cannot be quietly inserted last month to manufacture budget, because the chain's links would break for every later reader. It also gives the log a narrative order that all parties can follow — authorisation, delivery problem, refund, adjustment — which is the order disputes and audits actually think in. The intent detail view renders this as a chain timeline next to the budget gauge, so the numbers and their story are never separated.
Operational hygiene: append promptly, note factually
Events are a shared record, so hygiene is a courtesy with consequences. Append the event when the underlying fact is confirmed — the refund processed, the credit issued — not in a monthly batch; until you do, counterparties plan against a spent figure that is wrong in the direction that blocks the agent's legitimate work. Write notes for a stranger: returned under RMA reference, price corrected per invoice, dispute filed with reference. Avoid blame and speculation in notes; the chain is evidence, and evidence reads best when it is boring. Finally, glance at the gauge after appending: the budget effect you expected should be the budget effect displayed, and catching a sign error the same day is far cheaper than at quarter end.
Events and the parties' decisions
Maintained events change behaviour for the better across the relationship. Agents stop being blocked by phantom spend, so operators stop pressuring issuers for budget raises the numbers do not justify. Merchants verifying receipts see a mandate whose custodians keep it current, which is its own form of creditworthiness. Issuers reviewing a renewal read net spend — the real economic footprint of the mandate — instead of gross authorisations. And when a genuine dispute arrives, the chargeback note with its reference means the first conversation starts from shared facts. None of this requires new machinery; it requires the discipline of recording reality in the place everyone already reads.
Events among MandateGuard's other records
It helps to keep the record types distinct. Workspace receipts record policy decisions on spends, including intent-linked authorisations. Intent events record the mandate's own lifecycle and corrections in its separate chain. Spend envelopes have their own mandate records for single tasks. The intent event log is therefore not a duplicate of the receipt chain but its cross-party counterpart: the receipts prove what the policy engine decided; the intent chain proves what the shared mandate has lived through. Auditors of a shared arrangement will want both, and MandateGuard's design keeps them joinable through the receipt linkage on intent authorisations.
Five actions to take now
- Append a refund event the week the refund is confirmed, not at quarter end
- Use adjustment events for price corrections with a note naming the reason
- Record chargeback notes even though they are informational — future readers need them
- Re-check the intent gauge after each event to confirm the budget effect
- Keep event notes factual and brief; the chain is a shared record
Worked example: a quarter of reality, appended
An intent with a 1,500-dollar cumulative budget shows 1,180 dollars spent after a quarter's purchases. Then reality arrives in three parts. A 140-dollar order is returned: the refund event restores it, spent drops to 1,040 dollars. A merchant corrects a mis-billed item by 25 dollars: the adjustment event brings spent to 1,015 dollars. A cardholder disputes a 60-dollar charge: the chargeback_note records the dispute's existence and reference while the amount's resolution is pending.
At the quarter review, the issuer, the agent's operator and the merchant all read the same figures — 1,015 dollars net spent, 485 dollars remaining, with every movement explained in the chain. Nobody reconciles three spreadsheets, because the intent's own log was maintained as events happened.
Frequently asked questions
Who can append events?
Issuer-side authority through the API or MCP intent.event tool. Merchant keys cannot write events — their role is read and verify.
Does a refund event move money?
No. It records a refund that happened on your payment rails and restores the intent's budget accordingly. MandateGuard tracks mandate state; it does not move money.
Are events editable later?
No — the intent log is hash-chained. A mistake is corrected by a further adjustment event, preserving the history of the correction itself.
What note should an event carry?
A brief factual note: what happened and a reference (return ID, dispute reference) that joins the event to your other records.
Do events affect the workspace receipt chain too?
Intent events live in the intent's own chain; authorisations under the intent also produce workspace receipts linked into that log.
Keep reading
- How do cumulative budgets work on an agent intent?
- What is an interoperable intent service for agent mandates?
- When should you suspend, resume or revoke an agent intent?
Put the policy in force: spend envelopes · intent registry · approval inbox · how the proof works · all MandateGuard guides