Wallet-as-a-service vs non-custodial deposit addresses
Wallet-as-a-service holds keys for your users; non-custodial deposit addresses never hold anything. A clear comparison of the two ways to add wallets to an app.
Last updated: October 12, 2026
Wallet-as-a-service gives each user a managed private key so they can hold and send their own crypto — and puts the weight of key custody on you or your provider. Non-custodial deposit addresses hold no keys: each user gets an address that can only pay out to your wallet, for deposits and top-ups. Choose by one question — do your users need to spend their own balance, or just fund yours?
The core difference: who holds a key
Wallet-as-a-service (WaaS) exists to give end users a real wallet without them managing seed phrases: a key is created and secured for each user, often with MPC or secure hardware, so they can receive, hold and send. That is powerful — and it means keys that belong to other people now exist in your system, with everything that implies for security and liability.
A non-custodial deposit address is the opposite trade. No key is created for the user at all. They get an address that is only a destination; whatever arrives is collected to the single wallet you control, and it can pay out nowhere else. There is nothing to custody, because there is no user key.
| Wallet-as-a-service | Non-custodial deposit addresses | |
|---|---|---|
| User can send/spend | Yes — it is their wallet | No — it is a deposit destination |
| Keys held for users | Yes (managed for them) | None |
| Custody liability | Significant | Minimal — no user keys |
| Best for | User-owned balances, transfers | Deposits, top-ups, collection |
| Funds ultimately go to | The user | A wallet you control |
| Security surface | A store of user keys | No key store to breach |
When wallet-as-a-service is the right tool
Pick WaaS when the product is genuinely about users holding their own crypto: a consumer wallet, a self-custody-style app, peer-to-peer transfers, or anywhere a user expects to send funds out to an address of their choosing. That capability requires a key the user effectively controls, and accepting the responsibility that comes with managing it.
When deposit addresses are the right tool
Pick deposit addresses when money needs to flow to you: funding an in-app balance you track in your own ledger, taking deposits into an exchange or marketplace, collecting payments, or giving each user a standing top-up address. You get the per-user experience without ever becoming the custodian of someone else’s keys — which is the liability most teams are trying to avoid in the first place.
You can combine them
These are not mutually exclusive. Plenty of products use deposit addresses for the money coming in and settling to treasury, and a separate custody solution for any user-spendable balance. The useful discipline is to be deliberate: hold keys only where the product truly requires it, and use non-custodial addresses everywhere you only need to receive.
Frequently asked
What is the difference between wallet-as-a-service and deposit addresses?
Wallet-as-a-service creates and manages a private key for each of your users, so they can hold and send their own crypto — you (or your provider) take on key custody and its liability. Non-custodial deposit addresses hold no keys at all: each user gets an address that can only pay out to your wallet, used for deposits and top-ups. One is for user-owned balances; the other is for collecting funds to you.
Which one do I need?
If your users must custody and spend their own crypto — send to anyone, hold a balance that is theirs — you need real wallets, which means key management (wallet-as-a-service or self-custody). If you just need each user to be able to deposit or top up and have the money reach you, non-custodial deposit addresses do that with far less risk and no key custody.
Is wallet-as-a-service custodial?
Usually, yes, in the sense that keys are generated and managed on the user’s behalf — by you or the provider — even if advanced setups split or secure them with MPC or secure enclaves. That means someone is responsible for those keys. Non-custodial deposit addresses sidestep the question because there is no user key to hold.
Start accepting stablecoins
Non-custodial, no KYC to start, and no infrastructure to run. Register a wallet you control and take your first payment on a test network in minutes.