Skip to main content
Prava has three integration paths. (A merchant wanting to sell to AI shoppers doesn’t integrate at all; see Agentic Commerce.) Which path you want comes down to two questions:
  1. Who owns the interface: an AI agent, or your own application?
  2. If it’s your application, how do you want to present card entry: inside your own UI, or hand off to a Prava-hosted page?
With Prava the payment itself is always AI/agent-mediated; what differs is who owns the interface and where the card UI lives. All three paths share the same secure core: the card is entered on Prava’s surface and turned into one-time, scoped credentials.

​
Decide in 10 seconds

1

Is the interface owned by an AI agent?

If the surface your user interacts with is an AI agent platform (OpenClaw, Hermes, ChatGPT; supported identifiers), connect Prava as that agent’s payment capability: via MCP (Model Context Protocol: one URL, any MCP client) or the CLI (agents that run shell commands).
2

Otherwise, do you want the card form in your own UI?

You own an AI application, or an app backed by a legal business entity:
The MCP connector is live. Add https://mcp.pay.prava.space/mcp to AI apps like Hermes, ChatGPT, or OpenClaw and pay with no CLI at all. See Prava MCP.

​
Compare the three

​
Pick your path

Embedded (SDK + API)

Card UI inside your own page. Use when you want checkout to feel native to your product.

Hosted (Full API)

Redirect to a Prava-hosted page. Use when you want to ship fast with minimal frontend code.

Agent (Prava Pay)

For AI-agent-owned interfaces. Connect via MCP or the CLI.
Embedded and Hosted are two ways to use the same session; see Integration Modes for the mechanics. Agent (Prava Pay) is a separate product for AI-agent-owned interfaces; start at its overview.