Payment Context Policy Conditions
Use an agent's own authorization history to add human review requirements.
Payment context lets a signed policy use an agent's own authorization history for the same payee. RobotMoney builds this history from recorded authorization decisions. It does not require a connected bank, accounting, invoice, ERP, or other external source.
Availability
Payment context on recorded authorization decisions
Live
Opt-in payment context policy conditions
Live
Internal USDC execution after an approved decision
Sandbox on Base Sepolia
Context conditions in the default Console policy presets
Planned
The conditions on this page affect the decision gate only. They do not make a payment rail production-ready.
What The Context Contains
Before each recorded decision, RobotMoney loads up to 100 prior authorization rows for the current tenant, agent, and payee from the preceding 90 days. The snapshot includes decision counts, recent amount statistics, review counts, execution counts, the last policy used, and the first and last decision times. The current request is not included in its own snapshot.
Each authorization stores the snapshot that existed before its decision. Policy evaluation receives a separate read-only projection and cannot change the stored snapshot.
Context Conditions
Context conditions are escalation-only. A matching rule must use execute: confirm, which adds human review. A context condition can never allow or reject a payment. Policies without these keys keep their existing behavior.
First-time payee
when:
context.payee.is_first: true
execute: confirmThis matches when the agent has no prior decision for the payee.
Amount above the recent average
This matches when the proposed amount is strictly greater than the payee's recent average multiplied by the positive decimal factor. The amounts must use the same currency.
Repeated blocked attempts
This matches when the prior blocked-decision count reaches the positive integer threshold.
Prior human rejection
This counts human review rejections. It does not count decisions blocked by policy as human rejections.
New-payee count per UTC day
This matches only for a first-time payee when the agent's historical count has reached the configured cap. The count uses distinct payees whose first decision for this agent occurred in the current UTC day. Because the current request is not counted yet, a cap of five sends the sixth new payee to review.
Missing Context
A missing, null, or malformed snapshot is treated as a first decision. context.payee.is_first is true, while history-dependent counts, amount statistics, and the daily new-payee count are null. A first-time-payee rule therefore matches, but the other context rules do not.
If the snapshot currency differs from the current request, RobotMoney keeps currency-independent history and treats only the recent amount statistics as unavailable.
Opt In Per Policy
These keys do not change existing policies or Console presets. Add a context condition to a signed policy rule when that history should require review. The policy validator refuses auto and reject on rules that use a context key.
For the authorization response fields, see the Authorizations API.
Last updated
