Skip to main content
Laso Finance lets an AI agent order a non-reloadable U.S. prepaid card for the exact checkout amount with USDC on Base or Solana through x402. An agent with a compatible self-custody wallet constructs and sends the x402 payment header. GET /get-card returns a card_id with status pending; poll GET /get-card-data until status becomes ready, then retrieve the card details programmatically. An agent without a compatible wallet can use a Laso-managed wallet instead. This page is the canonical reference for that flow, start to finish.

​
How to make an online purchase

Once your agent is set up and authenticated, it can buy things online using a prepaid card from Laso Finance. Laso offers two prepaid card products via x402:
  • USA prepaid card (GET /get-card): issued instantly. USD, U.S. merchants only, ships to U.S. addresses. Min $5, max $1,000.
  • International prepaid card (GET /order-intl-card): queued for admin fulfillment (typically within 24 hours). USD, usable globally. Min $100, max $1,000 in whole dollars, plus a 3.8% fee.
Pick the USA card for U.S. merchants (fastest, no fee). Pick the international card if:
  1. You or your agent are outside the United States.
  2. Spending at a merchant headquartered outside the United States.
  3. Spending in a non-USD currency.
Here are example prompts:

​
What happens under the hood

When your agent calls a Laso Finance endpoint, the x402 protocol handles payment automatically:
1

Agent navigates to the store

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 checks merchant compatibility (optional)

Before ordering a card, your agent can call GET /search-merchants?q=nike to check if the card is known to work at that merchant. If the merchant comes back as accepted, you’re good to go. If not_accepted, the card will fail there. If the merchant isn’t listed or is unknown, it just means no one has tried it yet. The card likely will still work.
3

Agent orders a card for the exact amount

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

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).
5

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.
6

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.
7

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).
8

Agent completes the purchase

Your agent enters the card number, CVV, and expiry on the checkout page to complete the order.
Cards are non-reloadable, so ideally your agent should order a card for the exact amount of the checkout total. That way there are no extra funds left over on the card.

​
Example: buying an item

Here’s what a full purchase flow looks like when you tell your agent to buy something:
Your agent will:
  1. Navigate to Nike.com and find the Nike Air Max 90s in size 10
  2. Add the item to cart and proceed to checkout
  3. Determine the exact total including tax and shipping (e.g. $148.23)
  4. Call GET https://laso.finance/get-card?amount=148.23 via x402 (pays $148.23 USDC from wallet)
  5. Receive a card_id and id_token in the response
  6. Poll GET https://laso.finance/get-card-data?card_id=X with the Bearer token until the card details are ready
  7. Enter the card number, CVV, and expiry on the checkout page
  8. Enter the shipping address and complete the order
The USA prepaid card (/get-card) is U.S. only. Issued in USD, usable at U.S. merchants only, and physical goods must ship to a U.S. address. For international merchants, use the international prepaid card (/order-intl-card) instead.

​
Example: buying from an international merchant

Your agent will:
  1. Navigate to the store and find the sneakers
  2. Add the item to cart and proceed to checkout
  3. Determine the total in JPY and convert to USD (e.g. ¥38,000 ≈ $255)
  4. Call GET https://laso.finance/order-intl-card?amount=255 via x402 (pays $255 × 1.038 ≈ $264.69 USDC from wallet). The order is queued for admin fulfillment
  5. Poll GET https://laso.finance/get-card-data?card_type=Non-Reloadable%20International with the Bearer token. Until an admin fulfills the order (typically within 24 hours), the card’s status is queued. Once fulfilled, status becomes ready and card_details is populated
  6. Enter the card number, CVV, and expiry on the checkout page
  7. Enter the shipping address and complete the order
International card orders are queued. They take up to 24 hours for an admin to fulfill, unlike the instant USA card. Only use the international card when the USA card won’t work (non-U.S. merchant or non-USD currency). If you change your mind while queued, call POST https://laso.finance/cancel-intl-order with the card_id to cancel and refund the charge back to your account balance.
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.