You delegate — in plain words.
Maya tells her agent what to do, sets a budget, and keeps the right to cancel.
One signature bounds everything.
Maya signs a User Consent Mandate on her own device — scope, caps, validity — revocable instantly.
Nine checks. Then a tamper-proof trail.
Every request runs a fixed, fail-closed verify chain — each layer lights up and seals a hash-chained provenance note.
Created — and you own it.
Vee provisions the account; the service returns receipts, and Maya gets an Ownership Certificate held in reserve.
Even at services that never integrated.
No native support? The agent falls back to a lower-trust strategy (OAuth app, browser automation) — value with zero merchant integration.
Inside the cap it just works. Over it, you decide.
Caps are checked on every payment. ₹499 sails through; ₹900 bounces back for approval.
OTPs and step-ups route to you.
When a service needs a sensitive action (an OTP, a password reset), the broker routes it to Maya for explicit approval — bearer tokens alone can't pass it.
Created → active → renews → cancelled.
Every transition emits a signed receipt; cancelling returns a prorated refund — and the user can take ownership at any time.
Your account, even if the broker vanishes.
The Ownership Certificate is a direct-claim path: Maya proves ownership to the service itself — single-use, service-signed — broker not required.
Disputes & refunds, on the record.
Didn't get what was paid for? The signed provenance trail is the evidence — open a dispute, get a refund, every step recorded.
TAP, AP2, ACP — normalized into one request.
Whatever protocol an agent arrives on, one neutral verifier checks it the same way and emits one provenance record.