Agentic payments: integration and readiness. 6 chapters and a final quiz.

Chapter 1. A machine-readable catalog.

An agent doesn’t see your website. Not your retouched photos, not your optimized checkout funnel, not your banners. It consumes structured data. If your products don’t exist in machine-readable form, they don’t exist for ChatGPT, Gemini, or Claude, however good your SEO for human visitors is. Agentic visibility is won across three complementary channels.

The 12 non-negotiable attributes

• Title, description, brand: the semantic foundation the agent compares
• GTIN (EAN/UPC code) and MPN: to match your offer with other sellers’ offers
• Standardized category (a product taxonomy such as Google’s): to target queries
• Price, sale price, currency: the agent compares down to the cent
• Availability and condition (new/refurbished): an undeclared stockout means a rejected order and damaged trust
• Image URL and canonical product URL: for display within the conversation

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Cafetiere a piston 1 L",
  "brand": { "@type": "Brand", "name": "Bodum" },
  "gtin13": "0699965238803",
  "image": "https://exemple.fr/img/cafetiere.jpg",
  "offers": {
    "@type": "Offer",
    "price": "34.90",
    "priceCurrency": "EUR",
    "availability": "https://schema.org/InStock",
    "url": "https://exemple.fr/p/cafetiere-piston-1l"
  }
}

In 2026, it pays to cover all three channels, because the mix of agentic traffic is shifting too fast to bet on just one. Schema.org markup is the floor: low cost, maximum reach. The ACP/OpenAI feed unlocks Instant Checkout. The MCP server lays the groundwork for deep integrations, including B2B, where the buyer’s agent queries your ERP directly.

Chapter 2. Agent identification: Web Bot Auth and KYA.

Before accepting a payment from an agent, you need to know who it is. The HTTP User-Agent is self-declared, so it can be spoofed; IP address lists are brittle. The answer now being standardized, Web Bot Auth, has the agent cryptographically sign every request (HTTP message signatures, Ed25519 keys). The server then verifies it against a directory of public keys.

GET /api/catalogue?q=cafetiere HTTP/1.1
Host: exemple.fr
Signature-Agent: "https://agent.exemple-ia.com"
Signature-Input: sig1=("@authority" "signature-agent");
  created=1783607000; keyid="ed25519-key-1"
Signature: sig1=:VGhpcyBpcyBhIHNpZ25hdHVyZQ==:

KYA: Know Your Agent

Technical identification isn’t enough. You also need to vet the agent, the way KYC vets a bank customer. KYA (Know Your Agent) cryptographically binds the agent to a registered operator (its developer) and to the delegating user, with metadata: type of activity, use case, intent. A merchant or PSP can then grade its level of trust.

Chapter 3. Delegated tokens and verifiable credentials.

One rule governs the entire architecture. An agent must never hold a PAN, nor unlimited access to a payment method. All the engineering work of 2025–2026 is about handing it narrow, revocable, traceable powers. Two families of objects do this: delegated tokens protect the instrument, and verifiable credentials prove the mandate.

For a PSP, the target architecture resembles network tokenization with one extra dimension: each token is indexed not only by merchant and instrument, but also by agent and by mandate. Revocation has to work on all three axes. A compromised agent, an expired mandate, and an instrument that needs to be blocked are each handled independently.

Chapter 4. Fraud and disputes: allocating liability.

The classic cardholder-merchant-issuer triangle gains a fourth corner. The agent platform enters the liability chain, whether it is OpenAI, Google, or an assistant developer. Disputes change in nature: fewer stolen cards, more “my agent exceeded its mandate” or “the product delivered doesn’t match what the agent ordered.”

• Tag every agent transaction as such in your systems (a dedicated flag, an “agentic” channel) so you can run separate reporting and fraud rules.
• Set specific limits per agent and per agent operator, separate from cardholder limits.
• Monitor dispute reasons: a high share of “not as described” often signals a problem with your feed quality, not fraud.
• Put contracts in place with agent platforms: commissions, liability, dispute procedure, access to logs.
• A reminder for Europe: the AI Act (phased in from August 2026 to 2027) doesn’t specifically address shopping agents. Consumer protection law and PSD2 remain your frame of reference.

Chapter 5. x402 in practice: HTTP 402 + stablecoin.

x402 beats cards when the buyer is a machine and the cart is tiny. Pay-per-call APIs, single news articles, datasets, AI inference, premium content for crawlers: in all these cases, creating an account and paying a 30-cent fixed card fee makes no sense. x402 settles in USDC, in under a second, for a fraction of a cent.

import express from "express";
import { paymentMiddleware } from "x402-express";

const app = express();

app.use(paymentMiddleware(
  "0xVotreAdresseDeReception",
  {
    "GET /api/rapport": {
      price: "0.005",        // in USDC
      network: "base"
    }
  }
));

app.get("/api/rapport", (req, res) => {
  res.json({ rapport: "contenu premium" });
});

Content publishers have a complementary use case. Cloudflare’s pay-per-crawl, whose dashboard has been unified across all plans since April 2026, lets you charge AI crawlers for your pages without writing code. You set a price per request and Cloudflare collects payment as merchant of record, a model the Monetization Gateway extends, via x402, to any resource behind its network.

Chapter 6. Integration roadmap and governance.

There’s no need to build everything at once: the market is moving too fast for heavy bets. The right approach is incremental. Become visible to agents first, then sellable, and finally industrialized, with governance guardrails at every step.

Governance: the permanent guardrails