Skip to main content

Overview

A saved card is a card the account holder already owns, typed once on the card issuer’s page and locked behind their passkey. Nothing is issued and nothing is prefunded: the holder’s own card pays, and every purchase waits for their approval on their own device. It needs no identity verification and no setup beforehand. The holder’s first saved card creates their card account, and they can also save one from the dashboard. Laso never sees the card number. The holder types it on the issuer’s page, which encrypts it on their device before it is stored.

Save a card

Saving the card is the holder’s step, the same way identity verification is. You mint the link and hand it over; you never open it yourself.
  1. GET /get-saved-cards to see what the holder already has. Never send a holder with a saved card through the flow again.
  2. If cards is empty, POST /create-saved-card-link and send the returned url to your human.
  3. Poll GET /get-saved-cards until the card appears.
The page asks for the card and a passkey, with no account to create and no code to type. Each link works once; mint a new one if it expires.
If the holder finished on the page but cards is still empty, the response carries a blocker. needs_code means they saved the card on a card account they already had: they confirm it once with a one-time code in the dashboard. linked_elsewhere means the card account they unlocked belongs to another Laso account. Relay the note either way. Name the card when you talk to your human (“your card ending 4832”), so an approval request reads as a yes or no rather than a question.

Buy with it

Once a card is saved, POST /buy-with-saved-card shops online merchants in plain language and pays with it. The holder approves each order on their own device.

Errors