AI Engineer World's Fair 2026

How AI Agents Pay: Checkout in ChatGPT and Google AI Mode — Sam Parsons, PayPal

Loading slides…

Read the talk

How AI Agents Pay: Checkout in ChatGPT and Google AI Mode

Selected presentation frame from How AI Agents Pay: Checkout in ChatGPT and Google AI Mode — Sam Parsons, PayPal at 92 secondsOpen full source frame
The slide introduces Agentic Commerce Protocol and Universal Commerce Protocol.

Sam Parsons explains three routes from an agent-assisted shopping session to a merchant charge—and how tokenization lets new checkout experiences use existing PayPal Enterprise Payments processing.

From a talk by Sam Parsons

At a glance

Ideas worth remembering

  • ChatGPT’s demonstrated ACP path separates merchant-built discovery from host-provided checkout, then delivers a payment token to the merchant’s MCP server for processing.

  • Tokenization replaces the card credential in the merchant handoff. The described tokens are constrained by merchant, maximum amount, currency and expiration, and transactions retain their checkout-source attribution.

  • Google AI Mode uses merchant-owned UCP sessions, public processor configuration and completion endpoints instead of a merchant-built MCP app; Google Pay supplies the tokenization route.

  • External checkout offers control over the payment experience and methods, at the cost of leaving the agent. A merchant session and completion communication let the MCP app reflect the finished order.

Three ways to reach the merchant’s payment system

A customer can discover a product inside an agent, decide to buy it there, and still have the merchant process the payment through its existing system. The engineering problem is connecting those steps: who presents the products, who collects the payment credential, and what reaches the merchant when checkout finishes? Sam Parsons, a senior staff engineer at PayPal, walks through that connection using PayPal Enterprise Payments—the business previously known as Braintree.

The recording follows three paths:

  • ChatGPT Instant Checkout: an MCP app provides the merchant’s shopping interface, then invokes checkout through the Agentic Commerce Protocol (ACP).
  • Google AI Mode: the Universal Commerce Protocol (UCP) connects the agent to merchant endpoints, with Google Pay handling the payment-tokenization path.
  • An MCP app with external checkout: the shopping interface lives inside the agent, while payment happens on a separate page under the merchant’s control.

Parsons describes ACP and UCP as very similar at this early stage. The practical differences emerge in the interface the merchant builds and the route by which checkout returns a payment token.

0:120:47
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

0:12 · section reference included

ChatGPT: the merchant owns discovery, the host presents checkout

An MCP app adds a rendered interface to an MCP server: HTML and JavaScript can appear inside a supporting agent host. In the examples here, ChatGPT calls this an app and Claude calls it a connector. That interface lets the merchant decide how products appear and how the customer interacts with them. Instant Checkout supplies the next step: an in-chat purchase initiated from that merchant-built interface.

The hotel-booking demonstration makes the division concrete. A customer searches for hotels in ChatGPT, and the travel app presents options through the merchant’s UI. The merchant can shape that interface around the thing being sold; a hotel search need not look like a generic chat response. When the customer selects Proceed to Checkout, the interface changes to ChatGPT’s Instant Checkout experience. The merchant built the discovery screen, while the host supplies the payment screen.

That transition also changes which component does the work. The MCP app asks its host to start a purchase using ACP. The user supplies a card or uses a stored payment credential; the checkout path tokenizes it through PayPal Enterprise Payments. Checkout then sends the resulting token to the merchant, which performs the charge. The app initiates the purchase, but the merchant remains the component that processes the transaction.

2:162:47
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

2:16 · section reference included

A card becomes a constrained token, then a confirmed booking

In the hotel demo, the customer enters a test credit card number into the host’s checkout. Tokenization exchanges that transactable credential for a token: a representation the merchant can submit for payment without receiving the original card number through this flow. Parsons describes this as avoiding an increase in PCI scope from passing the token around. That claim concerns the token handoff; it does not remove the merchant’s existing payment-compliance responsibilities.

