Cowrie Research

laso-finance

3 min read

Laso Finance

  • Name: Laso Finance
  • URL: https://laso.finance/
  • Category: crypto-to-card spending infrastructure / x402 payment-gated prepaid-card and gift-card API / stablecoin spend control plane
  • Tags: ethereum-ecosystem solana-ecosystem
  • Summary: Laso Finance is a small spend-and-redemption control plane, not a card-program anchor. The useful layer is x402-gated access to prepaid cards, gift cards, and push-to-card flows, plus the post-payment fulfillment logic that decides when credentials, card data, and payout steps actually become usable.
  • What it does:
    • Exposes x402 paywalled endpoints that let an agent or app pay in USDC on Base or Solana to obtain auth credentials, order U.S. prepaid cards, order international prepaid cards, buy gift cards, or initiate push-to-card transfers
    • Uses a two-step U.S. card flow where /get-card provisions the card and returns a pending card_id, and /get-card-data is then used to poll until the actual card details are ready
    • Supports a queued international-card workflow with separate cancellation and status-check paths, making the cross-border card product operationally distinct from the instant U.S. flow
    • Provides searchable gift-card catalog endpoints plus order endpoints that return redemption details, codes, or URLs depending on the brand
    • Supports push-to-card flows for USD, EUR, and GBP debit-card destinations, where the API returns a redemption URL that must be completed in a browser to finish the transfer
    • Maintains a broader authenticated operations layer around balances, withdrawals, merchant search, card refresh, auth-link handoff into the web dashboard, and support/help-center documentation
  • Key claims:
    • The agent llms.txt describes Laso Finance as a privacy-maximizing way to spend cryptocurrency and says users can deposit stablecoins and receive prepaid cards, gift cards, or card-based disbursements without the onboarding shape of a traditional card program
    • The OpenAPI spec explicitly says all paywalled routes use the x402 protocol and identifies Base and Solana USDC payment recipients, which is the strongest signal that Laso should be treated as programmable payment-gated spending infrastructure rather than only a consumer web app
    • The OpenAPI and SKILL docs both emphasize that /get-card does not return the card number, CVV, or expiry and that agents must poll /get-card-data until status becomes ready, which shows the product has a real post-payment fulfillment/control-plane layer
    • The AI plugin manifest and SKILL doc jointly show a much broader operating surface than “buy a card”: auth bootstrap, queued international orders, gift-card search and purchase, push-to-card flows, merchant search, and dashboard-link generation
    • The help center exposes separate collections for international users, U.S./CAD users, PayPal/Venmo, deposits, and withdrawals, which is useful evidence that Laso operates a sizable consumer-and-operations support surface beyond a single API endpoint
  • Whitepaper: No canonical standalone Laso Finance whitepaper or litepaper surfaced in this pass. The clearest source of truth was the agent llms.txt, the public OpenAPI spec, the published SKILL doc, the AI plugin manifest, and the help-center corpus; see ../whitepapers/laso-finance-primary-sources-2026-05-03.md.
  • Sources:

Internal linkages

Control surface

  • Practical authority sits in x402 payment-gating, supported settlement rails, card-issuance and fulfillment policy, regional payout coverage, and the authenticated dashboard layer Laso keeps around balances, refreshes, and withdrawals.

  • Treat it as small operator plumbing for spend redemption. The gift-card and prepaid-card menu is packaging, not a new payments rail.

  • Last reviewed: 2026-06-14 UTC

Graph View