Skip to main content
Sapiom enables your agents to autonomously make purchases for your users. Agents can pretty much do everything they need on the web, but financial infrastructure is still largely walled off. Sapiom is your gate through the wall: your agent can prompt your users to securely add a card and a budget for the next 30 days. Within that budget, your agent will be able to make purchases on its own. The card number is vaulted, and neither you nor your agent nor Sapiom ever sees it. Sapiom strictly guards cardholder information. The basic flow is that your agent asks to buy, Sapiom checks the budget and spending limits, and then Sapiom executes the payment. Inside of one high-level flow, there are many types of online payment variations: UCP and other protocols, multi-currency, and many combinations between merchant payment processors and user cards. Sapiom provides a next action at each point of the payment route to handle every error or edge case.

How it works

OnceThe user adds a card and sets a budget for the next 30 days.Then, for each purchase:
  1. 1RequestYour agent sends what it’s buying.transactionId
  2. 2CheckBudget and your spending limits. Without a budget, the user enters their security code.↻ Repeats: wait, approvalnextAction
  3. 3PaySapiom Browser Pay swaps the placeholder for the real card.payment_ready
  4. 4CompletedSapiom sent the card. Confirm the order with the merchant.completed
Cancel until your agent paysPOST …/cancel
  1. Request. Your agent sends the merchant, the items and the total, with the user’s key.
  2. Check. Sapiom checks the purchase against the user’s budget and your spending limits. Without a budget, the user enters their security code on a hosted page. Your agent follows nextAction until the purchase is payment_ready.
  3. Pay. Your agent fills checkout with a placeholder card. Sapiom sends the real card to the merchant’s payment processor.
  4. Completed. The purchase reads completed. Confirm the order with the merchant.
Until your agent pays, it can cancel the purchase.

Who is involved

Each user’s cards and purchases are visible only with that user’s key.

Start here

First purchase

Make one purchase end to end in the sandbox.

Sandbox

Test cards, a test merchant, and no real money.

Set up your platform

Get your platform key, then a user and a user key for each of your users.

Card data and security

Where the card number goes, and who can see it.