← Go back

Guide // MandateGuard

When should you suspend, resume or revoke an agent 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

Suspend, resume and revoke are the issuer's three verbs for an intent's life. Suspend pauses the mandate reversibly — authorisations stop, every checker sees the suspended state, budgets are preserved — and is the right response to uncertainty or investigation. Resume restores it once the cause is resolved and the figures are re-read. Revoke ends the spending authority for good, after in-flight commerce settles and final events are appended; the chain remains readable for verification and audit. All three are issuer-only operations, recorded in the intent's own event chain, effective for every party at once.

What do suspend, resume and revoke each do?

Intent status management is the issuer's control over a registered intent's life. Suspend pauses the mandate: authorisations under it cannot proceed while suspended, and every checker sees the suspended state. Resume returns a suspended intent to active. Revoke ends the mandate permanently as a spending authority. All three actions are issuer operations, recorded as events in the intent's chain, and take effect for agent, merchants and issuer-side checkers simultaneously because all parties read the same state.

Three verbs for three situations

Suspend is for uncertainty: something looks wrong, a party is under investigation, a programme pauses for a season. It is reversible, immediate and legible — every party reading the intent sees suspended and knows authorisations will not proceed. Resume is for resolved uncertainty: the cause is understood, the fix is in, and the mandate's original terms are still the right terms. Revoke is for endings: the arrangement is over, the authority should not merely sleep but cease. Choosing the mildest sufficient verb is a governance habit — suspending where revocation is meant invites a stale live mandate later; revoking where suspension was meant forces a needless re-registration and breaks the continuity of the shared record.

Suspension as the shared-mandate freeze

Suspend plays the role for shared mandates that the kill-switch freeze plays for your own agents, with one difference: its audience includes outsiders. When you suspend, merchants stop honouring new mandate-backed orders against that intent and can see why in the state itself; the agent's attempts are refused and the pattern of attempts remains visible in the record. That transparency is why suspension should be prompt when a shared mandate misbehaves — counterparties are extending real value against the intent, and every hour of un-suspended anomaly spends their confidence as well as the budget. Communicate in parallel (a message to known counterparties) but never instead of suspending: the state change is the reliable signal, the message is the courtesy.

Resuming with intent

Resume is a decision, not a default. Before resuming, confirm the original diagnosis is closed: the bug fixed, the investigation cleared, the paused programme genuinely restarting. Re-read the intent's figures — spent, remaining, period position, window remaining — because time passed during suspension and the mandate you resume into may be near a period or window boundary that changes what happens next. Then resume and watch the first authorisations as you would after unfreezing an agent: the pattern should return to the pre-incident shape. If it does not, suspend again and treat the problem as deeper than diagnosed; a second suspension with better data is good operations, not indecision.

Revocation and the wind-down

A clean revocation is a small project. Let in-flight orders complete or be cancelled by agreement; append final refund or adjustment events so the spent figure tells the truth; confirm with counterparties that the mandate is ending; then revoke. The intent's chain remains readable after revocation — history is preserved even though authority ends — so auditors and counterparties can still verify receipts and reconstruct the arrangement's life. What revocation must not be is a surprise: a merchant who learns of it from a failed verification has been handed an incident. The state change is instant and universal, which makes advance notice the issuer's professional obligation.

Who may do what

Status management is issuer authority, exercised through the issuer's keys or the registry. Merchants and agents hold read-and-verify access: they can observe status the moment it changes but cannot change it. That asymmetry is the trust model working as intended — the party whose money and name stand behind the mandate controls its life, and every other party gets perfect visibility instead of partial control. Inside the issuer's organisation, restrict who holds issuer keys the way you restrict who can freeze your own agents: few people, named, with a backup, because a suspended intent at the wrong moment halts a commercial relationship, not just a process.

Status changes as relationship communication

Because all parties read the same state, an intent's status becomes a channel of the relationship's truth. A promptly suspended and clearly resumed intent builds confidence: counterparties learn the issuer watches the mandate and acts. A mandate left active through a known problem teaches the opposite lesson, and merchants price that lesson into how eagerly they honour the next intent. Treat the intent detail — gauge, chain timeline, status — as a document your counterparties genuinely read, because the good ones do. Issuers who manage status visibly find that verification stops being an adversarial check and becomes the relationship's shared dashboard.

Five actions to take now

  1. Use suspend for investigations and pauses — it is reversible and visible to all parties
  2. Use revoke only when the mandate truly ends; treat it as final
  3. Tell counterparties before a planned suspension, and immediately after an urgent one
  4. While suspended, watch for authorisation attempts — they reveal agent behaviour
  5. On resume, confirm budgets and scope are still the terms everyone expects

Worked example: pause, repair, resume, retire

A brand's intent for a sampling agent (budget 800 dollars, two merchants scoped) shows an anomaly in week three: authorisation attempts at triple the usual rate, each small. The issuer suspends the intent at 09:15; attempts continue for an hour and fail against the suspended state, leaving a clean record of the agent's persistence. Investigation finds a scheduling bug that triple-queued the sampling tasks.

The bug is fixed, the duplicated tasks purged, and the issuer resumes the intent at 14:40 the same day with 612 dollars of budget intact. Six months later the sampling programme ends: the issuer lets final deliveries settle, appends a last refund event for a returned batch, and revokes the intent. Pause, repair, resume, retire — each transition visible to both merchants in the same state, each recorded in the chain.

Frequently asked questions

Does suspension delete remaining budget?

No. Budgets are preserved through suspension; resume restores the intent exactly as it was, subject to its window.

Can a merchant suspend an intent?

No. Status management is issuer authority. Merchants who see a problem should contact the issuer — their verification evidence will focus the conversation.

What happens to purchases already made when an intent is revoked?

They stand as history in the chain; refunds and adjustments for in-flight commerce can still be recorded as the arrangement winds down. Revocation ends new spending authority.

Is revocation reversible?

Treat it as final. A mandate that must live again should be registered as a new intent, with fresh terms reviewed.

Does suspension affect the agent's other work?

Only work under that intent. The agent's policy-governed spending outside the intent is a separate matter — freeze the agent if the problem is the agent itself.

Keep reading

Put the policy in force: spend envelopes · intent registry · approval inbox · how the proof works · all MandateGuard guides