Guide

Agentic checkout for AI shopping apps: the full flow

Agentic checkout for AI shopping apps: the full flow

Agentic checkout for AI shopping apps: the full flow

The five steps from a product request to a confirmed order in an AI shopping app, and what to do when a price, a store or a payment changes.

Guide: Agentic Checkout for AI Shopping Apps

When a user asks a shopping assistant for something specific, such as a waterproof rain jacket under $150, the agent can usually do the research well. It reads reviews, compares fabrics, checks sizing and picks a good option.

Many apps then hand the user a link to the store. The user opens a new tab, often has to create an account, types in their card and waits for a verification code, and some of them give up along the way.

If the agent can't complete the purchase, the app is mainly a search tool. This post covers what it takes to build checkout into an AI shopping app: the five steps involved, what the approval screen should show, what goes wrong in real stores, and how fast checkout can be.

The five steps of agent checkout

  1. Find. The agent searches products across stores. Prava's Shop API covers any store on UCP, the Universal Commerce Protocol, plus merchants we've enabled directly, such as Macy's. Search understands how people describe things: "750 ml" and "0.75 L" find the same bottle.

  2. Quote. Before asking anyone to approve, get the exact total: item price, shipping, tax, import duties and any discount code. Prava's quote holds that price for about 15 minutes, so the number the user approves is the number they pay.

  3. Approve. The user sees the store, the items and the total, and approves with a passkey. That approval produces a one-time card network token locked to that store and that amount. The agent never sees the user's card.

  4. Check out. UCP stores and merchants with an API get the order directly, in 5 to 20 seconds. Everywhere else, Prava's Browser Harness completes checkout on the store's own website, the way a person would. The store doesn't integrate anything.

  5. Confirm. Your server gets a signed webhook when the payment succeeds or fails, and your agent tells the user the order is placed.

What the approval screen should show

The store's name, each item with size or color, the full total with shipping and tax, and the card it will be charged to. If any of these is missing, users are right to hesitate. Once the screen shows all of it, a single Face ID or Touch ID confirmation is enough.

Common problems and how to handle them

Situation

What happens

The price changed after the quote

Re-quote and ask again. Never charge more than the user approved.

The store adds paid extras, like package protection

The Browser Harness removes them before paying.

The final total doesn't match the approval

Checkout stops before payment.

The last step is unclear, like an unusual form

It stops and asks a person instead of guessing.

The payment is declined

Your app gets the reason and can ask the user to pick another card.

The user doesn't approve in time

The session expires after 15 minutes and nothing is charged.

Checkout speed

On UCP stores, checkout takes 5 to 20 seconds. On regular store websites, Prava's browser checkout takes 10 to 20 seconds on most stores in our runs, where general-purpose AI browser agents usually take one to two minutes. On slower sites it finishes in under 40 seconds, against two to four minutes.

Repeat purchases without asking every time

Some purchases, like coffee, printer ink and groceries, repeat regularly. With a mandate, the user approves once with a passkey and sets the limits: which store or product, how much, how often, and for how long, such as up to $30 a month. Each order still gets its own one-time credential and is checked against the store's real price. Limits can renew weekly, monthly or yearly, and the user can pause or cancel them.

Building checkout with Prava

Prava covers all five steps in one API: the Shop API to find and quote, a passkey approval and one-time network token to pay, checkout on UCP stores and regular store websites, and signed webhooks to confirm. Payments run on Visa Intelligent Commerce and Mastercard Agent Pay. You keep your product, your agent and your brand. The card form and approval sheet carry your logo and colors, embedded in your app or on a hosted page. See how the pieces fit together.

Summary

  • Checkout in an AI shopping app has five steps: find, quote, approve, check out and confirm.

  • Get the exact total, including shipping, tax, duties and discount codes, and hold it before the user approves.

  • Checkout has to work on every store, including ones that never integrated with you. Prava completes it in 5 to 20 seconds on UCP stores and 10 to 20 seconds on most other store websites.

To try it, create sandbox keys in the dashboard and follow the quickstart.

FAQ

Do stores need to integrate with Prava? No. UCP stores and directly enabled merchants are reached through their APIs, and the Browser Harness checks out on regular store websites. To the store, it's a normal card payment.

Who is the merchant of record? The store. Prava never holds the money.

How do returns work? Through the store, like any card purchase. The refund goes back to the user's card.

Can I use my own checkout automation? Yes. You can use Prava only for approvals and payment tokens and run checkout yourself.

Sources

Prava team

Copyright © 2026 Prava Payments Inc. All rights reserved

Copyright © 2026 Prava Payments Inc. All rights reserved