☞ 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.
Sell integration overview
The Sell integration lets users sell crypto assets for fiat currency directly inside Ledger Wallet. As a Sell provider, you handle the order, payout, and compliance; Ledger handles the secure transaction signing on the user’s device and the embedded LiveApp experience.
To become a native Sell provider, you need to deliver three things:
- Backend API: adapt your API to the Ledger Sell specification. Each sell order is secured with a cryptographic payload and signature: your backend generates a structured binary payload, signs it with your private key, and sends both to Ledger. You must also share your public key with Ledger so signatures can be verified.
- LiveApp: a web application that loads inside Ledger Wallet. It uses the Ledger Exchange Services Kit alongside the Wallet API to initiate and track sell orders. The LiveApp receives the quote the user entered in the wallet as query parameters, so the user lands directly on a pre-filled sell flow. You also need to write or update your manifest and follow Ledger’s UX requirements.
- Testing and submission: test the full integration end-to-end using Developer Mode in Ledger Wallet, then submit your API, manifest, and public key for Ledger review.
Each component can be worked on in parallel. The integration only goes live once all three have passed review.
What to read next
- Architecture — flow overview showing how the components interact
- Backend — the API endpoints, payload format, signature scheme, and key-pair requirements
- LiveApp — LiveApp URL format, manifest requirements, Exchange Services Kit usage, and UX guidelines
- Test & Submit — how to test end-to-end with Developer Mode and submit for review
- Code examples — payload generation and encoding examples in multiple languages
