☞ 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.
Card integration overview
The Card integration lets users buy crypto with a debit or credit card directly inside Ledger Wallet. As a Card provider, you handle the payment processing and order fulfilment; Ledger supplies the secure, device-verified receive address and the embedded LiveApp experience.
To become a native Card provider, you need to deliver three things:
- Backend API: adapt your API to the Ledger Card specification. Each order is secured with a cryptographic payload and signature: your backend generates a structured 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, and keep your private key secure.
- LiveApp: a web application that loads inside Ledger Wallet. It uses the Ledger Exchange Wallet API in addition to the standard Wallet API to handle card purchase flows and transaction signing on the device. 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
- Backend — the API endpoint, payload format, signature scheme, and key-pair requirements
- LiveApp — LiveApp URL format, manifest requirements, Exchange Wallet API 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
