Overview
How might we complete a purchase inside the AI surface without skipping informed consent on item, seller, total, and payment?
When to use
- Shopping assistants and discovery feeds where leaving for a merchant site kills conversion.
- Repeat buys once a wallet and shipping address already exist in the product.
- Low-to-mid consideration goods where card, total, and seller are enough to decide.
- Answer or feed UIs that already show product cards with price and retailer attribution.
When to skip
- High-consideration B2B deals that legally need quotes, contracts, or sales review.
- Regions or categories where in-chat checkout is not compliant.
- When payment credentials cannot be secured inside the AI client.
States
Design the money path as a short state machine, not a single Buy button that charges silently.
- 01
Offered
A product card stays in the thread with image, title, price, seller, and Buy. It remains as history after checkout starts.
- 02
Preparing
Ephemeral agent working on the offer card while shipping, payment, and total assemble. It does not become a permanent message.
- 03
Reviewing
A new checkout card appears below the offer with ship-to, payment, and all-in total. Cancel stays first-class. The offer above stays visible.
- 04
Processing
Payment is in flight on the checkout card. The UI blocks double-submit and says what is happening instead of freezing blank.
- 05
Confirmed
Receipt replaces the checkout card in place. The earlier offer card remains above as thread history.
- 06
Cancelled
The person backed out. Return to the offer card with no charge and no leftover “pending” state.
- 07
Failed
Payment or fulfillment failed. Say why, keep the cart intact when safe, and offer retry or another method.
Key UX elements
The parts that must be present before real money moves.
Card
Show the product people are about to buy.
Image, title, price, rating, and seller on one scannable card so the offer is comparable before Buy.
Buy
Put purchase on the product surface.
Buy now lives on the card or detail, not behind a hop to a homepage. First tap starts checkout prep, it does not charge.
Total
Disclose the all-in amount before pay.
Item price plus tax, shipping, and fees. A headline price that changes after Pay is not consent.
Payment
Show which instrument will be charged.
Masked card, wallet, or “add payment” for first-time buyers. Never imply a stored method that is not there.
Pay
Make Pay the explicit money verb.
Pay states the amount. Cancel is equal weight. Agents must not auto-execute spend from run-through mode.
Receipt
Leave a durable order record.
Success restates item, seller, ship-to, and payment, then points to tracking or support.
Rules
One-tap buy without showing final price, fees, seller, or return terms.
Purchases that fire from agent execute mode without a confirm step.
Broken handoff that dumps users on a homepage after “buy.”
Upsells added after the user confirms the original item.
Evidence
| Product | Implementation |
|---|---|
| Perplexity Shopping | Product recommendations with purchase paths from the answer surface. |
| Amazon Rufus | Assistant-guided discovery that stays in the Amazon buy graph. |
| Google Shopping | AI-assisted product finding with merchant checkout routes. |
| ChatGPT commerce plugins / apps | In-thread product cards that continue into pay and confirm flows. |