Selected presentation frame from How AI Agents Pay: Checkout in ChatGPT and Google AI Mode — Sam Parsons, PayPal at 368 secondsOpen full source frame
A checkout form shows card-entry fields and a payment button.

The host coordinates tokenization with PayPal Enterprise Payments and receives the token back. It then passes the token to the merchant, which processes it using its usual payment integration. The visible result is a return to the hotel app with the booking confirmed. The causal sequence matters: entering a card does not itself update the booking interface. Tokenization supplies a usable payment reference, the merchant transacts with that reference, and the app reflects the completed booking.

Where does the card credential stop, and where does the merchant’s existing processing begin? The flow below separates credential exchange from token delivery and the final UI update. It shows why the merchant can receive a new checkout source while continuing to process a familiar kind of payment token.

The merchant implements two integration points:

  • Start checkout in the widget. JavaScript inside the MCP app triggers the host’s Instant Checkout experience.
  • Receive completion on the server. A checkout-completion tool call reaches the merchant’s MCP server with the payment token. The server can then process it as a typical PayPal Enterprise Payments token.

These touchpoints keep the payment handoff small, but building the MCP app is still real integration work. Settlements, refunds, chargebacks and compliance continue through the existing PayPal Enterprise Payments operation.

The token also limits what can be charged:

  • Merchant: it can be processed only for a given merchant.
  • Maximum amount: it carries a spending ceiling.
  • Currency: it specifies the currency of the payment.
  • Expiration: it cannot remain usable indefinitely.

These constraints limit the token’s permitted use after it leaves the checkout component. Transactions also retain their source attribution, so this payment appears in PayPal Enterprise Payments as a ChatGPT-originated transaction.

From hotel selection to booking confirmation

Merchant hotel appMerchant — Presents hotels and a Proceed to Checkout action inside ChatGPT.
ChatGPT Instant CheckoutHost — Presents the payment screen and coordinates tokenization.
PayPal Enterprise PaymentsPayment processing — Exchanges the payment credential for a token.
Merchant MCP serverMerchant — Receives the checkout-completion call and processes the token.
Booking confirmedMerchant — The customer returns to the updated hotel app.
The host exchanges the card credential for a token. The merchant receives that token, processes the payment, and the hotel app returns with a confirmed booking.
Read the diagram as text
  • Merchant hotel app. Merchant — Presents hotels and a Proceed to Checkout action inside ChatGPT.
  • ChatGPT Instant Checkout. Host — Presents the payment screen and coordinates tokenization.
  • PayPal Enterprise Payments. Payment processing — Exchanges the payment credential for a token.
  • Merchant MCP server. Merchant — Receives the checkout-completion call and processes the token.
  • Booking confirmed. Merchant — The customer returns to the updated hotel app.
  • Merchant hotel app → ChatGPT Instant Checkout: Initiate checkout.
  • ChatGPT Instant Checkout → PayPal Enterprise Payments: Tokenize payment credential.
  • PayPal Enterprise Payments → ChatGPT Instant Checkout: Return token.
  • ChatGPT Instant Checkout → Merchant MCP server: Complete checkout with token.
  • Merchant MCP server → Booking confirmed: Process payment; app reflects completion.
5:506:20
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

5:50 · section reference included

Google AI Mode: publish products and endpoints instead of an app UI

Google AI Mode reaches a similar payment outcome through a different shopping integration. In the running-shoes example, the agent uses UCP to create a checkout session for the user against the merchant. That session belongs to the merchant and provides the entity through which checkout progresses. When the customer chooses to pay, Google Pay tokenizes the payment through PayPal Enterprise Payments. Completion delivers the token to the merchant, which submits it with the transaction information to perform the charge.

