Skip to main content
Sendpaper accepts Stripe shared payment tokens (SPTs), the way AI agents pay merchants on your behalf. Your agent never sees your card number and neither do we. Each token is capped at one order’s price, works once, and expires.

How it works

1

The agent creates the order

create_postcard or create_letter returns the order id and its exact price, for example ord_8k2m… for $2.99 (299 cents).
2

You approve the payment

Your agent asks Stripe Link for a one-time token for that amount. You approve it in Link, on your phone or in the agent.
3

The agent pays

The agent calls pay_order with the token. We charge it once, the order is marked paid, and it goes to print.
If the agent can’t get a token, it gives you the order’s checkout link instead. That’s a normal Stripe Checkout page, where you can also pay with Link, cards, Apple Pay and more. Agents that have Stripe’s Link CLI (as a skill or MCP server) can request a token like this:
  • --amount is the order’s price.amount_cents.
  • Sendpaper’s Stripe network ID is returned by the get_pricing tool (payment.stripe_network_id).
  • --request-approval asks the user to approve before the token is issued.
Then pay:

Over HTTP

The response is the updated order with "status": "paid".

Errors your agent can fix

Paying is safe to retry: the same token is never charged twice for the same order.

Safety

  • You approve every payment. Agents should only call pay_order after you’ve agreed to the purchase and price.
  • Nothing extra is stored. We keep the Stripe payment reference for refunds, never the card.
  • Refunds: if we refuse a piece under the content policy, or you cancel before printing, the payment is refunded in full.