Crypto deposits should happen in your app.
Not in a wallet tutorial, bridge flow, or exchange detour.
depositOS gives product teams one integration for crypto deposits, stablecoin funding, confirmation visibility, and recovery flows. Let users pay from a wallet, exchange, or private path while every deposit settles to the destination you control.
The problem
Deposits are where onchain products lose people
Not at signup, and not at checkout. At the one step where a user has already decided to give you money and the product asks them to go figure out crypto first.
Wrong chain, wrong token
Their funds are on Base. You settle on Arbitrum. They are now reading a bridging tutorial instead of using your product.
No wallet, no deposit
Plenty of people ready to fund have never installed a browser wallet. The funding step assumes one anyway.
The handoff kills momentum
Every redirect to an exchange or bridge is a chance to get distracted and not come back.
The fix
Three ways in. One integration.
However your user holds their money today, the deposit lands in the same place — and your engineers wire it up once.
Connected wallet
Pay from any chain, any token.
The user connects, picks from what they already hold, and routing handles the bridge and swap. They never learn which network your treasury sits on.
Deposit from anywhere
An address. No wallet needed.
Each user gets their own persistent deposit address. They send from an exchange, a custodian, or a phone wallet, and it lands in your account.
Private deposit
Funding without the trail.
For users who would rather their balance not be linked to a public address the moment they fund it.
Coverage
Meet users on the chain they already use
Wallet mode routes 100+ tokens across major EVM networks and Solana. Walletless deposit addresses are live on Ethereum, Arbitrum, Base, and Optimism.
Ethereum
Wallet + address
Arbitrum
Wallet + address
Base
Wallet + address
Optimism
Wallet + address
Solana
Wallet
Polygon
Wallet
BNB Chain
Wallet
Avalanche
Wallet
Integration
An afternoon's work, not a quarter's roadmap
No wallet-vendor account, no bridge contracts to audit, no settlement logic to own. Install, lock the destination, and open it where the intent already is.
npm install @gizmolab/depositos
Built for teams with a compliance review
Control where it matters, flexibility where it doesn't
The destination is yours
Chain, token, and recipient are fixed in config. The user picks how they pay — never where the money lands.
It looks like your product
Theme it to your brand, rename every label, drop the footer. The widget ships its own scoped styles and cannot leak into your CSS.
Attribution built in
Per-app API keys mean volume, deposits, and transactions are already split by product line when finance asks.
Any stack, any framework
A React component, a headless SDK if you want to build the UI yourself, or an iframe and script tag if you are not on React.
Keys stay server-side
Routing and provider credentials live in the API, never in your bundle. Your users' funds never touch a depositOS-held wallet.
Run it your way
Use the hosted API, or point the SDK at your own deployment when procurement needs the data path inside your perimeter.
$1.24M
Volume
3,180
Deposits
2,041
Unique users
Base → Arbitrum
USDC
Solana → Arbitrum
USDC
Exchange → Arbitrum
USDT
Illustrative figures — your portal shows your own.
Who it's for
Anywhere a balance has to get funded
Exchanges & brokerages
Take first deposits from users whose funds are still sitting on a competitor.
Wallets & neobanks
Fund a new account without asking for a seed phrase on day one.
Games & marketplaces
Top up a balance mid-session, in the currency the player already holds.
DeFi & trading apps
Turn a cross-chain balance into usable collateral without leaving the trade screen.
Get started
Take a deposit in your own app today
Create an app in the portal for an API key, or open the playground and watch a real cross-chain deposit settle before you write a line of code.











