Ledger Wallet integrations

☞ The renaming of “Ledger Live” to “Ledger Wallet” and “wallet” (in the hardware sense) to “signer” is still in progress. This page may contain legacy references that will be updated.

Ledger Wallet is the companion application through which users manage accounts, exchange assets, and interact with third-party services, all secured by their Ledger device. This section of the documentation gathers every path available to integrate a project with Ledger Wallet. Which path applies to you depends on what you are integrating and how deeply it needs to sit inside the wallet.

Choosing an integration path

If you provide a blockchain or a coin and want users to hold, send, and receive it from the “Accounts” section of Ledger Wallet, you need an Accounts integration. This is the deepest form of integration: it requires a Ledger device application, a coin module in the Ledger Wallet monorepo, and a signed agreement with Ledger before development starts, because it involves shipping code that runs on the device itself.

If you provide an application or a service that users should be able to open from within Ledger Wallet, such as a dApp, a Live App, or any tool that needs read or write access to the user’s accounts, you need a Discover integration using the dApp Browser or the Wallet API. This path does not require a Ledger device application: your app runs as a web application loaded inside Ledger Wallet and communicates with the user’s accounts through the Wallet API.

If you are an exchange, on-ramp, or card provider and want to offer swap, sell, buy, or card services directly inside Ledger Wallet, you need an Exchange provider integration. This path combines a backend that implements Ledger’s exchange specification with, in most cases, a Live App for the user-facing flow.

Ledger Wallet integrations

Choosing an integration path

What to read next