How do I send money to someone’s debit card from code?
Last reviewed: August 2026
Call GET /get-push-to-card with an amount and a currency (USD, EUR, or GBP), and pay for the call in USDC over x402. The response returns a redemption_url. The cardholder opens it, enters their own debit card details, and the funds are pushed to the card, so your code never needs a processor account or a card number.
Why this is usually hard
Card payout APIs from payment processors are built for businesses: you open an account, pass an approval, and then integrate their transfer flow. That is the right tool for a company paying thousands of recipients. It is a lot of setup for an agent or a small program that needs to pay one person once.
Send the money
The face value is in the currency you choose, from 10 to 9,541.98. The USDC price is that value converted to USD plus a 4.8% fee, with a minimum fee of 1.50 in the chosen currency. An x402 client library builds the payment header for you; without one, the first call returns a 402 with the exact price.
curl "https://laso.finance/get-push-to-card?amount=100¤cy=EUR" \
-H "X-Payment: <x402-payment-header>"
# {
# "success": true,
# "amount": 100,
# "currency": "EUR",
# "redemption_url": "https://...",
# "note": "The debit card must be tied to a Eurozone bank account."
# }Pass redemption_url to whoever holds the card. The form asks for the sender name, the debit card number, and the cardholder name. The transfer is not complete until that form is submitted, and there is no server-side status to poll for it.
| Currency | Debit card requirement |
|---|---|
USD | U.S. bank account |
EUR | Eurozone bank account |
GBP | U.K. bank account |
Pick the right route
A debit card is not always the best place to land the money. Choose by what the recipient already has.
| You want to pay | Endpoint | Limits and fee |
|---|---|---|
| A debit card (USD, EUR, GBP) | GET /get-push-to-card | 10–9,541.98 face value, 4.8% fee (min 1.50) |
| A Venmo or PayPal account | GET /send-payment (identity verification once) | $5–$1,000, 4.9% fee (min $1.50) |
| A U.S. bank account by ACH | GET /send-bank-payment | $10–$50,000, 0.25% fee (min $1.50) |
| A merchant that takes cards | GET /get-card | $5–$1,000 prepaid card, 0% fee |
If you are a business sending payouts at volume to many recipients, a direct payout API from a payments provider gives you more control over the flow and per-transfer status. Push to card fits one-off payments where nobody wants to set up a processor relationship first.
Full reference: push to debit card, Venmo and PayPal, bank payments, and how x402 works.
Frequently asked questions
Can an AI agent send money to a debit card by itself?
It can start the transfer and pay for it. The transfer completes when someone submits the card details at the redemption_url, which the agent can do with browser access or hand to the cardholder.
Do I need a payment processor account to push money to a card?
No. You pay for the call in USDC on Base or Solana over x402, so there is no processor contract or bank integration to set up.
How do I let the recipient enter their own card number?
Send them the redemption_url. They type their own card details into the form, so the number never passes through your code or your agent’s context.
Which countries can I send to?
USD goes to U.S. debit cards, EUR to Eurozone debit cards, and GBP to U.K. debit cards. The card must be tied to a bank account in that region.
How much does it cost to send money to a debit card?
The face value plus a 4.8% fee, with a minimum fee of 1.50 in the chosen currency. Both are included in the single USDC price of the x402 payment.
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.
- 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.