Your Agent Just Authorized What?! — Jay Mok & Ben Coumes, Paypal
Key Takeaway
Agent authorization requires a contextual mental model spanning low-stakes system logs, medium-stakes OAuth shared vaults, and high-stakes verifiable intent tokens to prevent unauthorized autonomous spending.
Highlights
PayPal builds an approval token primitive for agentic payments that lets users start the order process before an item or merchant is found.
Gemini users choosing PayPal as their payment method will use the new PayPal approval token primitive in production.
Fido verifiable intents and AP2 mandates use a multi-layered selected disclosure JSON Web Token signed by the user's private key.
Payment processors verify payment mandates while merchants verify checkout correctness without requiring prior relationships.
Agent authorization frameworks divide scenarios into low stakes cloud coding, medium stakes shared vault operations, and high stakes autonomous multi-party transactions.
Timeline
Core Agent Authorization Questions
Human authorization uses methods like passkeys while scopes use time-bound tokens with amounts and merchant intent. Ecosystem openness dictates whether parties know each other beforehand. Working within a trusted office building serves as an analogy for closed ecosystem trust.
- Agent authorization relies on determining human approval, scope validity, and proof for future disputes.
- Payment context requires answers dependent on stakes and ecosystem openness.
- Workplace badge analogies describe operating within trusted trust boundaries.
Low and Medium Stakes Authorization Scenarios
Users set up GitHub and Jira connectors using human authentication while configuring tool permissions. Travel companies monetize occupancy data and reviews through buyer agents using enterprise infrastructure primitives. Vaults store payment credentials on behalf of buyer agents and provide access via OAuth.
- Cloud code integration represents a low stakes closed ecosystem relying on system logs or manual reversions.
- Shared vaults and OAuth scopes handle medium stakes commercial travel card payments within trusted partners.
- Transaction logs suffice for dispute handling in closed medium stakes environments without cryptographic proof.
High Stakes Autonomous Payments and Approval Tokens
Multi-layered selected disclosure tokens contain layers from trusted credential providers, user instructions signed with private keys, and autonomous agent signatures. PayPal approval tokens return JSON payloads with amount, expiry, and merchant details. Street interactions without prior familiarity serve as analogies for high stakes trust requirements.
- Fido verifiable intents and AP2 mandates govern high stakes transactions with unknown counterparties.
- PayPal approval tokens allow users to start order processes before agents find a specific item or merchant.
- Verifiable security models extend beyond payments to hard to reverse actions like medical orders and e-signatures.
Description
A PayPal order has always been synchronous. You find the item, you open the app, you approve it, it is done. The approval token demonstrated here inverts that: the user approves before the agent has found an item or picked a merchant, and PayPal returns a JSON payload carrying the amount, the expiry, and the merchant the agent is permitted to transact with. It was days from shipping when this was recorded. That inversion is the concrete end of a broader argument about agent authorization, built on three questions any such system has to answer. Did the human authorize this? Is it allowed right now, in this scope? And can we prove it later? The answers, the talk argues, depend entirely on how high the stakes are and on whether the two parties have ever met. The rest maps those questions onto a ladder. At the bottom is a coding agent, where consent happens once when tools are connected, permission is granted per tool as allow, ask or deny, and ordinary logs are proof enough because the actions can be reverted. In the middle is money moving between parties who already know each other through a shared vault and OAuth scopes, where a mandate carries the amount and the scope and existing transaction logs settle disputes. At the top is the case nobody has running in production yet: an agent transacting autonomously with a counterparty it has never met. The proposal there is a layered selective disclosure JWT, so a merchant can verify the checkout and a processor can verify the payment mandate without either knowing the other. Timestamps: 0:00 - Terminator, and the agent that empties your wallet 1:26 - Three questions any agent authorization has to answer 2:49 - Stakes, counterparties, and the badge analogy 4:12 - Low stakes: a coding agent with allow, ask and deny 6:15 - Medium stakes: a shared vault and OAuth scopes 9:45 - High stakes: counterparties who have never met 10:29 - A layered selective disclosure JWT 12:30 - The approval token, and inverting the order flow 14:31 - Why the ladder applies beyond payments
