Sign InOpen Brain
AI EngineerVideoSource Linked

Your Agent Just Authorized What?! — Jay Mok & Ben Coumes, Paypal

Agent authorization should scale with stakes and reversibility: logs may cover coding changes, while open-ended payments need scoped, time-bound, independently verifiable mandates.

AI Engineer · Sep 1, 2026
Open Source Open MarkdownOpen JSON
Source Summary

PayPal frames authorization around **three questions**: did the human approve, is the action currently within scope, and can that approval be proven later. Its approval token can be issued before product selection and carries constraints including **amount, expiry, and merchant**.

Practical Implication

Match controls to consequences. Reversible coding work may rely on permissions and logs; payments inside a vetted network can use scoped credentials; irreversible actions across unknown parties need signed intent that merchants and processors can verify independently.

Agent-Ready Context
PayPal frames authorization around **three questions**: did the human approve, is the action currently within scope, and can that approval be proven later. Its approval token can be issued before product selection and carries constraints including **amount, expiry, and merchant**.

Match controls to consequences. Reversible coding work may rely on permissions and logs; payments inside a vetted network can use scoped credentials; irreversible actions across unknown parties need signed intent that merchants and processors can verify independently.

The highest-stakes open-ecosystem model was **not yet observed in production**. PayPal's near-term token is an opaque value only PayPal can validate, while interoperable FIDO verifiable intents and AP2 mandates remain the proposed direction.
Connected Context · Feed7 Judgment

PayPal sharpens general harness guidance into an authorization test for consequential actions: approval must be attributable to a human, valid for the current action, and provable afterward. Amount, merchant, and expiry constraints make that test concrete for payments and show why logs alone are insufficient across unknown parties. The distinction between PayPal’s closed-network token and proposed interoperable mandates also narrows current deployment claims.

From coding to Knowledge work agents — Karan Vaidya, ComposioComposio’s preflight checks and enforced permissions are the general harness layer that PayPal specializes into consequence-sensitive, independently verifiable payment authority.Teaching agents to pay — Anna Spysz, StripeStripe’s provider-enforced limits, cancellation, and disclosure complement PayPal’s proof of human authorization by governing transaction execution after intent is granted.AI Agents Are Just Distributed Systems Now — Salman Munaf, TikTokDistributed-systems ambiguity after timeouts means a valid mandate still needs idempotency, status reconciliation, and recovery to prevent uncertain or duplicated external effects.In Code They Act, In Proof We Trust — Erik Meijer, Leibniz LabsMachine-checkable proofs before side effects are a stricter proposed gating mechanism; PayPal instead focuses on portable evidence that a human authorized a bounded commercial action.
Context Map
agentcodingsecurity#tool-use#harness-engineering#agent-reliability
Uncertainty
The highest-stakes open-ecosystem model was **not yet observed in production**. PayPal's near-term token is an opaque value only PayPal can validate, while interoperable FIDO verifiable intents and AP2 mandates remain the proposed direction.