Circle and Proof Test ID-Verified Stablecoin Pay for AI Agents

Circle and Proof AI agent payments pair a verified ID with USDC. See who is accountable without chargebacks and what to ask before you accept them.

Adrian ReyesSenior Payments & Fintech Editor

October 31, 2026 · 8 min read

Silhouettes of two businessmen holding briefcases and shaking hands in a doorway against a hazy city skyline

Photo: Pixabay

On this page 5 sections

The Demo: How Circle and Proof AI Agent Payments Work
Why USDC AI Agent Payments Need Identity Attached
No Chargebacks: How Disputes and Refunds Work on Stablecoin Rails
How Know Your Agent on Stablecoins Differs From Card-Network Agent Programs
What Online Sellers Should Ask Before Accepting Agent-Initiated Crypto Payments

Key takeaways

Before paying in USDC, the agent shows the merchant a verified identity and a signed approval for that exact purchase. The demo ran at Money20/20 and is not a live checkout product yet.
A USDC payment can't be charged back. The only refund is one the merchant chooses to send, so your written refund policy becomes your dispute system.
The signed approval is strong evidence against "I never authorized this." It does nothing to settle "my agent got it wrong."
Each identity check costs money, so it pays off on larger and regulated sales and makes little sense on micropayments.

Circle and Proof spent Money20/20 in Las Vegas showing how an AI shopping agent can prove which verified person sent it and then pay in USDC, the dollar-backed stablecoin Circle issues. The Fintech Times covered the Circle and Proof AI agent payments demo on Oct. 28, 2026, after the companies announced the collaboration on Oct. 19. In their flow, the merchant gets two things before it ships: a verified identity with a signed approval for that exact order, and a payment that settles onchain. What the merchant does not get is a chargeback system, so on stablecoin rails the merchant ends up holding most of the accountability for an agent's purchase.

None of this is a checkout button you can turn on today; Circle calls it exploration. It is still the clearest picture yet of verified-identity stablecoin payments, and of "know your agent" outside the card networks.

The Demo: How Circle and Proof AI Agent Payments Work

The demo pairs two open protocols, and each one reuses an old web status code. x401, which Proof published in June 2026, builds on the HTTP 401 "Unauthorized" response so a site can tell an agent what proof of identity it needs. x402, which Circle supports across its agent products, uses the HTTP 402 "Payment Required" response so a site can tell the agent what payment it needs. CryptoBriefing reports that x401's contributors include Visa, Circle and Okta.

According to the Oct. 19 press release, the purchase runs in four steps:

The agent asks to buy. The merchant answers with an x401 identity requirement and an x402 payment request in USDC.
The agent's Proof wallet presents the person's verified credential, disclosing only the facts the merchant asked for, plus a signed approval for that specific purchase.
The merchant checks the signature against Proof's published public keys. It does not call Proof or store the person's personal information.
The agent pays in USDC over x402 from a Circle Agent Wallet, and the order completes.

The credential rests on identity proofing certified by Kantara at NIST IAL2, a federal standard for strong identity verification, and is tied to a hardware-protected key. Circle added Agent Wallets to its Agent Stack toolkit on May 11, 2026; the wallet's owner sets spending caps, and Circle checks every payment against them.

The pitch targets a real problem: The Fintech Times reported that several large institutions at the conference were blocking AI agent traffic entirely. Proof CEO Pat Kinsel said the demo gives businesses "a reason to say yes to agents instead of blocking them."

Why USDC AI Agent Payments Need Identity Attached

A card payment carries identity by default, because the issuing bank verified the cardholder and approves every authorization. A USDC transfer carries a wallet address and an amount. Nothing in it tells the merchant who sent the agent or whether that person agreed to this order. Without that, the joint release says, the only safe choices are to block agents or let them through blind.

"Know your agent" is the industry's name for closing that gap. In the Circle and Proof version, a verified human is bound to the agent, and the human's approval is bound to one purchase. That gives a merchant three things it can't get from a bare stablecoin payment. It knows a real, identity-proofed person stands behind the order. It holds a signed record of what that person approved. And because disclosure is selective, it can ask only for the facts it needs instead of collecting a full identity file it then has to protect.

A credential doesn't replace the merchant's own obligations. Rules for age-restricted or state-regulated products still apply, and so does sanctions screening; our guide to OFAC sanctions screening for online sellers covers what to check, and wallet addresses belong on that list. This is general information, so confirm your obligations with a qualified attorney.

No Chargebacks: How Disputes and Refunds Work on Stablecoin Rails

On a card, a customer who disputes a charge goes to their issuing bank, and the network's dispute rules decide the case. If the merchant loses, its processor debits the sale amount, usually plus a dispute fee the processor sets. The customer doesn't need the merchant's agreement to file, and for fraud claims doesn't have to contact the merchant at all.

A USDC transfer has no issuer in the middle with the power to pull funds back. Once the payment settles, it's final. A refund is a new payment the merchant chooses to send to the buyer's wallet. So the merchant is now the whole dispute desk, deciding whether a complaint is valid, what it owes, and whether to pay. That changes which kind of agentic commerce fraud a seller worries about: stolen-card chargebacks fade, and refund requests it alone must judge take their place.

