Recurring mandates
Agent Pay status: Approve does not execute. Execution: not enabled. ACH settlement: not enabled. prepare_payment never moves money. Machine-readable: /docs/agents/status.json.
A recurring mandate is a template for a repeating payment: an amount, a currency, a saved payee, and an interval in days. It is not a standing approval. Every cycle needs a fresh human approval.
Limits today
This feature is Live (limited). Mandate cycles can be drafted to a saved payee. Each mandate cycle needs a fresh human approval, valid until the cycle time plus a grace period. Claims before the cycle time are refused. Scheduled claims are not enabled, and a claim only records the claim. Money doesn't move while execution is not enabled.
In detail:
- Fresh human approval every cycle. Approving one cycle never approves the next.
- Owner only. Mandates are created and managed by the account owner in a signed-in POINTS session. No MCP tool creates or claims a mandate, and there is no mandate screen in the app yet.
- Early claims are refused. A cycle can't be claimed before its cycle time.
- A scheduled claim option exists but is not enabled. It can't be turned on from the app, and without it the owner claims each cycle in a signed-in session.
- A claim only records the claim. It returns
executed: falseand never moves money. Execution: not enabled.
One cycle, step by step
- Prepare. The owner opens the cycle for the next cycle time. It starts as
pending_approval. - Draft. A payment draft is created from the stored mandate terms, addressed to the saved payee. Nothing in the request can change the amount or payee.
- Approve. A human approves the draft as usual, and a fresh signed envelope is minted.
- Attach. The envelope is attached to the cycle. It must match the mandate terms exactly (amount, currency, payee) and pass the scope checks. The cycle becomes
approved. - Claim. At or after the cycle time, the owner claims the cycle. It becomes
claimed, and the next cycle time moves forward one interval.
Approval window
- A cycle approval stays valid until the cycle time plus a grace period. The grace period is a server setting.
- Approval opens only a limited time before that deadline, also a server setting. Earlier approvals are refused.
- Other drafts keep the ordinary 1-hour window.
What can go wrong
| Situation | Result |
|---|---|
| Claim before the cycle time | Refused as not due. Nothing is written, and the same cycle can be claimed once it is due. |
| Approval lapsed or revoked before the claim | The cycle becomes expired, and the slot can be prepared again. |
| An execution attempt was recorded for the draft | The cycle becomes refused, and the slot is used up. |
| The owner skips the cycle | The cycle becomes skipped, and the next cycle time moves forward one interval. |
| Terms don't match the mandate | Attach or claim is refused. |
Each envelope can be used for one cycle only. Mandate and cycle statuses are listed in Statuses.