---
title: "Wallet"
date: 2026-04-06
author: "Olga Tarasova"
categories:
  - name: "Expertise"
    url: "https://metalamp.io/expertise.md"
---

# Wallet

# Crypto wallet   
for your business

 We design and build crypto wallets for managing digital assets: custodial and non-custodial solutions with user-friendly interfaces and a strong focus on security.

 [Get a consultation](#modal_for_form_without_textarea)

 
## Types of wallets and their differences

 In general, crypto wallets are divided into two types: custodial and non-custodial. The key difference is simple: it depends on who controls the private keys and, accordingly, access to the funds. We can develop either of these solutions.

 
### Non-custodial

 This is a wallet where private keys are held by the user, and the service has no control over them. This setup gives users full control, but it also has downsides: if the seed phrase or key is lost, access usually cannot be recovered.

 
- ### Mobile

 It’s a mobile app wallet. Convenient for daily operations.
- ### Web wallets

 These type of wallets work through a browser or extension. They are often used for dApps.
- ### Desktop

 Installed on a computer, suitable for more «work-focused» scenarios and better environment control.

 
### Custodial

 This is a wallet where users’ private keys are managed by a third party (for example, a platform or service). The advantage is that it’s easy to use, these wallets also have options for account recovery and user support. The downside is that the user is dependent on the rules and reliability of the custodian.

 
- ### Exchange wallets

 Wallets within an exchange or broker, where keys are stored on the platform’s side.
- ### Custodial platform (product-level)

 Wallets that are integrated into your service, where keys and operations are managed by your infrastructure or a custody provider.

 
## Features that are important to think through during development

 The feature set depends on the type of wallet (custodial or non-custodial) and the product scenarios. Below are the components that are usually built into the wallet architecture from the very beginning.

 ![](https://metalamp.io/images/wallet/functions-icon-wallet.svg) 
### Sending / receiving funds

 Core wallet operations: getting an address, sending funds, estimating fees, and tracking transaction status until final confirmation.

 ![](https://metalamp.io/images/wallet/functions-icon-swap.svg) 
### Swap

 Built-in token exchange through an aggregator or DEX: route selection, preliminary rate and fee calculation, trade confirmation.

 ![](https://metalamp.io/images/wallet/functions-icon-chart.svg) 
### Price chart

 Displaying asset prices and performance: charts, notifications, and simple analytics. Helps the user understand what is happening with their balance and the market.

 ![](https://metalamp.io/images/wallet/functions-icon-chains.svg) 
### Multichain solution

 Multiple blockchain networks support: adding networks, handling fees, addresses, and transaction nonces. Start with the required feature set and expand further.

 ![](https://metalamp.io/images/wallet/functions-icon-tokens.svg) 
### Support for any tokens

 Display of tokens and stablecoins: balances, icons, allowlists, and protection against fake assets. A separate viewing mode can be added for NFTs.

 ![](https://metalamp.io/images/wallet/functions-icon-api.svg) 
### API for crypto exchange integration

 Integration with exchange APIs for market data, deposits, withdrawals, or trading (if needed). Configure API keys, access permissions, and secure limits.

 ![](https://metalamp.io/images/wallet/functions-icon-devices.svg) 
### Cross-platform / cross-browser

 Unified UX across web and mobile: consistent flows, stable performance on different devices and browsers, data synchronization, and minimal fragmentation.

 ![](https://metalamp.io/images/wallet/functions-icon-wallet.svg) 
### Sending / receiving funds

 Core wallet operations: getting an address, sending funds, estimating fees, and tracking transaction status until final confirmation.

 ![](https://metalamp.io/images/wallet/functions-icon-swap.svg) 
### Swap

 Built-in token exchange through an aggregator or DEX: route selection, preliminary rate and fee calculation, trade confirmation.

 ![](https://metalamp.io/images/wallet/functions-icon-chart.svg) 
### Price chart

 Displaying asset prices and performance: charts, notifications, and simple analytics. Helps the user understand what is happening with their balance and the market.

 ![](https://metalamp.io/images/wallet/functions-icon-chains.svg) 
### Multichain solution

 Multiple blockchain networks support: adding networks, handling fees, addresses, and transaction nonces. Start with the required feature set and expand further.

 ![](https://metalamp.io/images/wallet/functions-icon-tokens.svg) 
### Support for any tokens

 Display of tokens and stablecoins: balances, icons, allowlists, and protection against fake assets. A separate viewing mode can be added for NFTs.

 ![](https://metalamp.io/images/wallet/functions-icon-api.svg) 
### API for crypto exchange integration

 Integration with exchange APIs for market data, deposits, withdrawals, or trading (if needed). Configure API keys, access permissions, and secure limits.

 ![](https://metalamp.io/images/wallet/functions-icon-devices.svg) 
### Cross-platform / cross-browser

 Unified UX across web and mobile: consistent flows, stable performance on different devices and browsers, data synchronization, and minimal fragmentation.

 
## What we deliver for business clients

 What we deliver for business clients

 
- ### Custody model and security

 We define who controls the keys and how access is managed: custodial or non-custodial model. This affects account recovery, risk profile, and requirements for protecting keys and operations.
- ### On-ramp and off-ramp

 We integrate crypto purchase and sale for fiat directly into your product: no unnecessary steps and with a clear UX. Integration is usually done through a provider that handles part of the procedures and compliance checks.
- ### Transaction flow

 We set up the full transaction lifecycle: signing, sending, fees, statuses, and history. It’s important that both the user and the operations team can always see what happened andcheck the operation status.
- ### Operational control

 For custodial scenarios, we add manageability: roles, limits, withdrawal rules, monitoring, and support processes. This turns the wallet into a tool that can be safely operated without deep onboarding.
- ### Compliance and KYC/AML

 If the product includes fiat rails or off-ramp, KYC checks and anti-fraud requirements are almost always required. We design this at the level of flows and integrations so that compliance doesn’t break the product after launch.
- ### Monetization and UX

 We’ll develop an exchange module with the ability to set custom fees and account for income in financial accounting. We’ll also implement gas-free transactions for users to lower the entry barrier and improve the user experience.

 **We design and develop a wallet tailored to your business model.** From a «universal wallet for everything» to a product-specific setup: who holds the keys, who signs transactions, how funds move, and where control and support are handled.

 [Free consultation](https://calendly.com/iana-g/30min)

 
## Our cases

 [See all cases](https://metalamp.io/cases)

 
## MetaLamp Magazine

 Expertise is our strong suit. Our articles frequently make it to the top rankings. You can also find our insights in [MetaLamp Magazine](https://metalamp.io/magazine), on our [Telegram channel](https://t.me/+kOQ34KeP7XU4ZWQy) and [X (formerly Twitter)](https://twitter.com/MetaLamp_Web3)

 
## FAQ

 
- ### What is the difference between a custodial and a non-custodial wallet?

 In a **custodial** wallet, the service (provider/platform) manages the keys. In a **non-custodial** wallet, the keys are held by the user, and the service cannot recover access for them.
- ### What to choose: custodial or non-custodial?

 If you need account recovery, user support, and controlled operations, a **custodial** model is usually the best option. If you want full user control and dApp scenarios, go with a **non-custodial** one. In practice, the choice depends on product requirements and compliance.
- ### Is it possible to enable login via email/socials without a seed phrase?

 Yes. This is usually called **embedded wallets**: the wallet "lives" inside your application, and the user logs in using familiar methods (email/social). The keys can be managed using approaches like MPC/AA to remove the seed phrase from onboarding.
- ### What is a smart-contract wallet and Account Abstraction (ERC-4337)?

 Account Abstraction (ERC-4337) allows replacing standard EOAs with smart accounts controlled by smart contract logic. This enables features like gas fee sponsorship, multisig, social recovery, and transaction limits. This approach is the foundation of smart-contract wallets and provides a Web2-like UX in Web3 applications.
- ### What is multisig and why does business need it?

 **Multisig** is a wallet where multiple signatures are required to execute a transaction (for example, 2-of-3). It is commonly used for corporate funds, treasuries, funds management, and scenarios where control and separation of responsibility are important.
- ### What are on-ramp and off-ramp, and can they be integrated into a wallet?

 **On-ramp/off-ramp** are services that allow users to buy crypto with fiat and convert crypto back to fiat. They can be integrated into a wallet via providers, but requirements heavily depend on jurisdiction and compliance.