That is where the signed approval matters. CryptoBriefing notes that a merchant in this flow holds cryptographic proof of what was agreed and paid. It won't stop a complaint, but it changes the conversation. "I never authorized this" is hard to argue against a signature tied to a verified person's hardware-protected key. "My agent misunderstood me" is a different claim, and no credential settles it. If a person's device and key are compromised, a valid signature can also sit on an order that person never meant to place.

Worked Example: One Contested Agent Order, Three Ways

Here is an illustrative case, not real data. A software seller offers a plan at $100 a month or $1,200 a year. A customer's agent buys the annual plan. A week later the customer says they wanted the monthly plan.

Card rail, through a network agent program: The customer can dispute with their issuer, though for a "wrong plan" complaint like this one, the issuer will usually expect them to have asked the merchant to fix it first. If the dispute goes ahead, network rules decide the outcome, the merchant can lose the full $1,200 plus its processor's dispute fee, and its evidence has to persuade a bank it never talks to.
USDC with x401 identity: There is no dispute channel. The customer emails the merchant, who holds a signed approval from a verified person for the $1,200 annual plan. The merchant can refund in full, refund the $1,100 difference and switch the customer to monthly, or hold to its published terms. Any refund goes out as a USDC transfer that the merchant sends.
USDC with no identity layer: The merchant has $1,200 from a wallet address and nothing showing who approved it. It can't tell a confused customer from someone using another person's agent.

The identity check also has a price. Proof prices identity claims individually, and Stablecoin Insider reports that Proof's docs have verifiers without a card on file pay per presentation in USDC on the Base network. We found no published per-check price, so assume $0.50 purely for illustration. That is 2.5% of a $20 order, 0.5% of a $100 order and about 0.04% of a $1,200 order.

For a one-cent API call it would cost 50 times the sale. The math points to a simple rule: identity gating pays off on higher tickets, regulated goods and anything you'd want to defend later, and makes little sense on micropayments unless one verification can cover many calls. Ask any provider how that works before you assume it does.

How Know Your Agent on Stablecoins Differs From Card-Network Agent Programs

Card networks are building their own agent-authentication layers, which The Fintech Times lists among the competing frameworks alongside W3C verifiable credentials. Our explainer on Visa and Mastercard's AI shopping agent plans covers them. The difference that matters to a seller is where accountability sits.

Question	Card-network agent programs	Circle and Proof stablecoin flow
Who knows the buyer	The issuing bank, from account opening	Proof, through an IAL2-proofed credential
Evidence of approval	Issuer authorization plus network agent authentication	Signed, purchase-specific approval the merchant keeps
Customer disputes	Chargebacks under network rules	None; the customer must go to the merchant
Refunds	Credited back to the card through the processor	A new USDC payment sent by the merchant
Who runs it	Card networks and issuers	Open protocols (x401, x402); demonstrated, as of Oct. 31, 2026

Platforms add their own controls too. EconoTimes reports that Shopify has described a buyer-controlled checkout for AI agents, where orders can't proceed until the shopper accepts the total and payment method. The camps also overlap, since Visa contributes to x401, so a seller may end up supporting more than one. Socure's approach to verifying the human behind AI buyers is a useful comparison on the identity side.

The card model protects the buyer, which is why buyers trust it. The stablecoin model takes fraud-chargeback risk off the merchant but hands it every refund decision, and buyers with no chargeback right may hesitate to let an agent spend for them. Whether consumers accept that trade is the open adoption question.

What Online Sellers Should Ask Before Accepting Agent-Initiated Crypto Payments

If a provider pitches identity-verified stablecoin payments from AI agents, get written answers to these first.

Who issues the credential, and to what standard? Ask how the identity was proofed, whose public keys you verify against, and how you learn about revoked credentials or rotated keys.
What does the signed approval cover? Confirm it names the amount, the items, your business and an expiry, and that you can store it with the order record for as long as your retention policy requires.
How much does each verification cost, and how is it billed? Find out whether one check covers a session or each purchase, and which chain and wallet you pay from.
Where does the USDC land, and how do you get dollars? Settlement chain, conversion fees and timing to your bank account all affect cash flow. Our guide to how USDC settlement works for merchants walks through each step.
Have you written a refund policy for agent orders? Write it for a rail with no chargebacks, publish it before the sale, and decide who on your team can send a refund.
Which side screens the wallets? Settle whether the provider or your team checks addresses against sanctions lists, and keep a record.

For the federal framework that governs stablecoin issuers, see our GENIUS Act explainer for merchants.

Your Monday task is smaller: pull your site logs and fraud-tool reports to see whether agents already reach your checkout and whether you're blocking them. Cards are where your existing customers already pay, so make sure your online payment setup handles card-not-present authentication well, including 3-D Secure for higher-risk orders. If you want a second look at how your card stack is set up for agent traffic, request a free quote and a MannyPay specialist will respond within one business day.

Sources

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.