Payment mandates for SaaS: how AI agents pay recurring bills without asking permission every time
You run a SaaS that charges API usage in USDC. An AI agent calls your endpoint every hour. The first payment goes through fine. The second time, the agent asks the human "can I pay $0.03 for another 1000 tokens?" and the human has to click approve. Day two, same question. Day three, the user stops responding and your SaaS stops getting paid.
This is the problem CAI payment mandates solve. One setup. No per-charge confirmations. The agent pays within the limits you define and the user sets.
How a payment mandate changes the flow
Without a mandate, every agent payment is a two-step conversation. The x402 prepare shows requires_user_confirm: true , the agent asks the human, the human says yes, x402 execute goes through with user_confirmed: true . That works for one-off purchases. It breaks for recurring SaaS billing.
With a mandate, the user creates a payment mandate once at cai.com/app or through the API.…