Table of Contents
Send dollars from a bank you already control, then receive native Circle-issued USDC on a named chain. The bank does not mint the token; the on-ramp is the fiat deposit plus the mint or convert.
That is not issuer redemption, and it is not how to off-ramp USDC to ACH or wire. Redemption and cash-out take tokens back to dollars; this page is how dollars become USDC.
Key Takeaways
- On-ramping USD to USDC is a bank send plus a mint or convert, not a deposit of tokens at your bank.
- Use Circle Mint when you can wire 1:1 into a Mint account; everyone else uses a processor or a venue.
- ACH is cheaper and slower; wire is faster and costs more; RTP is near-instant when the bank participates.
- Circle credits USDC 1:1 after the fiat deposit settles, then typically mints on-chain in about 15 minutes.
- Dual-control the Circle beneficiary details before you send the first wire.
- Include the tracking reference unless your linked bank has a virtual account number.
- A returned wire re-credits the sending bank, not a USDC wallet.
- Mark the on-ramp complete only when available USDC balance shows the credit.
What on-ramping USD to USDC is
On-ramping USD to USDC is treasury sending fiat from an operating account and receiving a dollar-pegged token. You still hold bank dollars until a licensed desk, processor, or venue credits native USDC.
It is the funding step before supplier payments. Fund first, then pay the commercial amount in native USDC on a named chain.
Do not treat the bank as a USDC issuer. A routing number and account number send dollars; they do not mint Base USDC.
Three paths to native USDC
You have three workable setups in 2026. Pick the one that matches your KYB and ticket size, not the one with the most chains.
| Path | How dollars become USDC | Which rail you send | Best for |
|---|---|---|---|
| Circle Mint deposit | Circle mints 1:1 into a Mint balance | Fedwire, SWIFT, RTP, SEPA, SPEI, CHATS, PIX, or book; Circle selects | Institutions with a Mint account and recurring treasury size |
| Processor or Stripe | The platform converts USD and delivers USDC to a wallet | Card, ACH, or local rails the platform supports | Teams embedding a checkout or wallet on-ramp |
| Venue ACH-and-convert | You deposit USD, then convert to USDC | ACH for cheap funding; wire when you need speed | Occasional buys below Mint eligibility |
Circle Mint is the institutional 1:1 desk. Circle's deposit-fiat guide only works after you have a Mint account and a linked bank.
A processor is the productized version of the same idea. Stripe's hosted on-ramp sends the customer to a standalone page, and Stripe acts as merchant of record for KYC and the purchase.
A venue is a fiat deposit plus a conversion. The USDC you receive is a trade, not Circle's par mint, which is why spreads and withdrawal holds belong in the quote.
Vendor shopping is a different job. Best stablecoin on/off-ramps compares providers; this page is the treasury workflow once you have picked one.
Pick the rail before you send
The mint is not the delay. ACH, wire, and RTP are different bank networks with different cutoffs, fees, and return rules.
| Rail | What you send | Typical timing | Use it when |
|---|---|---|---|
| ACH | USD debit from a US account | 1–3 business days; some venues quote 3–5 | Recurring funding where cost beats speed |
| Wire (Fedwire or SWIFT) | USD or EUR credit to Circle or the venue | Same day before cutoff, else 1–3 business days | Large or time-sensitive mint |
| RTP | USD credit, 24/7 | Near-instant if the sending bank participates | Same-day operating USDC at RTP banks |
| Circle auto-route | Circle picks the rail for the linked bank | Domestic wire same day before cutoff; on-chain mint typically ~15 minutes after fiat credit | Mint accounts; you do not tick "ACH" on the instruction |
Circle's supported rails are explicit on the last row. Deposits go through the wires endpoint, and Circle routes Fedwire, SWIFT, RTP, SEPA, SPEI, CHATS, or a book transfer from the linked bank.
ACH is still the default US venue rail. A US exchange deposit is usually ACH unless you pay for a wire.
Do not fund Monday payroll off a Friday ACH. Business-day rails do not run on Saturday, and "pending" on Sunday is not USDC on Monday morning.
How to run a Circle Mint deposit
Link the operating bank first. Circle registers the account, issues a destination id, and will not match a wire sent to an unregistered string.
Retrieve the wire instructions for that linked bank. Circle returns the beneficiary name, the routing details, a tracking reference, and, when the settlement bank supports it, a virtual account number unique to you.
When virtualAccountEnabled is true, send to that virtual account number and the memo is optional. When it is false, put the tracking reference in the wire memo or Circle cannot match the deposit.
Confirm the beneficiary name, account number, and routing number character-for-character before the bank releases the wire. Mismatched details cause returns or delays of several business days.
Send the wire from the linked account, not from a new subsidiary or a personal account. Circle attributes the deposit to the registered bank.
Watch status from pending to complete. Complete on the deposit list means Circle has credited the Mint balance; it does not yet mean USDC is sitting in an external wallet.
Circle typically completes on-chain minting in about 15 minutes after the fiat credit. Transfer out only from available balance; unsettled inbound dollars are not USDC yet.
How to run a processor or venue on-ramp
Complete KYB on the company, then attach the same operating account you already use for wires. Treat a new bank source like a vendor-detail change: dual control, then a small test.
For a processor, send the customer or the treasury user to the hosted on-ramp with the destination asset set to native USDC on a named chain. Stripe documents USDC on Ethereum, Solana, Polygon, Avalanche, Base, and Stellar, with regional gaps you have to read before you promise a chain.
For a venue, deposit USD first, then convert to USDC. Do not skip the conversion and assume the bank "sent USDC."
Withdraw only to a wallet you control, on the chain you actually use for supplier payments. A venue credit on the wrong network is not an on-ramp delay; it is a recovery job.
Confirm the token against how to check the official USDC or USDT contract. A ticker match is not the issuer test.
Confirm you actually received native USDC
Broadcast and processor-complete are not received. Received is an available USDC balance that matches amount, date, and official contract.
Store the deposit id, the rail, the source account last-four, the USD amount, the USDC amount, the chain, and the contract in one file. That file is the audit record; the chain explorer is not.
Match it back to the payable or payroll run that needed the tokens. Accepting USDC is a different inbound job; this step is proof the treasury funded itself.
Fees and spreads need a rule before the first mint. If a venue clips $40 off a $50,000 buy, post the difference; do not leave the ledger $40 light.
Returns, fails, and the wrong beneficiary
A failed deposit never left the bank. Check the error, fix the instructions, and send a new wire; do not resend the same unconfirmed details.
A returned wire is different. Circle documents that mismatched beneficiary details can bounce the payment, and the dollars go back to the sending bank, not into a USDC wallet.
ACH returns follow bank rules, not blockchain rules. A protocol USDC transfer does not reverse; a bank debit can.
If you wired the wrong beneficiary, treat it as a misdirected wire, not as a hash you can undo. Freeze further sends to that destination, file the incident, and do not "retry" from the same unconfirmed details.
When not to on-ramp
Skip the mint when you already hold the USDC you need to pay. Converting idle bank dollars and converting them back next week is a round-trip tax on the same funds.
Skip Circle Mint when you are not an institution or cannot pass Mint KYB. The 1:1 desk is not a retail teller, and the deposit guide is the eligibility map.
Skip ACH when the payable must leave today. Use a wire or RTP, or keep a USDC buffer so the mint is not the critical path.
Skip any rail when you cannot staff dual control on beneficiary changes. A substituted account number will cost more than a slow SWIFT payment.
FAQs
Does my bank mint USDC if I send a wire?
No. US banks send dollars over ACH, wire, or RTP; they do not mint Circle-issued USDC.
Send fiat to a licensed desk, processor, or venue, then receive the token.
Is a Coinbase ACH buy the same as Circle Mint?
No. Circle Mint is a 1:1 issuer mint into a linked account after a matched fiat deposit.
A venue buy is a deposit plus a conversion, and the USDC you receive is a trade, not Circle burning or minting against your wire.
How long does a USD on-ramp take?
Circle Mint domestic wires received before cutoff typically settle the same business day, and Circle says on-chain minting then takes about 15 minutes. ACH often takes one to three business days, some venues quote three to five, and RTP can be near-instant at participating banks.
Weekend and cutoff windows sit on the bank leg, not on the chain confirmation.
What if the wire shows sent but Mint has no credit?
Sent means your bank dispatched the fiat. Wait for Circle's deposit list, then call the bank with the tracking reference and beneficiary, because a sent wire can still be returned.
Do not send a second wire until you know whether the first will credit or bounce.
Should I on-ramp everything in the operating account?
Only the cash you must hold as USDC. If the next payable is a bank wire, keep that buffer in the bank and mint the rest.
This content is provided for informational and educational purposes only and does not constitute financial, investment, legal, or tax advice; no material herein should be interpreted as a recommendation, endorsement, or solicitation to buy, sell, or hold any financial instrument, and readers should conduct their own independent research or consult a qualified professional.
){kind=link}