---
title: "What is crypto wallet integration? A developer's guide"
seoTitle: "What is crypto wallet integration? A developer's guide"
description: "Crypto wallet integration adds wallets, key custody, signing, and compliance to an app. The six components, three integration models, and cost drivers."
date: "2026-08-17"
updated: "2026-08-17"
category: "stablecoins"
author: "BlindPay Team"
faq:
  - q: "What is crypto wallet integration?"
    a: "Crypto wallet integration adds blockchain wallet functions to an existing app: creating or linking wallets, controlling the private keys, signing transactions, tracking balances, and screening transfers. Most teams plug in a wallet provider through a wallet API, an embedded SDK, or a white-label app instead of building key management themselves."
  - q: "What are the main components of a wallet integration?"
    a: "Six components: key management, chain connectivity through RPC nodes, transaction signing under policies you define, balance and transaction monitoring, compliance hooks such as address screening, and the user interface. A wallet provider usually covers the first four. Compliance decisions and the interface stay with your team, even when vendors supply parts of them."
  - q: "Do I need a license to add crypto wallets to my app?"
    a: "It depends on the custody model and the country. In the US, FinCEN's 2019 guidance treats hosted wallet providers that store and transmit value for users as money transmitters, while a person using an unhosted wallet for their own purchases is not one. Working with a registered provider can change your exposure. Confirm your setup with counsel."
  - q: "Which blockchains should a wallet integration support first?"
    a: "Start with the networks your first customers and counterparties already use, and keep the first release to one or two chains. Each extra chain adds an address format, a fee model, confirmation logic, and test coverage. Ask your first ten customers which network and stablecoin they hold today, and build for that."
  - q: "Can I add stablecoin payments without building a wallet?"
    a: "Yes. A payments API with virtual accounts and payouts can convert bank deposits into stablecoins, deliver them to a wallet, and pay out to bank accounts. The customer can use a wallet they already have, or a managed wallet the provider custodies. A wallet still exists somewhere in the flow. You just don't have to build it."
  - q: "Does BlindPay provide crypto wallets?"
    a: "BlindPay is the payments layer, not a wallet provider. It links a customer's existing wallet to payins and payouts without holding its keys, and offers managed wallets in beta for teams that want BlindPay to custody the balance. For key management at scale, BlindPay works alongside wallet infrastructure providers such as Fireblocks, Circle, and Privy."
---

Crypto wallet integration is the work of adding blockchain wallet functions to a product you already run: creating or connecting wallets, deciding who holds the private keys, signing transactions, reading balances, and screening transfers before they move. Most teams don't build this layer themselves. They plug in a wallet provider through an API, an embedded SDK, or a white-label app.

This guide is for developers and product managers at the start of that project. It assumes you know REST APIs and webhooks, and not much about blockchains.

## What is crypto wallet integration?

Crypto wallet integration connects your application to wallets on one or more blockchains, so your users can hold, send, and receive digital assets inside your product. In practice it means wiring four things into your stack: a way to create or link wallets, a way to control their keys, a way to sign and broadcast transactions, and a way to watch what happens on-chain.

A crypto wallet doesn't contain coins. A wallet is a private key plus the public address derived from it. The tokens live on the blockchain's ledger, and whoever controls the private key can move whatever that address holds. That one fact drives most design decisions in a wallet integration: who holds the key, who can sign, and what happens when a key is lost.

