{"id":4,"date":"2026-09-25T10:26:31","date_gmt":"2026-09-25T10:26:31","guid":{"rendered":"https:\/\/demos.canvaswp.com\/ai-payments\/features\/"},"modified":"2026-10-01T08:57:50","modified_gmt":"2026-10-01T08:57:50","slug":"features","status":"publish","type":"page","link":"https:\/\/demos.canvaswp.com\/ai-payments\/features\/","title":{"rendered":"Features"},"content":{"rendered":"
\n
\n
\n
\n

The card lifecycle<\/p>\n

Six steps,
all of them auditable<\/em><\/h2>\n<\/div>\n
\n

Cards are short-lived by design. Each one exists for a single job, carries a single budget and closes the moment the job is done.<\/p>\n<\/div>\n<\/div>\n

\n
\n
\n<\/i>\n<\/div>\n
Request<\/div>\n

Your agent calls the API with the job, the merchant and a budget. No card details ever live in its prompt or its memory.<\/p>\n

\n
"action"<\/span>: "card.request"<\/span>,<\/div>\n
"merchant"<\/span>: "browserless.io"<\/span>,<\/div>\n
"budget"<\/span>: $49<\/span><\/div>\n<\/div>\n<\/div>\n
\n
\n<\/i>\n<\/div>\n
Check<\/div>\n

Your policies run before anything is issued: budget caps, merchant locks, category rules and velocity limits.<\/p>\n<\/div>\n

\n
\n<\/i>\n<\/div>\n
Approve<\/div>\n

Above your threshold, a person gets the final say in Slack, email or SMS. Below it, the agent keeps working.<\/p>\n

\n
Hey human :<\/div>\n
Approve a $49.00 subscription for the research agent?<\/div>\n
\n