How do I give my AI agent a card I can top up with USDC?
Last reviewed: August 2026
Use a card product that holds or draws on USDC and lets you add more without replacing the card. MoonPay’s MoonAgents Card spends from a Solana wallet up to an allowance you delegate, for residents of supported regions outside the U.S. The Interlace Agent Card is funded with USDC or USDT and delivered to the agent over MCP, with a $20 lifetime limit per card. A Laso reloadable card holds a balance the agent tops up in USDC from Solana or Base for $5 to $10,000 at a time, and the same card stays open across charges.
What a top-up card needs to do
A single-load prepaid card is spent once and then thrown away. An agent that pays an ad platform, an inference provider, or a monthly plan needs a card number the merchant can keep on file, plus a way to add money to it when a bill is coming. If the agent’s money is USDC, the top-up should also happen in USDC, without a person converting it to dollars first.
The three products below all fund a card from stablecoins. They differ in where the money sits before a purchase, how much one card can spend, and who is eligible to hold one.
Side by side
| Laso reloadable card | MoonPay MoonAgents Card | Interlace Agent Card | |
|---|---|---|---|
| Where the money sits | A card balance held for the account holder at the card issuer | In your own Solana wallet until each purchase. The card spends up to the SPL token allowance you delegate | Deposited on-chain to an address returned when the card is issued |
| Stablecoins accepted | USDC on Solana or Base | USDC and XO on Solana, per MoonPay | USDC and USDT. The tutorial shows Ethereum, Arbitrum, and Base |
| How you add money | GET /fund-card-balance over x402, $5 to $10,000 per top-up, priced at exactly the amount loaded | Re-delegate a larger allowance with the MoonPay CLI (mp card wallet link) | Send stablecoins to the card’s deposit address |
| Spend limit per card | The balance you load. The card stays open across charges until it is spent | The delegated allowance. MoonPay’s example delegates up to 5,000 USDC | A $20 lifetime limit, after which the card is disabled, per Interlace’s tutorial |
| Cards per user | Many. Creating a card is free, and each can be reusable or single-use | One card per user at launch | One active card per user |
| How the agent reaches it | Plain HTTP: x402 routes plus a Bearer token, described in SKILL.md and openapi.json | The MoonPay CLI, which MoonPay says guides you through setup after verification | MCP tools only. Interlace says card details are delivered to the agent exclusively through MCP |
| Human steps | The account holder completes identity verification and enters a one-time code to link the card issuer | Identity verification, which MoonPay calls the only step that requires a person | Registration on the Interlace developer page |
| Who can use it | Account holders who pass verification. Not available to residents of India | Residents of supported regions outside the U.S. MoonPay says U.S. residents are not currently supported | The docs do not state regional limits |
| Getting money back | POST /withdraw-card-balance pays unspent balance out as USDC on Base, usually within 1 to 3 business days | Unspent funds never leave your wallet. Revoke the delegation with mp card wallet unlink | Deleting the card returns the remaining balance to your crypto wallet as stablecoins, per Interlace’s overview |
When MoonPay’s MoonAgents Card is the better fit
Pick MoonAgents if you live in a supported region outside the U.S. and want the USDC to stay in a wallet you control until the moment of purchase. Nothing is pre-loaded onto the card, so there is no balance to withdraw later, and revoking the delegation stops all spending in one on-chain transaction. The tradeoffs are one card per user, Solana only, and a CLI-driven setup.
When the Interlace Agent Card is the better fit
Pick Interlace if your agent already runs on MCP and its purchases are small: a few API credits or a trial subscription. The $20 lifetime limit per card is a hard ceiling on what a misbehaving agent can spend. The same limit rules it out for an ad budget or anything that renews at more than a few dollars a month, and card use is limited to online payments.
When a Laso reloadable card is the better fit
Pick Laso if the agent should keep one card on file with a merchant and refill it itself as bills arrive. Each top-up is a single x402 call paid from Solana or Base, and the card number the merchant saved does not change. The account holder can create several cards against one balance, for example one per merchant, and reads every spend, deposit, and top-up from GET /list-card-transactions. The tradeoffs are that the holder must verify their identity and link the card issuer before the first card, and withdrawals pay out on Base only.
Topping up a Laso card from the agent
Once the account holder has finished setup, the agent can fund, create, and read the card on its own. This example loads $50 from the managed wallet, so the agent never builds a payment header or holds a key.
# 1. Confirm setup. status is not_started, code_sent, linked, or kyc_required
curl "https://laso.finance/get-card-issuer-status" \
-H "Authorization: Bearer $LASO_ID_TOKEN"
# If kyc_required, hand kyc_url to your human
# 2. Top up the card balance with $50 of USDC from the managed wallet
curl https://laso.finance/agentX402Pay \
-H "Authorization: Bearer $LASO_ID_TOKEN" \
-H "Content-Type: application/json" \
-d '{"data":{"userId":"usr_...","route":"fund-card-balance","params":{"amount":50}}}'
# The route answers with a top_up_id, status "paid", and funded_usd
# 3. Create a reusable card against the balance (free)
curl -X POST "https://laso.finance/create-reloadable-card" \
-H "Authorization: Bearer $LASO_ID_TOKEN" \
-H "Content-Type: application/json" \
-d '{"usd_amount": 50}'
# { "card": { "card_id": "...", "last4": "...", "balance": 50, "reusable": true, ... } }
# 4. Read the number, expiry, CVV, and billing address for checkout
curl "https://laso.finance/get-card-data?card_id=$CARD_ID" \
-H "Authorization: Bearer $LASO_ID_TOKEN"
# Later: read balances before the next bill and top up again with step 2
curl "https://laso.finance/get-card-data?card_type=Reloadable" \
-H "Authorization: Bearer $LASO_ID_TOKEN"
An agent with its own x402 wallet can call GET /fund-card-balance?amount=50 directly instead of going through agentX402Pay. A top-up usually reaches the card balance in under a minute; follow it under top_ups in GET /list-card-transactions as it moves from paid to credited. There are no partial approvals, so a charge larger than the balance is declined in full. Every field, the issuer link steps, and withdrawals are in the reloadable card guide.
How to choose
If you are outside the U.S. and want the USDC to stay in your own Solana wallet, use MoonAgents. If the agent makes a handful of small purchases through MCP, the Interlace card caps the damage at $20. If the agent pays the same merchants over and over and should refill its own card, use a Laso reloadable card. For a bill that renews every month, the subscription roundup also covers bank-funded cards from Privacy, Ramp, and Meow. For a single purchase of a known total, a fixed-balance prepaid card needs no setup at all.
Sources
- MoonPay, MoonAgents Card: crypto-funded virtual payment cards
- Interlace, Agent Card overview
- Interlace, Agent Card integration tutorial
Frequently asked questions
How do I refill my AI agent’s card when it runs low?
On Laso, the agent calls GET /fund-card-balance with an amount from $5 to $10,000 and pays in USDC from Solana or Base. The full amount lands on the card balance and the card number stays the same.
Can my AI agent spend USDC at a normal online store?
Yes, through a card funded with USDC. The merchant sees an ordinary card payment, and the agent enters the number, expiry, CVV, and billing address at checkout.
How do I give my agent a card without pre-loading money onto it?
MoonPay’s MoonAgents Card spends from your own Solana wallet up to an allowance you delegate, so funds stay in your wallet until each purchase. It is available to residents of supported regions outside the U.S.
How do I keep an agent card from spending more than a set amount?
Load only what you want it to spend. A Laso reloadable card declines any charge above its balance, the Interlace card stops at $20 for its lifetime, and a MoonAgents card stops at the delegated allowance.
Can I get unspent USDC back off my agent’s card?
On Laso, POST /withdraw-card-balance pays from $2 to $10,000 of the balance out as USDC to a Base wallet you control, usually within 1 to 3 business days.
More guides
- How to give your AI agent a credit card — An AI agent cannot pass credit underwriting, but it can issue itself a virtual prepaid card over an API in about a minute. The working pattern, with real requests: x402 payment in, card number out.
- x402 vs AP2 vs ACP vs MPP vs UCP: which should your agent use? — All five agent payment protocols compared honestly: x402 and MPP for machine-to-machine HTTP payments, ACP for ChatGPT checkout, UCP for Google surfaces, AP2 for authorization. Which layer each one is, when to use each, and a worked x402 example.
- x402 vs Stripe Issuing for AI agents — Two real ways to put a card in an AI agent’s hands: Stripe Issuing behind a business account, or x402 card issuance the agent drives itself. An honest comparison of onboarding, funding, controls, and when each wins.
- Issue a virtual card with one x402 call — A complete, runnable walkthrough: pay one x402 request in USDC and receive a virtual prepaid card with number, expiry, and CVV. Real endpoints, real response shapes, error handling included.
- How can an AI agent pay for an API call with USDC? — An AI agent pays for an API call with USDC by answering the API’s HTTP 402 challenge with a signed payment. Two ways to do it: your own wallet with an x402 client, or a managed wallet with a price cap and no private key.
- How do I give an AI agent a bank account? — Two real ways to give an AI agent bank details: a business checking account it can operate (Meow) or a U.S. bank account that converts incoming dollars to USDC in the agent’s wallet (Laso). What each one is, who approves what, and when to pick which.
- How do I cap how much my AI agent can spend? — Cap an AI agent’s spending with limits it cannot raise: a funded balance, a per-payment spend limit set by the account owner, a per-call price cap, and prepaid cards loaded with exactly the amount to spend.
- How do I send money to someone’s debit card from code? — Send USD, EUR, or GBP to a debit card with one API call paid in USDC. No payment processor account: you get a redemption link, the cardholder enters their own card details, and the funds are pushed to the card.
- What are the best ways to pay someone on Venmo or PayPal from an AI agent? — Four ways an AI agent can pay a person on Venmo or PayPal: the PayPal Payouts API, a USDC-paid payout through Laso, a bank or card payout instead, or a human approving each payment. Tradeoffs for each.
- How do I let my AI agent buy a gift card through an API? — An AI agent buys a gift card with two calls: search the catalog for a laso_server_id, then order it with a USDC payment. The redemption code comes back in the same response. Includes a runnable example and the currency gotcha.
- How do I let my AI agent buy something online? — Two working ways for an AI agent to buy something online: spend the account holder’s saved card with their approval on each order, or pay for a prepaid card in USDC and check out like any cardholder. How Laso and Crossmint each handle it, with runnable calls.
- How do I send dollars to a bank account from an AI agent? — Pay a U.S. bank account by ACH from an AI agent. Register the recipient once, then make one API call paid in USDC. Limits, fees, settlement time, and a runnable example.
- What are the best ways to give an AI agent its own wallet? — Four ways to give an AI agent a wallet it can spend from: a key you hold yourself, Coinbase Agentic Wallet, Crossmint agent wallets, or a Laso managed wallet. Custody, spend limits, and tradeoffs for each.
- How do I get notified when my AI agent spends money? — Get an alert every time your AI agent spends: register one signed webhook for card orders, payouts, withdrawals and deposits, or poll the balance and card transaction endpoints. Working code included.
- How do I convert USDC to fiat in my app without a multi-week integration? — Three ways to turn USDC into dollars, euros, or pounds from code: Laso pay-per-call payouts over x402, a Stripe stablecoin balance, or Circle Mint redemption. Onboarding, outputs, and tradeoffs for each.
- How do I let my AI agent use my own credit card safely? — Let an AI agent pay with your own card without ever handling the number: save the card once behind a passkey, let the agent build the cart over an API, and approve each order on your own device. Working calls included.
- How do I let my AI agent pay for a subscription that bills every month? — A subscription charges the same card again each month, so a single-use card fails at the first renewal. Four ways to give an AI agent a card that stays open, from Privacy, Ramp, Meow, and Laso, with the calls for a reloadable card funded in USDC.
- How do I move USDC between Solana and Base from an AI agent? — Move USDC between Solana and Base from an AI agent with one HTTP call: no bridge UI, no gas token on either chain, and no private key in the agent. Working curl examples, fees, and timing.
- All agent guides, or how Laso compares to the alternatives
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.