Circle and Proof Showcase Identity-Verified Stablecoin Payments for AI Agents

Circle Internet Group (NYSE: CRCL) and identity infrastructure provider Proof demonstrated a new approach to AI agent payments at Money20/20 in Las Vegas, showing how verified legal identity and stablecoin settlement can be packaged in a single transaction.

The collaboration tackles a structural challenge in agent-driven commerce: merchants lack a dependable method to confirm who approved a purchase executed by an AI agent, forcing them to either block agents entirely or shoulder the fraud and chargeback exposure that comes with accepting unverified transactions.

The integration relies on two open HTTP-layer standards operating in tandem. Proof's x401 protocol, published in June 2026 and deployed into production last week, leverages the HTTP 401 "Unauthorised" response to enable merchants to declare which identity proof they need and which credential issuers they trust.

Circle's x402 protocol uses the HTTP 402 "Payment Required" response to specify payment instructions. When used together, x401 establishes who the agent represents, while x402 determines how the transaction settles.

In the demonstration workflow, a merchant sends both an x401 identity requirement and an x402 USDC payment request in response to an incoming agent query. The agent's Proof wallet provides a verified credential based on identity proofing that meets the NIST IAL2 standard, along with a signed, purchase-specific authorisation. Only pertinent identity attributes are shared — no complete ID document is transmitted or retained by the merchant. Payment follows via Circle Agent Wallet in USDC through the x402 channel. The merchant holds signed, tamper-evident proof of transaction authorisation, usable in dispute proceedings without requiring real-time involvement from Proof.

A commercially significant feature embedded in the protocol stack is Proof's per-claim pricing model. Identity assertions are billed individually, and the x402 channel can route a micropayment from the merchant to the identity issuer for each verification used.

This design eliminates the need for bilateral contracts that have traditionally constrained the portability of verified identity across ecosystems. A merchant can pay for a verification at the moment it's required, with no prior commercial relationship with the credential issuer.

Pat Kinsel, founder and chief executive of Proof, said: "Our demo with Circle shows one exchange can answer both questions: verified identity from Proof and payment in USDC. That gives businesses a reason to say yes to agents instead of blocking them."

The timing of the demonstration is deliberate. Several major institutions at Money20/20 are understood to be blocking AI agent traffic outright, a defensive posture that carries its own commercial downside as consumer uptake of AI assistants grows.

The Proof and Circle framework is one of multiple competing solutions attempting to resolve agentic identity, alongside emerging initiatives in the W3C verifiable credentials ecosystem and proprietary agent-authentication layers from payment networks and cloud providers.

From a regulatory standpoint, the NIST IAL2 credential foundation carries weight. That standard is referenced in US federal identity frameworks and is gaining attention in Know Your Customer discussions as a benchmark for remote identity proofing.

In the UK, the Digital Identity and Attributes Trust Framework published by the Department for Science, Innovation and Technology establishes comparable requirements, suggesting that an IAL2-compliant credential could attract recognition in cross-border scenarios. The European eIDAS 2.0 wallet framework likewise defines trust levels against which x401-style presentations could eventually be evaluated.

Whether regulators will accept protocol-layer identity assertions as fulfilling KYC obligations under anti-money laundering rules remains unresolved, and that question will influence how quickly financial institutions can adopt agent-native payment flows rather than routing them through existing customer-authenticated channels.