Where Rehive works — and where it's going.
Move money and verify customers across the rails and regions we cover today — one surface over our providers, with coverage that grows corridor by corridor.
Every rail, one surface.
| Method | Region | Currency | Direction |
|---|---|---|---|
01ACH | United States | USD | In · Out |
02Wire | United States | USD | In · Out |
03SEPA | Europe | EUR | In · Out |
04Faster Payments | United Kingdom | GBP | In · Out |
05PIX | Brazil | BRL | In · Out |
06SPEI | Mexico | MXN | In · Out |
07On-chain | Multi-chain | USDC · stablecoins | In · Out |
08Cards | Select markets | USD | Out |
The wallet lives on one chain; the ramps don't. Bank rails and on-chain deposits and withdrawals converge on a USDC or EURC wallet on Base — held by licensed providers like Bridge, or in the customer's own self-custody wallet via Privy.
Bank rails where supported. On-chain everywhere.
Bank rails, where supported
Local on and off-ramps in the corridors we serve today: USD over ACH and wire, EUR over SEPA, GBP over Faster Payments, BRL over PIX, MXN over SPEI. Each ramp lands in the same wallet, mirrored on Rehive's ledger.
On-chain, everywhere
Stablecoin deposits and withdrawals reach across chains and settle into a USDC wallet on Base — so customers outside the bank-rail corridors can still move value in and out.
Verification to match
KYC and KYB onboarding runs across the corridors we serve, with provider-backed checks behind one onboarding flow. Requirements adapt per corridor.
Growing coverage, corridor by corridor.
We'd rather ship a corridor that works end to end than a long list of countries with an asterisk. Here's how the map fills in.
Corridor by corridor
We add coverage deliberately — each new corridor arrives with its rails, its verification requirements and its compliance posture wired in, not just a flag on a map.
One surface throughout
New corridors show up behind the same API and the same wallet applications. Nothing to re-integrate when coverage grows — your integration already speaks every rail we add.
Bring your own provider
Already have a provider relationship in a market we don't cover yet? Plug it into Rehive and extend your own coverage, with our ledger as the record.
If we don't cover it yet, let's talk.
Bring your own provider to extend coverage into a market we don't serve yet, or tell us where you're headed and we'll tell you what's on the roadmap. New corridors land behind the same API you've already integrated.