> ## Documentation Index
> Fetch the complete documentation index at: https://docs.prava.space/llms.txt
> Use this file to discover all available pages before exploring further.

# Use Cases

> What people build with Prava, shown as concrete flows.

Prava does one thing: it lets an AI agent pay with a real card, without ever holding that card. Here
is what that looks like in practice.

## An agent buys something for you

You tell your agent "order me a phone case under \$20". The agent, connected via
[MCP](https://docs.prava.space/mcp/overview.md) (Model Context Protocol) or the [CLI](https://docs.prava.space/prava-pay/overview.md):

1. Searches products across merchants and picks a case: \$18.50.
2. Locks the live price with a quote.
3. Sends you a payment link. You open it and approve with Face ID.
4. The agent completes the checkout. You get an order id; the agent never saw your card.

If the total had changed mid-checkout, the charge would not have gone through. The credential is
locked to that merchant and that amount.

**Start here:** [Connect via MCP](https://docs.prava.space/mcp/connect.md) or [Prava Pay quickstart](https://docs.prava.space/prava-pay/quickstart.md).

## An agent pays a bill you already know

No product discovery needed. You say "pay my $54.20 internet bill at Comcast". The agent creates a
payment session for exactly $54.20, you approve with a passkey, and it pays with the one-time
credentials. Wrong-amount or wrong-merchant use is declined.

**Start here:** [Payment sessions (CLI)](https://docs.prava.space/prava-pay/sessions.md) or
[create\_payment\_session (MCP)](https://docs.prava.space/mcp/tools.md#create-payment-session--checkoutrun).

## Your AI app takes payments from its users

You're building a shopping assistant, a travel planner, or a booking bot. Your users need to pay
*inside your product*. You integrate the [SDK + API](https://docs.prava.space/sdk/overview.md): your backend creates a session,
your frontend shows Prava's secure card form, and your app receives one-time credentials to complete
the purchase. Your servers never touch a card number, which keeps you out of PCI scope (the
security compliance that applies once you handle card data).

Example: a stylist app's user picks a $79 jacket. The app creates a session for $79, the user enters
their card and approves in the embedded form, the app checks out at the boutique with the one-time
token, then reports the result.

**Start here:** [Add Payments to Your AI App](https://docs.prava.space/guides/add-payments-to-your-ai-app.md).

## Human-in-the-loop, by design

Every flow above has the same shape: **the agent proposes, the human approves, Prava executes.**
The approval is a passkey (Touch ID / Face ID) on the user's own device. An agent cannot skip it,
and an approval for one purchase authorizes nothing else.

## Recurring payments

A [mandate](https://docs.prava.space/concepts/mandates.md) is the user's standing permission to pay: approve once, and the agent
charges within caps without a fresh passkey each time. A user approves "up to \$12/month at one
merchant" a single time, and the agent charges monthly within those limits. *Scheduled* subscriptions —
where Prava auto-charges each cycle — are coming next; for now the agent initiates each charge.

## Where to next

> [card] [Choose your integration](https://docs.prava.space/choosing-your-integration.md)
>
> Agent, embedded, or hosted. Decided in 10 seconds.

> [card] [How Prava works](https://docs.prava.space/concepts/how-it-works.md)
>
> The lifecycle behind every flow above.

> [card] [Sell to AI shoppers](https://docs.prava.space/integration/merchants.md)
>
> For merchants: what works with zero changes.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.