Four products
Stablecoin deposits
Any stablecoin, from any wallet on any supported network, routed and settled
where you want it.
On/off ramps
Bank cards and bank transfers, both directions - fiat in as stablecoin, and
stablecoin out as fiat.
Virtual accounts
Permanent bank details per user. What arrives is converted and settled to a
wallet automatically.
Card issuing
Cards your users spend from a stablecoin balance.
Two ways to integrate
Rheon SDK
The full flow embedded in your product, or standalone. One embed covers every
product it supports.
Rheon API
One key, one error format, your own UI on top. Quotes, payment methods,
statuses, and limits across every product.
How the products work
Stablecoin deposits
For users: choose a stablecoin, connect a wallet, confirm the payment. For you: one integration covering multiple stablecoins, wallets and chains. Under the hood it uses a solver network, cross-chain routing, liquidity and treasury management, external protocols such as Circle CCTP, intent-based execution, and compliance monitoring. See Stablecoin/crypto deposits.On/off ramps with bank cards
For users: pay with a card or Apple Pay on a hosted page, pass 3DS, and receive stablecoin - or send stablecoin and have money land on the card they already hold. Apple Pay is part of this product, on the hosted page or as a native in-app sheet through the API. For you: a handful of calls in each direction, and card details never touch your page or ours, so PCI scope stays out of your product. See On/off ramps with cards.On/off ramps with bank transfers
For users: send a normal transfer in their own currency from their own bank, and stablecoin settles to a wallet - or send stablecoin and get paid into any bank account. For you: two shapes on the way in, permanent details or a one-off deposit with a reference, and nothing is held as fiat at any point. See On-ramp and Off-ramp.Virtual accounts
For users: their own permanent bank details - IBAN, SWIFT, or local rails - that they can pay from any bank, any number of times. For you: money arrives already attributed to one user, converted to the asset you set and settled to the wallet you attached, so there is no matching names on statements. See Virtual accounts.Card issuing
Cards your users spend from a stablecoin balance, taking the outgoing direction a step further than a payout: rather than pushing money to a card they already hold, the user is issued one of their own. See Card issuing.Positioning
Rheon is not only a wallet, bank, processor, bridge, or aggregator. It is a money resolution layer that helps companies accept, convert, route, and settle value across fiat and stablecoin systems.Who it’s for
Money apps: fintechs, wallets, neobanks, exchanges, brokerages, marketplaces, stablecoin apps, and embedded finance platforms.What you can build on
- The deposit widget - the full deposit flow, running at widget.rheon.io.
- The crypto deposit API - quote, transaction, and status, so you can build your own UI on the same rails the widget uses. Quotes work in both directions: fix what the payer spends, or fix what must land.
- The card API - price a card payment, start it, and follow it to settlement, with reference endpoints for currencies, countries, limits, and rates.
- The bank API - virtual accounts with real bank details per user, plus on-ramp and off-ramp over local rails.
- Reference endpoints - countries, currencies, limits, rates, and statuses, so your integration reads coverage at runtime instead of hard-coding it.
- Rheon ID - a user verifies once and that verified result is shared with the payment partner behind whichever rail they use, so nobody verifies twice.
Sandbox
Test every product with no real funds before you go live.
API reference
Every endpoint, with requests and responses.
Coverage
Networks, assets, currencies, and rails.
Integration options
SDK or API - pick the path that fits your product.