What is PayPal agentic commerce?
PayPal agentic commerce is the umbrella name for the services PayPal sells to merchants who want to be bought from inside an AI assistant. PayPal launched it on October 28, 2025 under the label agentic commerce services, and the announcement named exactly two things: an agentic payment solution and a catalog and order management offering. Those became Agent Ready and Store Sync. The framing matters more than the names. Every other major player in this market published a protocol and asked merchants to implement it. PayPal published a pair of managed services and asked merchants to enroll. If you are trying to work out which vendor to spend engineering time on, that is the first fork in the road, and it is the reason the rest of this page reads differently from our write-ups of Stripe agentic commerce and Shopify Agentic Storefronts.
What is PayPal Agent Ready?
Agent Ready is the payments side. PayPal describes it as letting existing merchants accept payments on AI surfaces, covering both supervised shopping (a person watching an assistant buy something) and automatic shopping (an agent buying without a human present), across conversational and browser-automated experiences. The pitch that PayPal keeps repeating is that it runs on top of your current checkout configuration, so a store already taking PayPal is eligible without new integration work, and PayPal fraud detection, buyer protection and dispute resolution come along unchanged. PayPal said at launch that Agent Ready would be available in early 2026, and it has been rolling out to merchants since, expanding coverage progressively rather than flipping on for everyone at once. If you are evaluating this, the honest question to ask your account team is not whether Agent Ready exists but which AI surfaces your specific account is enabled for today.
What is PayPal Store Sync, and what did the Cymbio acquisition change?
Store Sync is the discovery side, and it is the half that had a gap. It connects your product data, inventory and fulfillment to AI shopping surfaces, then drops resulting orders into the order management system you already run. Two commitments in PayPal's description are worth reading closely, because they are exactly what merchants lose in a marketplace arrangement: you keep merchant of record status, and you keep control of brand visibility and customer communications. At launch PayPal reached Store Sync through partners, naming Wix, Cymbio, Commerce (BigCommerce and Feedonomics) and Shopware. Then on January 22, 2026 PayPal announced it would acquire Cymbio outright, a Tel Aviv multichannel orchestration platform founded in 2015, and closed the deal on February 5, 2026. PayPal said plainly that the Cymbio team and technology would power Store Sync. In other words, the catalog syndication layer moved from being a partnership to being owned infrastructure, which is a reasonable signal about how central PayPal thinks it is.
Where PayPal agentic checkout is actually live
The integrations arrived faster than the product names suggest. PayPal and OpenAI announced a partnership on October 28, 2025, the same day as the agentic commerce services launch, to power Instant Checkout inside ChatGPT, with PayPal stating it would adopt the Agentic Commerce Protocol so ChatGPT users could check out with PayPal and so PayPal merchant catalogs, small businesses as well as large retail brands, would reach ChatGPT commerce during 2026. Perplexity went live first in practice: an integration launched just before Black Friday on November 25, 2025, letting people search, compare and buy inside Perplexity's chat interface using PayPal passkey authentication. Microsoft Copilot is the third surface PayPal and Cymbio both cite. If you want the mechanics of the ChatGPT side specifically, we cover them in ChatGPT Instant Checkout.
Does PayPal support the Agentic Commerce Protocol?
Yes, and this is a point of genuine confusion because PayPal simultaneously sells you a service that means you do not have to care. ACP was co-developed by Stripe and OpenAI and is the specification behind ChatGPT Instant Checkout. PayPal committed to adopting it, and the practical effect is that PayPal implements ACP so that its merchants do not have to. Your store does not stand up an ACP endpoint, publish a feed or handle a delegated payment token. PayPal's server speaks ACP to OpenAI on your behalf and settles into your existing PayPal account. That is the entire value proposition, and whether it is the right trade depends on how much you mind the intermediation. A merchant implementing ACP directly through Stripe owns the integration and the roadmap. A merchant going through Agent Ready owns neither and ships in a fraction of the time.
What the PayPal MCP server and agent toolkit actually do
This is the part most search traffic is actually looking for, and it is a different product from Agent Ready. The PayPal agent toolkit integrates PayPal REST APIs into AI agent frameworks, with support for the Model Context Protocol alongside Amazon Bedrock, CrewAI, LangChain, OpenAI's Agents SDK and Vercel's AI SDK. The PayPal MCP server exposes those APIs as callable tools, grouped roughly into invoicing (create_invoice, send_invoice), payments and refunds (create_order, create_refund), disputes (list_disputes, accept_dispute_claim), shipment tracking (create_shipment_tracking, get_shipment_tracking) and subscriptions (create_subscription_plan, cancel_subscription). Google also documents a PayPal MCP tool for its Agent Development Kit. The general shape of MCP payment tooling, and where it stops, is covered in MCP payments, and we compare PayPal's server against Stripe, Square, Checkout.com and Adyen in payment MCP servers.
The PayPal MCP server is a merchant back office, not an agentic checkout
Read that tool list again and notice what is in it. Drafting invoices, capturing orders, issuing refunds, accepting dispute claims, cancelling subscriptions. These are seller-side operations against your own PayPal account. The MCP server lets an agent run your back office. It does not let a shopper's agent buy from you (that is Agent Ready) and it does not let your agent buy from someone else with a budget attached. It is also worth being precise about the risk it introduces: an agent holding your PayPal API credentials can issue refunds and accept dispute claims, which are irreversible movements of money that no MCP tool definition constrains. If you connect it, scope the credential and log every call.
We probed the payments industry for agent discovery endpoints
A reasonable merchant assumption in 2026 is that becoming agent-discoverable means publishing a file, the way robots.txt or a sitemap works. Shopify reinforced that assumption by emitting a UCP capability document at /.well-known/ucp for every eligible store. So on September 3, 2026 we tested whether the payments industry does anything similar. We requested six candidate discovery paths across nineteen payment and commerce hosts, followed redirects, and, critically, checked the response content type rather than trusting the status code. We also sent a deliberately nonsense control path to each host to catch catch-all servers. That control step is the whole methodology, and the table below shows why.
The probe shows PayPal agent discoverability is enrollment-gated, not file-gated
The result is cleaner than we expected. Across nineteen hosts, not one payment provider served a machine-readable agentic discovery document at a well-known path. Every apparent hit was a catch-all HTML shell: braintreepayments.com, paypal.ai and shopware.com each returned HTTP 200 with HTML for a path we invented on the spot, so their 200s on /.well-known/ucp and /.well-known/agent-card.json mean nothing. The only genuine machine-readable agent artifact in the entire payments set belonged to Shopify, a commerce platform rather than a processor, and it was a Web Bot Auth signing key directory rather than a commerce capability file. The practical conclusion for a merchant is worth stating flatly: there is no file you can publish to make PayPal treat you as agent-ready. Discovery runs through enrollment at PayPal.ai and through the Store Sync connectors, not through the open web. If a consultant tells you to add a well-known endpoint to become PayPal agent-discoverable, they have invented that.
Almost no payment provider has an opinion about AI crawlers yet
While we had the hosts open we checked something adjacent and more actionable: whether these companies name AI crawlers in robots.txt at all. Eleven of the twelve payment and commerce hosts we parsed named none of GPTBot, OAI-SearchBot, ChatGPT-User, PerplexityBot, ClaudeBot, Google-Extended, Amazonbot, Applebot-Extended, Bytespider, CCBot or meta-externalagent. No allow, no block, no rule. Only shopware.com had written any AI crawler policy, and it was a set of partial path disallows rather than a blanket position. Ten of the nineteen hosts did serve an llms.txt, including paypal.com, developer.paypal.com, stripe.com, adyen.com, checkout.com, squareup.com, shopify.com, bigcommerce.com and wix.com. PayPal's is dated February 28, 2026, version 1.0.4, and opens by describing itself as part of a proposed standard for machine-readable LLM guidance. So the industry has adopted the voluntary summary file and has almost entirely ignored the enforceable one, which tells you where the actual thinking is.
PayPal agentic commerce compared with Stripe ACP and Shopify Agentic Storefronts
These three are not competing implementations of the same idea. Stripe gives you a protocol and expects engineering. Shopify switched a sales channel on by default and most merchants were live without knowing. PayPal sells a managed service that wraps the protocol so you never see it. The right choice follows from where your catalog already lives and how much control you want over the integration. A Shopify store that also takes PayPal can end up reachable through both paths at once, which is fine but worth knowing about when you try to attribute an order. The comparison table below is the honest version, including where PayPal is the weaker answer.
What PayPal agentic commerce does not do on the buy side
Everything above concerns money moving toward you. There is a second half of agentic commerce that PayPal's merchant services deliberately do not address: governing what your own AI agents are allowed to spend. Searching PayPal's agentic commerce documentation for a developer-facing spend policy engine, a programmable human approval step, per-agent scoped card issuing or an agent-attributed audit log returns nothing, because those are not what Agent Ready is for. Its controls are framed around a consumer deciding whether to let an assistant buy on their behalf, not around a finance team deciding what a fleet of production agents may purchase. If you run agents that spend company money, that layer is still yours to build or buy, and it is what agent spend controls and agentic payments governance exist to cover. We lay out the split in more detail on our PayPal Agentic Commerce alternative page.
How to get set up with PayPal agentic commerce
The sequence is short because most of the work is not yours. First, confirm you are an existing PayPal merchant in good standing, since Agent Ready builds on the checkout configuration you already have. Second, go to PayPal.ai and request access, which is the documented route: PayPal asks merchants to complete a form to contact its AI team for onboarding. Third, decide how your catalog reaches Store Sync, either directly or through one of the named connectors, Wix, Cymbio, BigCommerce with Feedonomics, or Shopware. Fourth, confirm with PayPal which AI surfaces your account is actually enabled for, because rollout has been progressive and the answer differs by merchant. Fifth, and this is the step people skip, work out how you will recognize an agent-originated order in your own reporting before the volume arrives rather than after.
Who PayPal agentic commerce is right for
It fits best if you already process meaningful volume through PayPal, your catalog sits on a platform PayPal has a connector for, and you have no engineering appetite for implementing a commerce protocol yourself. Under those conditions it is genuinely the lowest-effort route into AI shopping surfaces available, and the buyer protection and dispute machinery are real advantages over agent rails that have neither. It fits worst if you want to own the integration, need behavior PayPal has not exposed, or care about being intermediated between your store and the assistant. And it does nothing at all if your problem is the buy side, where the question is not how you get paid by an agent but what your own agents are permitted to spend.