Skip to main content
The USA prepaid card is the fastest way for an agent to pay a U.S. merchant. Your agent calls GET /get-card?amount=X over x402, pays that amount in USDC on Base or Solana, and gets a card_id back. The card number, expiry, and CVV are issued a few seconds later and read from GET /get-card-data. There is no fee: the amount you pay is the amount on the card. Cards are non-reloadable, so order for the exact checkout total when you know it. Nothing is stranded if you do not: leftover balance stays spendable at another U.S. merchant until the card expires.

​
Tell your agent

​
Check the merchant first

Laso Finance prepaid cards work at most merchants, but not all. Before ordering a card, your agent can query Laso’s merchant database to see whether the card is known to work at a given merchant. This is free and only requires a Bearer token from /auth or /get-card. The examples write it as $LASO_ID_TOKEN, exported from your saved credentials. Call GET /search-merchants?q=MERCHANT_NAME with your Bearer token. By default this searches the USA prepaid card (/get-card) acceptance database. Pass card_type=Non-Reloadable International to search for the international prepaid card instead:
The response includes a list of matching merchants with a status field: If a merchant isn’t listed at all, it means no one has tried it yet, and the card likely will still work there.

​
Example response

​
When to use it

  • Before ordering a card — Check the merchant first to avoid wasting funds on a card that will be declined.
  • When a purchase fails — Search for the merchant to see if it’s known to be not_accepted.
  • To build confidence — If the merchant is listed as accepted, your agent can proceed without hesitation.
This endpoint is free. There’s no reason not to check before every purchase.

​
Order the card

1

Agent determines the exact total

Your agent browses the merchant’s website, adds items to cart, and proceeds to checkout to determine the exact purchase total (including tax and shipping).
2

Agent orders a card for that amount

Your agent calls https://laso.finance/get-card?amount=X where X is the checkout total.
3

Server responds with payment details

The server returns a 402 Payment Required response with the price, recipient wallet address, and network (Base or Solana USDC).
4

Agent pays via wallet

An agent with a compatible self-custody wallet lets its x402 client construct and send the payment header, then replay the request. An agent without one pays from a Laso-managed wallet by calling agentX402Pay with route: "get-card", so it never builds a payment header itself. The managed wallet is funded with USDC on Solana.
5

Card is issued

The server verifies payment and returns a card_id with status: "pending". It does not return the card number, CVV, or expiry. Those become available in ~7-10 seconds.
6

Agent retrieves card details

Your agent polls https://laso.finance/get-card-data?card_id=X with the Bearer token until status is "ready", then reads card_details (card_number, exp_month, exp_year, cvv, available_balance, and a billing_address to use if the merchant asks for one).
7

Agent completes the purchase

Your agent enters the card number, CVV, and expiry on the checkout page to complete the order.
The full set of states a card moves through, and the response shape at each one, is documented in the card lifecycle reference.

​
What ordering a card checks

A card order clears three checks and no others. Each is a distinct response you can handle: Neither /get-card nor /order-intl-card reads an identity-verification status, so there is no verification step to complete before ordering and no kyc_required field on either response. Verification is required per feature rather than per account: GET /get-kyc-status reports a wallet’s current state and GET /get-kyc-link starts verification, and both exist for the endpoints that do gate on it. Calling either one changes nothing about a card order.
This describes what the Laso API enforces at order time. Use of an issued card is separately governed by the card issuer’s terms, and a frozen account blocks new orders regardless of verification state.

​
Polling best practices

  • Poll every 2-3 seconds, and don’t hammer the endpoint
  • The card is typically ready within 7-10 seconds
  • If still pending after 30 seconds, something may be wrong. Log the card_id and contact support
  • Always check the status field before reading card_details

​
Limits and restrictions

The USA prepaid card ordered via /get-card is U.S. only. It can only be used at U.S.-based merchants for USD purchases, and physical goods must ship to a U.S. address. For non-U.S. merchants or non-USD purchases, use the international prepaid card. All cards are intended for the caller’s own use and are non-transferable.
When a merchant asks for a billing address or ZIP code, use the billing_address from card_details. The billing name is always Laso Finance. For USA cards no specific address is enforced, so any valid U.S. billing address works and the returned address is a known-good default (ZIP 91723).

​
Next

International prepaid card

Buying from a non-U.S. merchant, or in a currency other than USD.
Uncomfortable with your agent handling raw card numbers? 1Claw’s Payment Card Vault lets agents order Laso cards while keeping the PAN and CVV behind human-gated reveals, per-agent spending limits, and a full audit trail.