Can I move money between Xverse and my bank?

Yes, with the usual crypto caveat: fiat moves through third-party partners (onramps, virtual accounts, exchanges you already use). Onchain moves are peer-to-peer between addresses. Timing, limits, and KYC depend on the route, not on Xverse "approving" your self-custodial coins.

Mental model

Direction What actually happens
Bank → Xverse Fiat goes to a regulated partner; you receive crypto or Cash/stablecoins in your account.
Xverse → bank When Cash Withdraw / Cash Pay is shown for your cohort: USDC→bank via Due (v1 EUR·SEPA + USD·ACH). Also Onramper Sell crypto, or send to an exchange then withdraw fiat. Flag-, region-, and partner-dependent — not promised for everyone.
Address ↔ address Pure onchain transfer. No bank involved.

Xverse does not hold your private keys. Partners still must follow banking and compliance rules for the fiat leg.

Common ways to move bank money into Xverse

1. In-app onramp (card / bank / Apple Pay where offered)

Buy supported assets from inside Xverse. Expect identity checks, purchase limits, and partner fees. Settlement is not instant in every case.

2. Cash Direct Deposit / virtual account (Due — live)

Bank deposit onramp is live: send fiat to a Due virtual account and receive USDC in Xverse Cash (same Due KYC/ToS/account as cashout). Local rails vary by region. This funds the dollar layer; it is not a full replacement payroll bank account in every country.

3. Buy elsewhere, withdraw to Xverse

Buy on an exchange you already trust, then withdraw BTC or stables to the deposit address shown in Xverse. Always match the network (Bitcoin L1 vs the correct L2 / stablecoin network). Wrong network sends are often unrecoverable.

Common ways to move value out toward a bank

1. Cash Withdraw / Cash Pay via Due (feature-flagged; primary in-app Xverse→bank path)

When your cohort sees it in Cash, you can withdraw or send USDC to a bank through Due — the same partner and KYC as Direct Deposit. v1 rails: EUR·SEPA and USD·ACH. Availability depends on feature flag, region, and eligibility; do not treat this as live for every user. Partner fees plus an Xverse markup apply; rates can change — check the live quote in-app.

2. Onramper Sell crypto

Onramper Sell still sits alongside Due cashout. Use it when that surface is offered in your build for selling crypto toward fiat.

3. Send to an exchange, then sell and withdraw fiat

Still a universal fallback worldwide.

  1. Copy your exchange deposit address carefully.
  2. Send from Xverse.
  3. Wait for confirmations.
  4. Sell to local currency on the exchange.
  5. Withdraw to your bank.

4. Peer payment instead of bank

If the recipient accepts BTC, Lightning/Spark, or stablecoins, you can skip the bank entirely.

Sending money to a bank in another country

You can send money globally-ish by combining Due onramp + offramp: deposit fiat into Xverse Cash via Due Direct Deposit (live), then Cash Withdraw / Cash Pay USDC→bank when that path is shown for your cohort (v1: EUR·SEPA + USD·ACH). That combo is how cross-border bank sends work today. It is not a native bank→bank wire product — you fund Cash in USDC, then cash out to a bank on Due's supported rails. Cashout remains feature-flagged by cohort and region.

What to expect (so support tickets stay low)

  • KYC on fiat legs. Your keys stay on your device; partners still ask for identity when moving dollars.
  • Hours and cutoffs. Onchain is 24/7. Bank wires follow banking calendars.
  • Fees. Network fees + partner spreads/fees. This article does not publish a fee table; check the live quote in-app or on the partner site.
  • Limits. Daily and lifetime limits are set by partners and your verification level.
  • Reversibility. Confirmed crypto transfers do not reverse like a bank chargeback.

Safety checklist

  • Verify the address and network before every send.
  • Start with a small test amount on a new route.
  • Bookmark official partner domains; ignore "support" DMs asking for seed phrases.
  • Keep a fiat buffer in a normal bank while you learn the rails.

Next steps