Adyen Agentic Commerce Pricing: What Merchants Actually Pay to Sell Through AI Agents

Short answer: Adyen has not published a separate price for Adyen Agentic, and at launch it was limited to US enterprise merchants, so there is no rate card to look up. What you can price today is the stack underneath it, and that is ordinary Adyen pricing: a $0.13 fixed processing fee per transaction plus a payment method fee, with interchange and scheme fees passed straight through under Interchange++. There are no monthly, setup, integration or closure fees, but there is a minimum invoice that depends on your industry and business model. The costs that will actually surprise you are the ones Adyen does not charge for at all.

Adyen announced Adyen Agentic on June 16, 2026 as three modular API layers: Agentic Feed for catalog, pricing and availability, Agentic Cart for connecting your existing checkout, tax and fulfillment systems, and Agentic Payments for authentication, token portability, merchant of record and risk on agent-led transactions. It supports the competing standards rather than picking one, so a merchant connects once and reaches OpenAI's Agentic Commerce Protocol, the Universal Commerce Protocol, Google's Agent Payments Protocol and Meta's AI checkout. Named partners include American Express, Mastercard, Visa and Salesforce, with ESW, Scheels, Sezane and SharkNinja among the early merchants.

That is a genuinely good product decision and it says nothing about what it costs. So let's build the number from the parts that are published.

What Adyen actually publishes

Adyen's public pricing page is unusually plain for enterprise payments, which helps here. The model is Interchange++: you pay the real interchange, the real scheme fee, and Adyen's markup on top, itemized rather than blended.

The practical read: if you are already an Adyen merchant, an agent-sourced order priced today looks like any other card-not-present order on your existing contract. Adyen has not signaled a premium for the agentic channel, and the architecture suggests why. Agentic Payments is a way of accepting a token from a different origin, not a new rail with its own economics.

The fees Adyen does not charge you, and somebody does

This is where merchant models go wrong. Your total cost per agent-sourced order is not your processing rate. Three other line items sit on top, and only one of them is a payment fee at all.

The agent platform's own fee. Selling through an AI assistant means the assistant's operator is now a channel, and channels take a cut. OpenAI charges merchants a fee on completed Instant Checkout orders in ChatGPT, and other surfaces are landing on similar arrangements. That fee is negotiated with the platform, not with Adyen, and it is typically larger than your processing cost. We break down the mechanics on our ChatGPT Instant Checkout page, and the equivalent Stripe economics on Stripe agentic commerce.

The cost of a feed that lies. Agentic Feed distributes live pricing and availability into surfaces you do not control. If your inventory count is stale, an agent sells something you cannot ship, and you eat the full acquisition cost plus a cancellation plus whatever the assistant's ranking does to you afterward. Merchants who have run marketplace feeds already know this tax. The fix is upstream of payments: keep the availability numbers behind the feed honest, which for most mid-market operations means tying usage, support tickets and revenue into one view rather than reconciling four dashboards by hand, because an agent-sourced order arrives with no session, no funnel and no referrer you recognize.

Disputes on orders no human watched. Agentic Payments includes risk and authentication, and Adyen's pitch is a risk engine trained on very large transaction volume. It is still the case that an order placed by software on someone's behalf has a different dispute profile than one a person clicked through, and the liability question is not fully settled across schemes. Model a higher dispute rate in year one and be pleasantly surprised.

Is Adyen Agentic available to you?

At launch it was limited US enterprise availability, with global expansion planned but unscheduled. Combined with the unpublished minimum invoice, that puts a real floor under who can buy it this year. If you are a mid-market merchant reading this because you want to be buyable inside ChatGPT before the holidays, Adyen Agentic is probably not your path in 2026, and the honest alternatives are the protocol implementations directly or a platform-managed route.

What to get in writing before you sign

Because there is no rate card, the diligence has to happen in the contract conversation. Five questions, in the order they matter.

Which surfaces am I actually enabled for? "Supports ACP, UCP, AP2 and Meta AI checkout" describes the product. It does not describe your account. Ask which specific assistants your merchant ID can transact on today, and get the roadmap dated.

Is there any agentic-specific fee, now or planned? Get a straight answer and get it in the contract. An unpublished fee is easier to introduce later than a contracted one.

Who is the merchant of record? Adyen states you remain the merchant of record and keep the post-purchase relationship. Confirm that survives every surface you enable, because it is the difference between a channel and a marketplace.

Where does dispute liability land on an agent-initiated order? Per scheme, per surface, in writing. This is the least settled area in agentic commerce and the answers differ.

What is the minimum invoice? It is the number that decides whether any of this is available to you, and it is the one figure Adyen never publishes.

The cost nobody puts in the model

Everything above is the sell side: what you pay to be bought from. If your business also has agents doing the buying, and increasingly both sides of this are true at once, the pricing question inverts and gets sharper. Adyen Agentic, like every agentic commerce product we have looked at, governs acceptance rather than spend. Nothing in Agentic Feed, Agentic Cart or Agentic Payments defines a budget for your own agents, a per-transaction ceiling, a merchant allowlist or an approval threshold, and neither does any payment MCP server your engineering team has connected in the meantime.

That is the correct scope for a processor. It is still a hole in the model, and it is the one that produces a number nobody forecast. A processing rate is bounded by revenue: you cannot pay 0.60% on money you did not take. An agent buying on your behalf has no such ceiling, and the first time anyone notices is usually the statement.

The fix is not a different processor. It is a policy layer above whichever rail you settle on: a funded wallet per agent instead of a shared corporate card, every intended payment checked against spend controls before a credential exists, anything above your threshold paused for human approval, and an audit trail that names the agent, the owner and the policy that allowed it. Keep that rail-neutral and the Adyen decision stays a commercial one instead of an architectural bet.

The short version

Adyen Agentic has no published price because it does not need one yet. It sits on your existing Adyen contract, which means $0.13 plus a payment method fee plus pass-through interchange, negotiated down at enterprise volume. Budget for the assistant platform's channel fee, a higher dispute rate and the operational cost of a feed that has to be right. And if your own agents are spending as well as selling, price that separately, because nothing in this stack is going to stop them.