Skip to main content
Stripe Link is Stripe’s payment wallet. Conto integrates with it at two points in a Link checkout: right before Link opens, and right before your agent submits the payment. Conto checks the purchase against the owner’s rules at both points. The agent opens Link and pays only after Conto approves. Then it reports whether the payment went through. Conto decides, and your agent’s platform enforces the decision. The buyer pays with their own Link account. Nobody connects Link to Conto. Try the Stripe Link demo to shop with Claude and see Conto check a purchase before Link checkout.

Add the checkpoints

You need an agent and its SDK key. Create the agent in the dashboard, then choose Generate SDK Key on its SDK Integration tab.
If any call throws, stop the checkout and do not pay. checkoutMethod defaults to LINK, so a Link checkout can leave it out. checkoutUrl is the store’s checkout page. Conto names the merchant by its domain. See the merchant is the checkout domain. Reuse the same idempotencyKey when you retry begin(). After a timeout, read the checkpoint with conto.checkout.get() before you retry. Never submit the payment twice. Checkout checkpoints covers every stage, the HTTP endpoints, and the MCP tools.

When the owner must approve

New organizations start with these limits: 25pertransaction,25 per transaction, 100 a day, and owner approval above 10.The10. The 15 purchase above goes to the owner for approval. See starter guardrails. When a rule requires approval, begin() returns the stage AWAITING_APPROVAL. Conto holds the $15 against the agent’s limits and sends the owner an approval request. Do not open Link while the checkpoint waits. waitForApproval() returns the checkpoint once the owner approves it. The agent then has 30 minutes to confirm. If the owner rejects the purchase or the request expires, waitForApproval() throws and Conto releases the spend. See when the owner must approve.

Report the outcome

After the agent submits the payment, it reports one outcome on the confirmed checkpoint:
  • PAID keeps the amount counted toward the agent’s limits.
  • NOT_PAID releases it.
  • UNKNOWN keeps it counted until the agent reports again or the owner records what happened.
Report an outcome only after confirm() succeeds. To stop before that, cancel the checkpoint with conto.checkout.cancel().

What the owner sees

  • Approvals. A purchase that needs approval appears in Alerts & Approvals with the merchant, the checkout site, the payment method, the items, the purpose, and the agent. The owner chooses Approve purchase or Reject purchase.
  • Transactions. Each checkout appears in Transactions. Its page shows the status, the amount, the agent, the order number, and each step.
  • Missing outcomes. When a confirmed checkout has no outcome, the owner gets an alert. After checking the order with the merchant, an Owner, Admin, or Manager chooses Mark as paid or Mark as not paid on the checkout page.
With the Stripe Link card integration, the agent asks Conto before it asks Stripe Link for a card. Stripe Link is asked only after Conto approves the purchase, for exactly the approved amount at that store. The person still approves the card in the Link app, and Conto does not receive the card number. Use it when the agent fills in a store’s card form with a Link card.

Stronger control with connected cards

Checkpoints rely on your agent’s checkout to call Conto and follow the answer. Conto does not see the Link payment, so it records the outcome your checkout reports. For control at the moment of payment, use a connected card. Conto releases a single-use card credential only after the owner’s controls pass. Connecting a card to Conto does not connect a Link account.