A New Protocol Layer Is Emerging in Fintech

As agents become decision-makers in transactions, identity, permissions, and payments can no longer sit inside application logic. They need to become standardized, machine-readable components of the ecosystem.

The clearest signal is that major platforms are already operationalizing parts of this stack for a world where transactions originate from agents, not humans.

Standards like Anthropic’s Model Context Protocol (MCP), Google’s Agent2Agent Protocol (A2A), and command line interfaces (CLIs) allow agents to invoke tools and coordinate across systems.

Commerce schemas such as the Agentic Commerce Protocol (ACP), developed by OpenAI and Stripe, and Google’s Universal Commerce Platform (UCP) define how agents browse, negotiate, and complete purchases programmatically. Identity frameworks like Visa’s Trusted Agent Protocol (TAP) focus on verifying who an agent represents and what it is allowed to do.

Payment infrastructure is evolving in parallel. Google’s Agent Payments Protocol (AP2) introduces machine-native payment handshakes between services. Visa Intelligence Commerce and Mastercard Agent Pay extend existing network rails into agent-driven environments. Meanwhile, Coinbase’s x402 proposal and Stripe/Tempo’s Machine Payments Protocol (MPP) explore a model where payment itself becomes the credential that unlocks services.

The acronyms may look fragmented, but the direction is clear: payments, identity, and access are converging into shared protocols for machine commerce.

When Requests Become Transactions

Today, digital commerce separates product usage from payment settlement. Systems meter activity, aggregate invoices, then charge later as a separate financial event. Agent-driven systems may move toward a different model.

One likely shift is the collapse of billing and payment into a single primitive. A request carries payment authorization. The agent requests a resource, includes proof of payment, and execution happens the moment payment is verified.

Execution and payment happen together.

Early examples already point there. x402 uses proof of payment as a credential that unlocks an API or dataset in real time. Instead of an API key, the request itself carries a payment signal. MPP follows a similar pattern: an agent requests a resource from a service, API, MCP, or HTTP endpoint, receives a payment request, authorizes it, and gains access instantly.

In this model, internet-native currencies such as stablecoins are well suited, especially for micropayments where card minimum fees can make transactions uneconomic.

That does not exclude cards. Both cards and stablecoins are likely to matter in the agent economy. One of the more notable MPP announcements was Visa’s related card-based specification extending the model to card payments as well.

Execution and payment are starting to merge.