What is agentic commerce?

Agentic commerce is a purchase where a software assistant does the shopping on a person's behalf: it finds a merchant, reads what is available, assembles an order, and completes a checkout. The person still decides what they want and still receives the goods. What changes is that the merchant's storefront has to be readable and transactable by a program rather than only by a human with a browser.

Does publishing an agent-ordering endpoint put my store inside Google or ChatGPT?

No. Speaking a protocol and being listed by a specific assistant are two different things. Google's Universal Commerce Protocol checkout program is open to selected merchants and is joined by expressing interest and completing onboarding in Merchant Center, where endpoints are registered and validated. Publishing a profile is not, on its own, how Google finds a business. Ordering inside Google Maps is a separate arrangement again, built on an activated Google Business Profile and named integration partners. ChatGPT uses OpenAI's own Agentic Commerce Protocol rather than UCP. Any vendor promising automatic placement in a named assistant is overstating what a point of sale can deliver.

Who takes the payment when an assistant places an order?

It depends entirely on the design. In a pay-at-pickup model the assistant places an unpaid order and the merchant collects at the counter on the rails they already use, so nothing about the merchant's payment setup or PCI scope changes. In an in-conversation checkout the payment is authorized during the assistant's flow, which raises the questions a merchant should ask before agreeing: who is the merchant of record, which card-not-present rate applies, who owns a chargeback, and what evidence exists that the cardholder authorized the purchase.

What should a merchant do about agentic commerce today?

Three things that pay off regardless of which protocol wins. Activate and complete a Google Business Profile, since it is free and is the prerequisite Square documents for its own sellers on Ask Maps. Keep the catalog, prices and hours accurate in the system of record, because every agent surface reads from that. And confirm the point of sale can publish a catalog and accept an order without a human retyping it, since that plumbing is what any protocol ultimately depends on.

Does agentic commerce increase PCI scope?

Only if card data flows through a new path. An ordering surface that takes no card and creates an unpaid order stores, processes and transmits no cardholder data, so it introduces no new card-data flow. Overall scope still depends on your whole environment, including systems connected to the cardholder data environment, so confirm it with your assessor. If an assistant-driven flow does capture payment, the same scope questions apply as any other card-not-present channel and should be answered before the channel is switched on.

Merchant guide

Agentic commerce: what AI ordering actually requires.

Assistants are starting to place orders on people's behalf, and every payments vendor now has a slide about it. Underneath the slides are two competing protocols, one invitation-only pilot, and a set of questions about who takes the money that most announcements skip. This guide is the version without the hype: what exists, what it actually takes to participate, and the three things worth doing today no matter which standard wins.

Get a rate review How card data stays out of scope

What "agentic commerce" means, minus the hype

An assistant does the shopping on a customer's behalf: it finds a merchant, reads what is available, assembles an order, and completes a checkout. The customer still chooses and still collects the goods. What changes is the audience for a storefront. For twenty years the reader was a human with a browser. Now some of the readers are programs, and a program cannot interpret a PDF menu, a photo of a chalkboard, or a price that only exists in someone's head.

That is the whole shift, and it is less mystical than it sounds. The practical requirement is that a merchant's catalog, prices, hours and availability exist somewhere a machine can read reliably, and that an order can arrive without a human retyping it.

Two protocols, and they are not the same thing

The industry has not settled on one standard, and a merchant does not have to pick a side to be ready.

UCP — the Universal Commerce Protocol. An open specification published at ucp.dev, backed by Google and Shopify among others. A business publishes a discovery profile at a well-known address describing what it supports, and assistants use a defined checkout API against the business's own server. Square, Google and others have said they are extending it to food ordering.
ACP — the Agentic Commerce Protocol. OpenAI's route, developed with Stripe, is how ChatGPT-side commerce works. It is a different specification with a different onboarding path.
Payment authorization. A separate layer again addresses the harder question underneath all of this: proving a human actually authorized a purchase an agent executed.