The key implementation difference is the absence of a merchant-built MCP app. This integration supplies products and checkout endpoints; it does not require the merchant to design an interface inside Google AI Mode. That removes the app-UI work from this path while leaving the merchant responsible for the endpoints that receive and complete checkout.

The two main touchpoints are configuration and completion:

  • Declare the payment processor. A well-known UCP JSON file identifies Braintree or PayPal Enterprise Payments and supplies the merchant ID and client key. Parsons describes that client key as suitable for public exposure; the configuration described here is not a request to publish a private processing credential.
  • Handle the completed session. A completion call reaches the merchant endpoint with the checkout session ID and the token representing the card behind the Google Pay payment. The merchant uses it to process the transaction.

The token arrives through Google rather than ChatGPT, but settlement, refunds, chargeback risk and compliance remain part of the merchant’s ordinary payment operation.

8:319:01
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

8:31 · section reference included

External checkout gives the merchant the whole payment experience

The third path uses an MCP app for shopping and a separate page for checkout. A product card and checkout button appear inside the agent. Clicking the button opens an external checkout page, where the merchant controls the experience and payment-method choices. The cost is an extra transition: the customer leaves the agent to finish paying.

In the Claude demonstration, the connector loads the merchant-designed shopping interface. The customer picks an item and clicks Checkout, which opens an external link tied to a merchant session. That session connects the purchase shown inside Claude to the checkout performed outside it. After payment completes, the MCP app updates automatically with the order status. Communication behind the scenes carries completion back to the app; the recording does not specify the transport or synchronization implementation.

How can an app inside an agent reflect a purchase completed on another page? The diagram follows the shared session across the handoff and the returning status update. The useful relationship is continuity of the order: checkout moves elsewhere, but the app can still show what happened to the purchase it started.

A shared session connects external payment to the in-agent app

MCP app in ClaudeInside the agent — Shows the merchant’s products and checkout button.
External checkout pageOutside the agent — Opens the merchant session and provides merchant-controlled payment choices.
Completed orderMerchant — Completion and order status are communicated back to the app.
Updated MCP appInside the agent — Automatically reflects the completed purchase.
The customer leaves the agent to pay. Completion communication updates the original MCP app with the order status.
Read the diagram as text
  • MCP app in Claude. Inside the agent — Shows the merchant’s products and checkout button.
  • External checkout page. Outside the agent — Opens the merchant session and provides merchant-controlled payment choices.
  • Completed order. Merchant — Completion and order status are communicated back to the app.
  • Updated MCP app. Inside the agent — Automatically reflects the completed purchase.
  • MCP app in Claude → External checkout page: Checkout link tied to merchant session.
  • External checkout page → Completed order: Customer completes payment.
  • Completed order → Updated MCP app: Communicate completion and order status.
11:0211:31
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

11:02 · section reference included

Choose by destination, UI ownership and checkout friction

Parsons closes with elicitation as a possible improvement to the external handoff. At the time of the recording, he says most major hosts do not yet support it. He presents it as a way to request external validation more smoothly, potentially through an iframe-like experience. It is a prospective improvement; the external-page demonstration is the working path shown here.

The choice follows the customer destination and the control the merchant needs:

  • For ChatGPT with a custom shopping interface: build the MCP app and connect it to Instant Checkout through ACP. The merchant shapes discovery and receives a token to process; the host presents checkout.
  • For Google AI Mode without building an in-agent UI: provide products, UCP configuration and checkout endpoints. Google Pay supplies the tokenization route.
  • For control over the full checkout experience: use an MCP app with an external page and connect the two through a merchant session. The merchant gains control over payment choices while accepting the friction of leaving the agent.

Across the first two paths, new checkout channels feed tokens into familiar merchant processing. The third extends the merchant’s own checkout into an agent-assisted shopping journey. The decision is where to place the customer experience and how much of it to build.

12:5213:22
Suggest correction

This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.

13:22 · section reference included

Transcript download
Full transcript

Loading transcript…