An agent that fills out a form or monitors a price can operate in a gray area for a while. Nobody asks for its credentials. But the moment an agent tries to spend money on someone's behalf, a whole chain of participants needs to know it's there.
That's the logic behind Mastercard's Agent Pay, announced in April 2025: agents must be registered and verified before transacting, consumers define what an agent can purchase, and the payment network distinguishes agent-facilitated transactions from ordinary ones. On the deployment side, OpenAI's Instant Checkout launched in September 2025 with scoped payment tokens constrained by amount, merchant, and session.
These are early program signals, not evidence of routine adoption. But the trajectory tells you something about where ambiguity gets resolved first. Payment systems already handle authorization, fraud screening, and disputes. U.S. billing-error rules can require documentary evidence tying a charge to the person who authorized it. When an agent enters that flow, "it clicked buy" isn't sufficient. The system needs to know who delegated, under what constraints, and whether the result matched the intent.
Other web workflows can tolerate ambiguity for longer. Money has always been less patient.
Reach: Agent surfaces a product and initiates checkout inside a conversational interface, no browser navigation required
Authority: Delegated payment tokens are constrained by amount, merchant, session scope, and expiration time
Recognition: Mastercard's program requires agents to be registered and verified; transactions are flagged as agent-facilitated for all payment-chain participants
Record: Dispute resolution can demand documentary evidence within 60 days. Checkout confirmation, token constraints, and transaction context matter after the purchase
Scope of current launches: OpenAI's Instant Checkout began with U.S. Etsy sellers, single-item purchases, and explicit user confirmation. Mastercard's Agent Pay is a program framework, not a deployed merchant count. The Agentic Commerce Protocol spec maintained by OpenAI and Stripe remains in beta as of April 2026