Short answer
Separate commerce flows, checkout and payment authorization. Choose eligible channels first, then confirm implementation with your platform or payment provider.
The answer in detail
UCP, ACP and AP2 address different parts of agentic commerce. They describe how systems exchange commerce data, initiate transactions and demonstrate payment authorization. None is a blanket promise that every merchant can accept purchases inside every AI assistant.
The benchmark
The source reviewed protocol and channel status on October 20, 2026. This English review keeps the functional distinctions while replacing the French-market availability verdict with a merchant-and-buyer eligibility check.
| Protocol or program | Main function | Operational question |
|---|---|---|
| UCP, Universal Commerce Protocol | Commerce interactions from discovery through checkout and beyond | Does the platform support the required capabilities? |
| ACP, Agentic Commerce Protocol | Programmatic commerce flows between buyers, agents and merchants | Which agent and checkout implementation actually use it? |
| AP2, Agent Payments Protocol | Verifiable authorization for agent-initiated payments | What mandate, constraints and payment proof are supported? |
| Visa Trusted Agent Protocol / Mastercard Agent Pay | Network-specific agent identification and payment capabilities | Is the merchant's provider enrolled and in production? |
UCP was developed with Google, Shopify and other commerce participants. ACP's source attribution is OpenAI and Stripe. AP2 began with Google and its documentation links to the FIDO Alliance standards work. These are distinct initiatives, even when an implementation combines them.
The official UCP documentation describes compatibility with AP2, MCP and A2A. MCP connects agents to tools; A2A concerns communication between agents. A useful technical specification is not the same as a live distribution agreement or a supported payment method in a particular country.
The current Shopify ChatGPT channel sends customers to the merchant's checkout. Do not infer a generally available native ChatGPT checkout from ACP's capabilities or historical launch materials. Other Shopify agentic channels can have direct-checkout options subject to their own requirements.
The rule
Decide which customer channel is commercially useful before funding protocol work. The platform and payment provider should explain the implementation, settlement, reporting and support arrangements.
The source quotes a demonstration in which an agent passes the customer's shipping and payment context to a website. A protocol governs that exchange: which party sends which data, to whom, with what authorization. It does not remove the merchant's responsibility to validate orders or understand its payment contract.
On Shopify, begin with supported agentic-storefront controls rather than building a server because you have seen “MCP” in a presentation. On a custom platform, involve the payment provider and technical owner. The source cites Stripe's Agentic Commerce Suite and Adyen Agentic as examples, but their market access, supported checkout models and production status require current confirmation.
The steps
- Identify the actual stack: Shopify, another hosted platform or a custom storefront and checkout. Record who controls payment authorization and order creation.
- On Shopify, inspect Sales channels > Agentic and read the requirements for each visible channel. See agentic storefront configuration. Eligibility and available settings can differ by store and plan.
- Ask the payment provider four questions: Which protocols are supported in production? In which merchant and buyer markets? Can we retain our checkout or must we use yours? How do agent-originated orders and disputes appear in exports?
- Repair catalog data before custom integration. Follow the catalog preparation checklist. Product identifiers, availability, pricing and policies must remain consistent across feeds and checkout.
- Improve the product page an AI can cite. Agents that browse the web may read it without using any transactional protocol.
- Record a review date tied to a concrete event: provider confirmation, channel eligibility change, specification release or a measurable business test. Treat announced future rollout dates as plans until supported by current documentation.
The pitfall
A custom integration can be technically complete and still lack channel access. The source's Google onboarding documentation described implementation followed by an interest form and merchant selection. A published standard does not bypass that selection.
The same applies to pilot announcements. Visa’s July 2, 2026 announcement describes live agentic purchases with participating merchants and more than 30 European issuers. That is evidence of selected implementation, not a self-service production offer for every European merchant. Other pilot announcements must likewise be separated from the merchant’s own access.
A custom cashmere retailer described by the contributors had maintained its platform for 15 years and also sold on marketplaces. Its next step was a provider discussion, not installing an app or rebuilding checkout on speculation. Keep llms.txt separate too: content discovery and transactional authorization solve different problems.
What to tell your team
“In this fictional plan, our platform handles protocol support. We will verify channel eligibility, spend three days improving product data and ask our payment provider to document production access, reporting and authorization. We will fund custom work only after those answers establish a usable channel.”
