AI Agents Just Paid Real Invoices. Here's the 5-Protocol Payment Map

No affiliate links on this page — every link points to official docs or reporting, nothing sponsored.

On October 20, Visa, BILL, and Billtrust announced the first live pilot of trusted AI agents initiating and completing approved buyer invoice payments, end to end, through supplier portals. Not a sandbox demo — real B2B invoices, paid through real supplier portals. We dug through the announcement and the protocol docs to map what actually launched and how it compares to the four other protocols racing for agent payments.

What actually launched

Three pieces clicked together in one pilot:

1. Visa Intelligent Commerce provides the rails. The Visa Trusted Agent Protocol (launched October 2025) plus an Agentic Directory. BILL's Payment Agent is registered through the protocol and pays with tokenized credentials under buyer-approved payment controls.

2. BILL's Payment Agent does the paying — but not the deciding. Here's the part most headlines will skip: the agent does NOT decide which invoices to pay. The buyer approves; the agent executes. Approval sits with the human, execution with the machine.

3. Billtrust authenticates the agent at the supplier portal. This is the quietly radical part. Billtrust verifies the agent's identity right at the portal — satisfying CAPTCHA and bot-blocking protections without an agent login and without sharing portal credentials. For years, the entire agent-payments conversation dead-ended at "but the portal will CAPTCHA-block your bot." Billtrust built the handshake that says: this bot is verified, let it through.

The pilot is already processing transactions with participating BILL buyers and Billtrust suppliers, per the announcement.

The honest caveats

I should say the part nobody in the announcement said out loud:

• No numbers. Transaction volumes, efficiency gains, error rates — none disclosed. Real transactions, yes; scale, unknown.
• No wider-availability date. This is a pilot with participating customers. There is no general-availability timeline yet.
• The agent is a payment executor, not a decision-maker. Invoice approval stays with the buyer. That's the right design for v1, but it's a narrower claim than "agents pay invoices."
• Replacing CAPTCHA is a security story, not just a convenience story. Verifying agent identity at the portal is a new trust boundary. Verified by whom, revoked how, audited how — the hard questions move; they don't disappear.
• Five protocols are racing for this space. Picking one to build on today is a bet, not a standard.

The 5-protocol payment map

The whole board, in one place:

And one more identity-layer piece worth knowing: Cloudflare Web Bot Auth (Oct 2025, with Visa/Mastercard) — signed HTTP messages as agent identity. Every payment protocol above needs verified agent identity underneath it; this is one answer to that layer.

The demand signal is not theoretical. Adobe data shows AI-source traffic to US retail sites grew 393% year over year in Q1 2026. The shoppers are already agents. The payment rails are what's catching up — five of them, at once.

What this means if you're building agents

• Your agents pay at checkout → map ACP + UCP first. They're the closest to retail surfaces your users actually buy from.
• Your agents touch invoices or accounts payable → this pilot is the only protocol-built path that exists. Watch the Trusted Agent Protocol registry; nothing else is live here.
• You sell API or data access → x402 gives you per-request stablecoin payments today. Unusual, yes. Working, also yes.
• Identity is the foundation. AP2 mandates and Cloudflare Web Bot Auth are the trust layer everything else leans on. None of the payment protocols work without verified agent identity — the CAPTCHA problem this pilot solved is the same problem everywhere else.
• Don't standardize on any one yet. Ship against the one closest to your use case, behind an abstraction you can swap when the race settles.

FAQ