For fintech products the asset is usually a stablecoin, a token that tracks a currency like the US dollar. USDC and USDT are the two largest. Stablecoins are tokens issued on existing chains: on Ethereum, Polygon, Base, and Arbitrum they follow the [ERC-20 token standard](https://eips.ethereum.org/EIPS/eip-20), and on Solana, Stellar, and Tron they follow each network's own token model.

## What can a wallet integration do inside a fintech product?

A wallet integration gives a product four capabilities: store a balance, send it, receive it, and convert it to and from local currency. Most fintech use cases combine those four, applied to stablecoins rather than volatile crypto assets.

| Capability | What it means | Example in a product |
| --- | --- | --- |
| Store | Hold a stablecoin balance at a wallet address | A dollar balance for a freelancer in Argentina |
| Send | Sign and broadcast a transfer to another address | Paying a supplier's wallet in USDT |
| Receive | Detect incoming transfers and credit them | A marketplace collecting USDC from buyers |
| Convert | Turn bank money into stablecoins and back | Payroll funded by ACH, paid out over Pix |

The fourth capability is the one teams underestimate. Converting bank money into stablecoins is called an **on-ramp**. Converting stablecoins back into bank money is called an **off-ramp**. A wallet does neither on its own: it holds tokens and never touches a bank account. On-ramps and off-ramps need banking partners, liquidity, and licenses, which is why they usually come from a separate provider. [What is a stablecoin API](/resources/more/what-is-a-stablecoin-api) explains that layer.

Multi-chain support adds another dimension. The same stablecoin exists on several networks, and each network has its own address format, fees, and confirmation times. A user who sends USDC on Solana to an address your product only watches on Ethereum has sent it somewhere your system will never see. [What happens on-chain in a stablecoin payment](/resources/more/what-happens-on-chain-in-a-stablecoin-payment) walks through what each network does during a transfer.

## What are the main components of a wallet integration?

A wallet integration has six components: key management, chain connectivity, transaction signing, balance and transaction monitoring, compliance hooks, and the user interface. A wallet provider usually covers the first four. Compliance and the interface stay with you, even when a vendor supplies parts of them.

| Component | What it does | Usually provided by |
| --- | --- | --- |
| Key management | Generates, stores, and protects private keys, or splits them into shares | Wallet provider, or the user's own device |
| Chain connectivity | Reads blockchain state and broadcasts transactions through RPC nodes | Wallet provider or a node provider |
| Transaction signing | Produces the signature that authorizes a transfer, under rules you set | Wallet provider, with your policies |
| Balance and transaction monitoring | Tracks balances, incoming transfers, and confirmations, then emits webhooks | Wallet provider or an indexer |
| Compliance hooks | Verifies users, screens wallet addresses, monitors transactions | You, plus compliance vendors |
| User interface | Shows balances, addresses, confirmations, and errors | You |

Three terms from that table, defined once:

- **RPC node**: a server that exposes a blockchain's data and accepts new transactions over an API. Every balance read and every broadcast goes through one.
- **Signing policy**: rules that decide whether a transaction may be signed, such as amount limits, allowlisted destinations, or a second approver.
- **Confirmation**: the point at which a transaction is included in a block. Finality, the point after which it can't be reversed, arrives later on some chains.

Key management is where the risk concentrates. A leaked key means lost funds with no chargeback. A lost key means a balance nobody can move. That's why the custody decision comes before any code.

## What are the three ways to integrate a wallet?

There are three integration models: a wallet API, an embedded wallet SDK, and a white-label wallet. They differ in how much of the product you build yourself, and how much control you keep over keys, user experience, and data.

A **wallet API** is a set of backend endpoints for creating wallets, reading balances, and requesting signatures. Your server calls the provider, and you build every screen. A wallet API gives the most control and takes the most engineering.

An **embedded wallet SDK** is a client library that creates a wallet for each user inside your web or mobile app, often tied to an email, social, or passkey login. The user never installs a separate wallet app. You get prebuilt onboarding and signing flows, with less control over how they look and behave.

A **white-label wallet** is a complete wallet application, branded as yours and run by the provider. A white-label wallet is the fastest route to launch and gives the least control over the product and the roadmap.

| | Wallet API | Embedded SDK | White-label |
| --- | --- | --- | --- |
| Control | Full control of UX and data | Your app, prebuilt wallet flows | Branding and configuration only |
| Speed to launch | Slowest | Middle | Fastest |
| Security responsibility | Shared: you own policies and backend security | Shared: provider owns key flows, you own the app | Mostly the provider |
| Best for | Fintechs with an engineering team and custom flows | Consumer apps that want wallets without wallet apps | Teams testing demand before investing |

Many products mix models: an embedded SDK for end users, and a wallet API for the company's own treasury wallets.

## Who holds the private keys?

Every wallet integration picks a custody model, and there are three. In a **custodial** model the provider or your company holds the keys. In a **non-custodial** model only the user holds them. In an **MPC** model the key is split into shares held by different parties, and no single party can sign alone.

MPC stands for multi-party computation, a family of cryptographic techniques that let several parties produce one valid signature without ever assembling the full key. NIST runs a [Multi-Party Threshold Cryptography project](https://csrc.nist.gov/projects/threshold-cryptography) to standardize these schemes. MPC is a key-management technique more than a custody model: who holds the shares decides whether an MPC wallet is custodial.

The custody choice has legal weight. FinCEN's [2019 guidance on convertible virtual currency](https://www.fincen.gov/resources/statutes-regulations/guidance/application-fincens-regulations-certain-business-models) (FIN-2019-G001) treats hosted wallet providers, which receive, store, and transmit value on behalf of account holders, as money transmitters. A person using an unhosted wallet to buy goods or services for themselves is not one. Rules differ by country, so confirm your model with counsel. [Non-custodial payments explained](/resources/more/non-custodial-payments-explained) covers the same question for payment providers.

## How long does a wallet integration take and what does it cost?

There's no reliable public benchmark for wallet integration timelines or costs, and vendor quotes depend on volume and contract terms. What drives both is predictable, though. Five factors set the scope:

1. **Authentication model.** Tying wallets to your existing login (email, passkeys, social) takes more work than a standalone wallet, and it decides how account recovery works.
2. **Number of chains.** Each chain adds an address format, a fee model, confirmation logic, and test coverage. One or two chains keep the first release small.
3. **Custody choice.** Custodial and MPC setups need signing policies, approval flows, and operating procedures. Non-custodial setups need recovery and support flows for users who lose access.
4. **Compliance scope.** User verification, address screening, transaction monitoring, and the Travel Rule each add an integration and a review queue. Moving money for others also raises the licensing question.
5. **Fiat connectivity.** On-ramps and off-ramps add banking rails, quotes, and payout states on top of the wallet work.

On cost, expect a mix of platform fees, per-wallet or per-transaction fees from the wallet provider, network gas fees on every on-chain transaction, and conversion fees whenever money crosses between bank accounts and stablecoins. Ask each vendor for pricing in writing against your own projected volume. [Build vs buy](/resources/more/build-vs-buy-stablecoin-payments) walks through what the in-house version costs in people and time.

## Where does BlindPay fit?

BlindPay is the payments layer around a wallet, not the wallet itself. It connects wallets to bank accounts: virtual accounts that turn bank deposits into USDC or USDT, on-ramps and off-ramps, live quotes, and payouts to local rails. It works alongside wallet infrastructure providers such as Fireblocks, Circle, Privy, Dfns, and Utila instead of replacing them.

A customer's existing wallet is registered with BlindPay as a [blockchain wallet](/docs/blockchain-wallets), either by signing a message or by submitting the address directly. From there:

- A [virtual account](/resources/more/stablecoin-virtual-accounts-explained) gives the customer US bank details. Each deposit converts to USDC or USDT and settles to the linked wallet, and each deposit is tracked as a payin.
- A payout pulls stablecoins from that wallet only after the customer authorizes the quoted amount, then sends local currency over Pix, SPEI, ACH, RTP, SEPA, SWIFT (POBO/COBO), and other rails. BlindPay never holds the keys to an external wallet, so that payout flow is non-custodial.
- For teams that don't want to run signing, BlindPay also offers managed wallets, in beta, which it custodies on the customer's behalf.

BlindPay is registered with FinCEN as a money services business. It is not a stablecoin issuer, a card acquirer, a consumer wallet app, or a key-management platform. If your main need is key custody for thousands of end users, a wallet infrastructure provider is the right first call, and BlindPay can sit behind it for the bank side.

## Glossary: 8 terms you'll see in every wallet integration

| Term | Plain-language definition |
| --- | --- |
| Private key | The secret number that authorizes transfers from a wallet address |
| Wallet address | The public identifier that receives tokens, derived from the key |
| Custodial wallet | A wallet whose keys a company holds on the user's behalf |
| Non-custodial wallet | A wallet whose keys only the user holds |
| MPC wallet | A wallet whose key is split into shares, so no single party can sign alone |
| Account abstraction | A wallet that is a smart contract with programmable rules; [ERC-4337](https://eips.ethereum.org/EIPS/eip-4337) is the main Ethereum standard |
| On-ramp and off-ramp | Converting bank money into stablecoins, and stablecoins back into bank money |
| KYT | Know your transaction: monitoring transfers and wallet addresses for risk |

## What to do next

Write down three answers before you talk to vendors: which chains and stablecoins you need at launch, who should hold the keys, and whether money has to reach bank accounts. Those three choices narrow the vendor list faster than any feature comparison.

If bank accounts are part of the answer, read [how a stablecoin payment works](/resources/more/how-a-stablecoin-payment-works) end to end. Then open the [blockchain wallet docs](/docs/blockchain-wallets) to see what linking an existing wallet to payins and payouts takes.