Circle and Proof Demonstrate Identity Checks Alongside USDC Payments for AI Agents

Circle Internet Group (NYSE: CRCL) and identity firm Proof have demonstrated a way for AI agents to present verified identity and complete a stablecoin payment in one transaction. Shown at Money20/20 in Las Vegas last week, the flow targets a basic obstacle to agentic commerce: a merchant may receive a purchase request from software without a dependable record of which person approved it.

That gap leaves businesses weighing two unattractive options: block agent traffic or accept more uncertainty around fraud and disputed purchases. The Circle and Proof demonstration proposes a technical path between those choices. It ties a specific identity claim and purchase approval to a payment, giving the merchant evidence it can retain after the transaction.

Identity first, payment next

The flow combines two open standards that use different HTTP response codes. Proof’s x401 protocol uses the 401 “Unauthorised” response to tell an agent what identity evidence a merchant requires and which credential issuers it accepts. Published in June 2026 and moved into production last week, x401 handles the question of who the agent is acting for.

Circle’s x402 protocol uses the 402 “Payment Required” response to specify payment terms. In the demonstration, a merchant’s response to an agent request includes both an identity requirement through x401 and a request to pay in USDC through x402. The agent presents its identity proof and then settles the transaction.

Proof’s wallet supplies a verified credential based on identity proofing certified to the NIST IAL2 standard. It also carries a signed approval tied to that particular purchase. The merchant receives only the relevant identity details; the flow does not send or store a complete identity document. Payment then comes from a Circle Agent Wallet in USDC over x402.

The resulting evidence is designed to remain useful after the transaction. The merchant retains a signed, tamper-evident record showing who approved the purchase. That record could support a later dispute without requiring the merchant to contact Proof in real time. For businesses handling agent-initiated orders, keeping the approval attached to a specific transaction may help close an accountability gap that payment confirmation alone does not address.

A payment path for identity checks

The protocols also create a possible way to pay for identity checks as they are used. Proof prices identity claims individually, and the x402 channel can send a micropayment from the merchant to the identity issuer for each check. A merchant could therefore pay for a credential when a transaction requires it, without first arranging a direct commercial relationship with the issuer.

That model could make credentials easier to reuse across different services. Today, identity checks can depend on separate agreements between the business requesting a check and the organization that issued the credential. A transaction-level payment offers another route: the merchant requests an accepted claim, the issuer supplies it, and payment accompanies the request.

The commercial case will depend on more than the protocol design. Merchants need confidence that the credential is meaningful, that the approval is genuinely tied to the purchase, and that the evidence will fit their dispute processes. Identity providers, wallet operators and payment services also need compatible systems. If any part of the chain is difficult to integrate, the convenience of combining verification and settlement may not be enough to overcome existing workflows.

Proof founder and chief executive Pat Kinsel 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.”

Adoption depends on trust and fit

The demonstration arrives as some large institutions at Money20/20 are understood to be blocking AI agent traffic. That choice can limit exposure to purchases whose authorization is unclear, but it may also prevent businesses from serving customers who increasingly use AI assistants. The Circle and Proof approach is one attempt to make agent requests easier to assess; other efforts include work in the W3C verifiable credentials ecosystem and proprietary authentication systems from payment networks and cloud providers.

The NIST IAL2 basis gives the credential a defined identity-proofing reference point. That may help businesses assess what the credential represents, but a standard alone does not settle whether a particular merchant should accept it for a particular transaction. Businesses will still need to judge the scope of the disclosed information, the reliability of the signed approval and the usefulness of stored evidence when a customer later challenges a purchase.

Nor does the demo establish that this protocol flow will satisfy every financial institution’s customer verification requirements. How businesses treat an identity assertion presented at the protocol layer remains a key uncertainty, especially where existing processes require a direct connection between a customer account and a payment. That question will affect whether agent purchases can move through new wallet-based flows or remain tied to familiar customer-authenticated channels.

The practical measure of success will be whether merchants can verify the person behind an agent request, preserve clear evidence of purchase approval and settle payment without adding friction that outweighs the benefit. Circle and Proof have shown how those steps might fit together; adoption will depend on acceptance of the credentials, integration across providers and how businesses handle disputes when an agent acts for a customer.