Look behind the login screen
Two applications can show a balance and a send button while using different control models. The useful question is who can authorize movement of the assets and what must happen to recover access. A familiar login experience does not answer either question by itself.
Ethereum.org explains wallets as interfaces for using accounts and authorizing actions. That is different from thinking of the app as a container that physically holds coins. The distinction matters when an app is replaced, a device is lost, or a different interface is used to access the same account.
Ask the product to explain its control model in concrete terms. Identify the person, device, provider or combination of signers involved. Then identify whether that model changes when you use a connected service such as a purchase, conversion or payout.
Different responsibilities, different questions
Self-custodial arrangement
Understand the authorization method you control, how it is backed up and who can change it.
Custodial account
Understand the provider’s account recovery, withdrawal conditions and terms for restricting access.
Neither description tells you the entire risk of a product. A carefully designed self-custodial setup can still be used to approve an unwanted transaction. A convenient custodial interface can still impose withdrawal or access rules that do not fit your needs.
For comparison, Safe’s shared approvals center on several signers, while MetaMask’s recovery guidance explains access arrangements for its wallet. These examples show why a general label should lead to a more detailed setup review.
What self custody does not settle
Control of a wallet does not establish the quality of an asset, the behavior of an issuer, the reliability of a network or the terms of a connected service. Keep those questions separate. Otherwise, a correct statement about the wallet can be mistaken for a promise about everything used through it.
A business stablecoin workflow illustrates this distinction. Bancoli describes bank receipts arriving as stablecoins in its Smart USD Wallet. A business evaluating that flow should consider the receiving method, wallet control, exact stablecoin and eventual payout separately. They are linked stages, but they are not identical products.
Write down the dependencies that your normal transaction requires. Include the destination’s accepted network, any conversion service and the people who must authorize the action. This list is more useful than a broad claim that one custody model removes every outside dependency.
Choose around your operating ability
Consider what you can consistently manage. A technically capable setup is not automatically a practical setup for someone who cannot maintain its backups or review its transactions. Conversely, accepting provider-managed recovery may not suit a team that needs direct control over a shared treasury.
For each candidate, answer three questions: who can act today, who can recover after a loss, and who can change those rules? If the answers are unclear, ask the provider for the exact documentation before funding. Our recovery guide turns the second question into a practical review.
Keep the eventual decision specific. “This fits our two-person approval process on this network” is more useful than “this is the safest wallet.” We do not assign security scores because a documentation comparison cannot establish that claim.
Source documents
Official documentation reviewed November 10, 2026. Product terms and availability can change.