The useful takeaway for a merchant is structural rather than technical: discovery, checkout and payment authorization are three separate problems, and a vendor claiming to have solved all three for you today is describing a roadmap.

What Square's Google announcement actually was

In August 2026 Square announced that its US food and beverage sellers can surface in Ask Maps, Google's conversational layer in Google Maps, with menus, hours and location details syncing automatically from Square Dashboard to Google, and checkout running through Order by Cash App.

It is worth being precise about the mechanics, because they are frequently reported as something a merchant can simply switch on:

Square documents an activated Google Business Profile as the prerequisite for its sellers. Google has not published a general requirement.
Menu, hours and location data syncs automatically from Square Dashboard to Google. A copy of the catalog lives outside the merchant's system.
Ordering inside Maps is partner-mediated — Google works with named integration partners rather than accepting any merchant who publishes an endpoint.

Separately, Google runs a Universal Commerce Protocol checkout program that a merchant joins through Merchant Center by expressing interest and being selected. It targets Google's AI answers in Search and Gemini rather than Maps, and a merchant registers and validates their endpoints inside Merchant Center — publishing a profile is not, on its own, how Google finds you. Two different rails, frequently conflated.

The part a payments company should be asked about: who takes the money

Most coverage of agentic commerce stops at discovery. The questions that decide whether it is safe for a merchant are further down.

Pay at pickup

The assistant places an unpaid order; the merchant collects at the counter on their existing rails. Nothing about the merchant's processing changes and no cardholder data touches the ordering path, so it introduces no new card-data flow. Overall PCI scope still depends on the whole environment and is a question for your assessor. The trade is real but modest: goods are prepared or held before money is committed, so stock reservation and a no-show policy matter.

Checkout inside the conversation

Payment is authorized during the assistant's flow. This is where a merchant should slow down and ask the questions that determine cost and liability:

Who is the merchant of record? That answer drives the funding flow, the descriptor a cardholder sees, and who fields the dispute.
Which rate applies? An agent-completed sale is card-not-present. If it is being priced like a card-present tap, the economics on the slide are not the economics on the statement.
Who owns a chargeback, and on what evidence? "The assistant said the customer approved it" is not compelling representment evidence. Ask what artifact proves cardholder authorization.
What happens to a refund? Reversals need to land on the rail that captured the money.

None of that argues against agentic commerce. It argues for reading the contract, which is the same advice that applies to every new channel that has ever been sold to a merchant as free incremental revenue.

Three things worth doing today, whichever standard wins

Activate and complete a Google Business Profile. It is free, independent of any point of sale, and the prerequisite Square documents for its own sellers on Ask Maps. If a business does one thing from this page, this is the one.
Make the catalog true in the system of record. Prices, availability, hours and what is actually sellable online. Every agent surface reads from that data, and no protocol rescues a catalog that is wrong.
Check the point of sale can publish a catalog and take an order without a human retyping it. That plumbing — a readable catalog and an order queue staff already work — is what every protocol ultimately depends on. A business that already runs online orders is most of the way there.

What we are building, stated plainly

LiftedPOS, the point of sale built by Lifted Holdings, is implementing the published UCP profile and checkout API so a merchant can be ordered from on the open standard rather than through one vendor's private integration. It is in development and not enabled for merchant accounts today.

Two design choices are worth stating because they are the opposite of how this is usually done:

No feed leaves the store. Nothing is uploaded, synchronized or registered with Google, OpenAI or anyone else. An assistant asks the merchant's own address and the system answers the request. There is no copy of the catalog sitting in a third party's database to go stale or be repurposed.
Orders arrive unpaid. The first version takes no card at all. The order lands in the online-order queue staff already work and the counter collects the money, so a merchant's payment setup and PCI posture are untouched by turning it on.

When a specific assistant can order from a LiftedPOS merchant, we will say so and name it. Until then the honest claim is narrower: the store speaks the standard, and the merchant keeps their data.

See the LiftedPOS capability set Talk through your setup