Start with three questions
- Who can move the funds?. Only the user, the user together with you, or you alone. This decides whether you run a custody service, which licence you need, and what happens if your company or your vendor disappears.
- Is the wallet the product or a feature?. If people choose you for the wallet, you need full control over its experience and roadmap. If the wallet is how your app pays out, receives or stores value, an SDK is enough.
- Which chains and tokens?. One chain and one stablecoin is a different project from ten chains, swaps and NFTs. Most fintech wallets start with USDC or USDT on one or two networks.
When does a white-label wallet fit?
A white-label wallet fits when you need a wallet in front of customers quickly, the wallet is not your core product, and you accept the vendor's roadmap. Typical cases are a bank or broker testing demand, or a company adding a branded wallet for a loyalty or community programme.
The costs show up later. Your users live in the vendor's app, so your data, your support and your brand experience depend on it. Moving users to another wallet means asking every one of them to move funds, or a key migration the vendor has to support. Ask for the exit path in the contract.
When does an embedded wallet fit?
Embedded wallets are SDKs that create a wallet for each user inside your app, usually signed in with an email, a social login or a passkey, with no seed phrase. The key is protected by MPC, by secure enclaves, or by shares split between the user's device and the vendor's service. Most can be configured so the user alone controls the funds, or so your app can sign within limits the user agreed to.
This is the usual choice for fintech and consumer apps that pay out to users, accept stablecoin top-ups, or hold small balances. You control the experience, the vendor runs key management, and good SDKs let users export their key. Check the pricing model carefully: many charge per monthly active wallet, which grows with your success.
When should you build your own?
Build your own wallet product on wallet infrastructure, or on self-hosted MPC, when the wallet is what you sell, when you need policies or chains no SDK supports, or when a regulator or bank partner will not accept a third party in the signing path. Expect to own key ceremonies, recovery, security audits, monitoring, every chain integration and an on-call rotation. Teams that underestimate this usually ship late, not insecure, because the security work is what they cannot skip.
Smart accounts change the trade-off
On Ethereum and its layer-2 networks a wallet can now be a smart contract. ERC-4337 introduced smart accounts with their own validation rules, and EIP-7702, live since the Pectra upgrade in May 2025, lets an ordinary address act as a smart account. That moves rules on-chain:
- Recovery by guardians or a second device, without a seed phrase.
- Spending limits and allowed recipients enforced by the contract.
- Network fees paid by your app or in the stablecoin itself, so users never hold ETH.
- Batching: approve and send in one step.
Smart accounts work only on chains that support them. For USDT on TRON, the most common payout rail in many corridors, you still need a classic key-based wallet, and fee handling works differently: there, renting energy instead of burning TRX is what lowers the cost.
What do you always build yourself?
- Onboarding and identity. Linking the wallet to a verified customer, and proving control of self-hosted wallets where the travel rule asks for it.
- The ledger link. Every deposit and payout booked in your platform's ledger and reconciled against the chain.
- Screening. Checks on incoming funds and outgoing addresses through your KYT provider.
- Recovery and support. What happens when a user loses a device, forgets a login or sends to the wrong network. This is most of your support load.
- Limits and fraud rules. Daily limits, new-address cool-offs and alerts, whatever the vendor offers.
- App store and legal text. Store reviews treat crypto apps strictly; your terms must say who controls the funds.
Questions to ask a wallet vendor
- Who can sign a transaction from a user's wallet: the user alone, you, your vendor, or a combination?
- How does recovery work, and does it ever give the vendor the ability to sign?
- Can users or we export keys, and how has that been tested?
- Which chains, tokens and smart account standards are supported today?
- How is pricing measured: wallets created, monthly active wallets or transactions?
- What happens to users' access to funds if the vendor's service is down or the contract ends?
What have we built?
Our founders built Stablerail, a self-custodial treasury workspace on MPC with approvals and audit records, and Transatron, non-custodial TRON infrastructure for wallets, exchanges and apps. For clients we build wallet features on embedded SDKs and wallet infrastructure, with the ledger link, screening and recovery around them.
FAQ
Q01What is the difference between an embedded wallet and a white-label wallet?
An embedded wallet is an SDK that creates a wallet inside your own app, signed in with email, social login or a passkey. A white-label wallet is a finished wallet app or web wallet that a vendor rebrands for you. Embedded gives you your own product; white-label gives you speed and less control.
Q02Does offering a wallet require a MiCA licence?
It depends on who controls the keys. If you or your vendor can move users' funds, that is usually custody and needs authorisation. If only the user can sign, many non-custodial wallet software providers fall outside MiCA. The design of key recovery often decides which side you are on, so check it with counsel.
Q03Should we build our own wallet from scratch?
Rarely. Building key management, recovery and signing yourself only pays off when the wallet is your core product and you have a security team to run it. Most teams build the product around a wallet SDK or infrastructure API.
Q04What are smart accounts?
Wallets that are smart contracts, so the rules for signing, recovery, spending limits and who pays the network fee live on-chain. ERC-4337 and EIP-7702 brought them to Ethereum and its layer-2 networks.
Sources
Disclosure: Vareger builds on wallet SDKs and infrastructure, including some named here. We receive no fees from any of them; if that changes, we say so on this page.
