Skip to main content
Sapiom Pay enables your AI agent to buy from merchants with a buyer’s securely vaulted card. The buyer adds their card once on a hosted page. For each transaction, Sapiom checks what is being bought and who it is from, asks the buyer to confirm, and then fills the card into checkout. Your agent never sees the real card details. To try the tools as one of your buyers, create a buyer key (quickstart steps 1 and 2), then paste this into an agent that supports remote MCP servers:

​
The integration in brief

  1. Create a buyer for each user. Your backend creates a buyer and its key.
  2. Save their card. The user adds their card once, on a hosted page that shows your brand.
  3. Request a transaction. With that user’s key, you send the merchant’s UCP checkout or, for any other merchant, the total your agent read from its checkout page.
  4. The user approves. They approve on a hosted page that shows what they are buying.
  5. Pay. Your browser worker fills checkout with a placeholder card, and the Sapiom Browser Pay SDK swaps in the real card.
  6. Confirm the order. Tell the user once the merchant confirms it.
How it works explains each step.

​
What works today

Sapiom Pay buys at any checkout Browser Pay can pay. The merchant doesn’t need the Universal Commerce Protocol (UCP). Outside UCP, your agent states the items and total, and the merchant’s page is the only order confirmation. See Checkout paths.

​
Start building

Quickstart

Create a buyer, save a card and connect your agent.

How it works

Who does what in a transaction.

Authorize a transaction

Turn a merchant checkout into an approved payment.

API reference

REST endpoints, MCP tools and the Browser Pay SDK.