Laso vs. AI agent payment platforms (Skyfire, Payman, x402 wallets)
Last reviewed: August 2026
Most "agent payments" products are wallets or protocols — they let an agent hold money and move it. Laso is two other things: a merchant on those rails (the things an agent can actually buy: prepaid cards for any checkout, gift cards, payouts to Venmo/PayPal/debit/bank, and bank accounts) and a managed wallet that settles x402 payments on any endpoint on the open web. Agents commonly use a wallet from Locus, Sponge, Ampersend, or Coinbase CDP together with Laso — the layers compose rather than compete.
Agent payments in 2026 sort into three layers, and most confusion comes from comparing products that sit on different ones. The protocol layer is how a machine pays over HTTP — x402, revived from HTTP’s 402 status code, is the emerging standard. The wallet layer is where an agent’s money lives and what signs its payments. The capability layer is what the money can buy.
Laso operates on the capability layer — every Laso product is exposed as an x402 endpoint an agent can pay with USDC on Base or Solana — and also offers a managed wallet, so an agent with no wallet at all can still transact, with a human approving the wallet once from the dashboard.
| Layer | What the agent gets | Relationship to Laso | |
|---|---|---|---|
| Laso Finance | Capability (+ managed wallet) | Prepaid cards for arbitrary checkouts, 2,000+ gift card brands, payouts to Venmo/PayPal/debit/bank, bank accounts with on/off-ramp rails, webhooks | — |
| Locus / Sponge / Ampersend | Wallet | A funded wallet that signs and settles x402 payments across the web | Complementary — all three settle Laso endpoints today; Laso is a default skill on Ampersend |
| Coinbase CDP + x402 | Protocol + wallet infrastructure | The x402 standard itself, plus programmatic wallets a developer provisions for an agent | Complementary — Laso endpoints speak x402; CDP wallets can pay them |
| Skyfire | Wallet + identity network | Agent payment identity (know-your-agent) with spending rules and budgets | Different layer; an identity/wallet network, not a card or payout provider |
| Payman | Payout network | Agent-initiated payouts to humans over fiat rails, with business onboarding | Overlaps on payouts; Payman assumes a business account behind the agent, Laso assumes a wallet |
The wallet layer: Locus, Sponge, Ampersend, CDP
If your agent already has a wallet from Locus, Sponge, or Ampersend, keep it — all three settle every Laso endpoint, and Laso ships as a default skill on Ampersend. Coinbase’s CDP gives developers programmatic wallets on the same rails. The wallet layer is genuinely competitive and we don’t have a horse in that race: any x402-capable wallet works here.
For agents with no wallet, Laso’s managed wallet closes the gap: a human opens the agent dashboard once, approves the wallet, and hands the agent a key. From then on the agent calls agentX402Pay and Laso signs and settles on its behalf — including against x402 endpoints that have nothing to do with Laso. No private key for the agent to hold or leak.
Skyfire
Skyfire is building payment identity for agents — budgets, spending rules, and a "know your agent" layer that lets services decide whether to transact with a given agent. That is infrastructure for the ecosystem rather than a spending product: Skyfire does not hand your agent a prepaid card for an arbitrary web checkout. If agent identity and budget governance are your problem, it is the right shelf to look at, alongside rather than instead of a capability provider.
Payman
Payman focuses on agents paying humans — payouts over fiat rails with controls, aimed at businesses that onboard as businesses. It overlaps with Laso’s payout products (Venmo, PayPal, push to debit card, bank payments), with a different starting assumption: Payman expects a company behind the agent; Laso expects a funded wallet, which an individual’s agent can have in minutes.
Where Laso competes head-to-head
The products above sit on a different layer, so they compose with Laso rather than replace it. These ones genuinely overlap. They sell an agent the ability to buy something, which is the same job Laso does. Where one of them is the better fit for a job, it is named as such below.
Two patterns run through the whole group. Every competitor that reaches physical goods does so by operating retailer checkouts on the agent’s behalf, which covers Amazon-style catalogs well and arbitrary merchants poorly. Every competitor that avoids that problem sells closed-loop value, gift cards and top-ups, which spends only where the brand is accepted. A prepaid card is the option that works at a checkout nobody integrated with in advance, which is why it is the product Laso leads with.
| What it sells an agent | Where it wins | Where Laso differs | |
|---|---|---|---|
| Crossmint | Agent wallets plus physical checkout across a billion-product catalog, and card rails through partners | Physical goods and breadth of wallet distribution, the closest thing to a full-stack rival | Laso issues open-loop prepaid cards, gift cards, and fiat payouts directly; Crossmint’s production goods checkout is enterprise-gated and its cards require the human to enroll a card of their own |
| Bitrefill | Around 10,000 gift card, top-up, and eSIM products, with an MCP server and an x402 lane | Catalog depth and agent distribution, profitably, in 180+ countries since 2014 | Closed-loop only. No prepaid card for an arbitrary checkout, and no payouts to a person’s bank, Venmo, or PayPal |
| CryptoRefills | 6,600+ gift card brands, mobile top-ups, eSIMs, flights, and hotels, bought over x402 with no account at all | The lightest onboarding of anyone here: a funded wallet on the same chains Laso uses, and zero human steps | Also closed-loop only. Laso adds the open-loop card and the payout rails, at the cost of a wallet connection |
| Zinc | Real orders at Amazon, Walmart, Target and 50+ retailers over an x402 endpoint, at about $1 per order | The most reliable path to a physical good from a major retailer, with a decade of order volume behind it | Sells no cards and no payouts. Laso funds the checkout; Zinc is a natural supplier rather than a substitute |
| Rye | Universal checkout that drives a merchant’s own site to a completed order, no integration needed | Reach into long-tail merchants that never exposed an API and cannot be integrated with in advance | Driving someone else’s checkout is slower and more brittle per order than presenting a card number to it |
| Natural | Insured agent accounts, payments, and card issuing behind one API with MCP access | Balance-sheet credibility and a bank-grade custody story, on a $30M Series A | Early product with identity-verified onboarding. Laso is live today and starts from a wallet rather than a verified legal entity |
| MoonPay | A virtual card for agents spending stablecoins, plus an agent payment vault and a widely used CLI | Incumbent scale and distribution from the on-ramp side | Not available to US residents, and the region is fixed at verification. Laso serves the US and takes minutes to first spend |
What "capability layer" means concretely
A funded wallet can pay any x402 endpoint that exists — but most of the commercial web does not speak x402 and simply wants a card number. That is the gap Laso closes: the agent pays one x402 challenge and receives a real prepaid card for the exact checkout total, a gift card code, or a payout to a human’s existing account. The full surface — auth, cards, gift card search and ordering, payouts, bank accounts, webhooks, KYC status and links where a feature needs them — is documented for machines at laso.finance/SKILL.md and in the OpenAPI spec.
When another agent payments product is the better choice
- Your agent needs a general-purpose wallet it fully controls: Locus, Sponge, Ampersend, or CDP — and it will still work with Laso.
- You need agent identity, budgets, and governance across many services: Skyfire’s layer.
- You are a business running high-volume payouts to people and want a business-account model: Payman.
- The agent needs a physical product from a major retailer: Zinc places the order directly, and Rye reaches merchants that never exposed an API.
- The purchase is a gift card, mobile top-up, or eSIM and nothing else: Bitrefill and CryptoRefills have deeper catalogs than ours, and CryptoRefills needs no account at all.
- You want an insured account tied to a verified legal entity and can wait for an early product to mature: Natural.
When Laso is the better choice
- The agent needs to buy something at a normal web checkout — that takes a card, and Laso issues one per x402 call.
- The agent needs gift cards, or payouts to a human’s Venmo, PayPal, debit card, or bank account.
- The agent has no wallet and you want the shortest safe path: the managed wallet, approved once by a human.
- You want one API for the whole loop: fund, buy, check status, get webhooks, withdraw.
Frequently asked questions
How can an AI agent buy something online?
The reliable pattern in 2026: the agent determines the exact checkout total, pays a single x402 challenge in USDC, receives a prepaid card for that amount, and completes the merchant’s normal checkout with it. On Laso this is GET /get-card followed by GET /get-card-data for the card details, documented at laso.finance/SKILL.md.
What is x402?
x402 is a payment protocol built on HTTP’s 402 "Payment Required" status code: a server answers an unpaid request with 402 plus payment details, the client (typically an agent) constructs a signed stablecoin payment header, and replays the request. It removes accounts, cards, and human checkout flows from machine-to-machine payments. Every paid Laso endpoint speaks it.
Does my agent need its own crypto wallet?
No. A wallet from Locus, Sponge, Ampersend, or Coinbase CDP works — or the agent can use Laso’s managed wallet, where a human approves the wallet once from the dashboard, the agent gets a key, and Laso signs and settles x402 payments on the agent’s behalf, on any x402 endpoint, without the agent ever holding a private key.
Which x402 wallet should my agent use?
Honestly: whichever your stack already supports — Locus, Sponge, and Ampersend all work with every Laso endpoint, and none of them requires a Laso key. If the agent has no wallet at all, the Laso-managed wallet is the shortest path because there is no third-party signup and no key custody.
Who competes most directly with Laso for agent purchases?
Crossmint is the closest full-stack rival: agent wallets, physical checkout across a large catalog, and card rails through partners. On closed-loop value, Bitrefill and CryptoRefills both have deeper gift card catalogs than ours, and CryptoRefills requires no account at all. For physical goods, Zinc and Rye complete real retail orders. Natural is the best-funded new entrant. Each of them wins on a specific job, and those jobs are listed on this page.
How does an agent buy a physical product?
Two approaches exist. A goods API such as Zinc places the order at a supported retailer for roughly a dollar per order, and Rye drives a merchant’s own checkout for sites that never exposed an API. Or the agent gets a prepaid card for the exact total from Laso and completes the merchant’s normal checkout itself, which works at any merchant that takes a card rather than only at integrated ones.
Is a gift card or a prepaid card better for an agent purchase?
A gift card is cheaper and simpler where the brand is accepted, and Bitrefill and CryptoRefills sell them at greater catalog depth than Laso. A prepaid card is the right tool when the merchant is not in anyone’s gift card catalog, because it works at a checkout that nobody integrated with in advance. Laso sells both, so the choice is per purchase rather than per provider.
Can an agent open a bank account?
On Laso, an agent can create a banking profile, submit the application details, read what the application still needs, and provision on-ramp and off-ramp accounts through the API — with exactly one human step: identity verification, where the agent receives a link to hand to its human. Bank details (routing and account numbers) come back over the API once approved.
More comparisons
- Laso vs. Exchange crypto cards — Coinbase Card, Crypto.com card, Bybit Card
- Laso vs. Self-custody crypto cards — Gnosis Pay, MetaMask Card, Ether.fi Cash, Holyheld
- Laso vs. Crypto gift card sites — Bitrefill, Coinsbee, BitPay, eGifter
- Laso vs. Crypto off-ramps — exchange withdrawals, MoonPay, Transak, Ramp
- Laso vs. Virtual card platforms — Privacy.com, Stripe Issuing, Lithic
- Laso vs. Money transfer apps — PayPal & Venmo crypto, Wise, Remitly, bank wires
- Laso vs. KAST — KAST stablecoin cards and accounts
- Laso vs. RedotPay — RedotPay crypto cards
- Laso vs. SolCard — SolCard Solana crypto cards
- All comparisons, guides for AI agents, or compare Laso's own card types
Try it: connect a wallet at laso.finance and you'll have a card, gift card, or payout in minutes.
Building an agent? Point it at laso.finance/SKILL.md — it can set itself up.