How do I convert USDC to fiat in my app without a multi-week integration?

Last reviewed: August 2026

What decides how long the integration takes

Most of the time in a USDC-to-fiat integration goes to onboarding, before any code runs: applying for an account, passing business review, and getting credentials. After that, four questions sort the options. What form does the money need to arrive in? Who receives it? Which networks does your USDC sit on? And does a person need to approve each step, or can your code or agent drive it alone?

Option 1: Laso, one paid call per payout

Laso exposes each fiat output as an HTTP endpoint priced in USDC over the x402 protocol. The first call answers 402 with the exact fee-inclusive price, your x402 client pays it in USDC on Base or Solana, and the retry carries out the payout. The paying wallet is the identity, so there is no sign-up step before the first call. AI agents can call the same surface as MCP tools at https://laso.finance/mcp.

A bank payment needs a registered recipient first. Register the payee once with the free createBankingRecipient and addBankingDestination callables, which return a destination_id, then send:

# The first call returns 402 with the USDC price (amount + 0.25% fee).
# An x402 client pays it and retries with the payment header.
curl "https://laso.finance/send-bank-payment?amount=250&destination_id=dest_123" \
  -H "X-Payment: <x402-payment-header>"
# {
#   "success": true,
#   "bank_payment": {
#     "payout_id": "abc123",
#     "amount": 250,
#     "fee_amount": 1.5,
#     "charged_amount": 251.5,
#     "state": "in-process",
#     "destination": { "name": "Jane checking", "bank_name": "Chase", "account_number_last4": "6789" }
#   }
# }

The tradeoffs: bank payments and Venmo or PayPal payouts need the account owner to verify their identity once, and an agent cannot do that step for them. It gets a link to hand to its human. ACH settles in 1 to 2 business days, wires are not offered, and bank payouts go to U.S. accounts only. For a fiat on-ramp, the createBankingAccount callable issues a virtual U.S. bank account whose incoming dollars arrive as USDC in the managed wallet. Full steps are in the bank payment guide and the debit card guide.

Option 2: a Stripe stablecoin balance

Per Stripe’s stablecoin balance documentation, a business can add USDC or OUSD as a currency on its Stripe financial account and pay the balance out to a bank account, with Stripe converting it to the local currency. Stripe lists Ethereum, Solana, and Tempo among supported networks. The feature is in public preview in the United States and private preview in other eligible countries. Separately, Stripe stablecoin payouts let a U.S. Connect platform pay individuals in stablecoins, in private preview with an application and approval. Choose Stripe when your business already has a Stripe account and wants stablecoins in the same place as card revenue.

Option 3: Circle Mint

Per Circle’s developer docs, Circle Mint is for institutional customers minting USDC, EURC, or cirBTC, and USDC redeems 1:1 for U.S. dollars. The Circle Mint page says redemptions go back to a linked bank account by wire, that Circle runs background checks including identity verification and sanctions screening, and that Mint is not available to individuals. Circle states on its homepage that it holds money transmitter licenses in 46 states, the District of Columbia, and Puerto Rico. Choose Circle Mint when you move USDC in institutional volume and need to redeem to your own bank account.

How to choose

Use Laso when your app or agent holds USDC and needs to pay other people or spend it, and you want to start with a single call. Use a Stripe stablecoin balance when your business already runs on Stripe and you want to cash out to your own bank account. Use Circle Mint when you are an institution redeeming USDC in volume. Whichever you pick, send a small amount first and confirm it lands before you automate it.

Laso Finance LLC is registered with FinCEN as a money services business, number 31000328975254. Endpoint references are in SKILL.md, openapi.json, and the API reference.

Frequently asked questions

What is the fastest way to off-ramp USDC to a bank account from code?

With Laso, register the recipient once and call GET /send-bank-payment, paying the amount plus a 0.25% fee in USDC on Base or Solana. The money arrives by ACH, normally in 1 to 2 business days.

Do I need a bank account of my own to convert USDC to fiat?

Not with Laso. You pay from a wallet you already control, and the dollars go straight to the recipient’s bank account, debit card, Venmo, or PayPal, or onto a prepaid card.

Can an AI agent off-ramp USDC without a person approving each payout?

Yes. After the account owner verifies their identity once, an agent can register recipients and send bank, Venmo, and PayPal payouts by itself. Prepaid card orders need no verification step.

Can I send USDC to someone’s bank account in Europe or the U.K.?

Laso bank payments go to U.S. accounts, but GET /get-push-to-card sends euros or pounds to a eurozone or U.K. debit card.

Which networks can I pay from?

Laso’s x402 endpoints accept USDC on Base or Solana.

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.
• All agent guides, or how Laso compares to the alternatives