Transaction Limits · 5 min read · 20 October 2026

Designing spending limits that actually contain risk

Layer per-transaction caps, daily budgets, merchant allowlists and velocity checks. Limits should be enforced at the payment rail, where the agent cannot rewrite them.

Layer your limits

No single limit is enough. Combine a per-transaction cap, a daily or monthly budget, a merchant or category allowlist and a velocity check on how many payments happen in a short time.

Enforce at the rail

Limits written in the agent's instructions can be ignored or rewritten. Limits set on a virtual card, a restricted API key or a wallet policy are enforced by the payment system itself.

Start small

Give new agents tight limits and raise them only after reviewing real behaviour. A low ceiling turns a successful attack into a small, recoverable loss.

Escalate, don't fail silently

When a payment hits a limit, route it to a human for approval instead of simply blocking it. This keeps the agent useful while keeping people in control of exceptions.