Flows | Developers


Estimated reading time: 3 minutes

High level flow

High level flow

The Exchange Application is an application for Ledger’s devices (Nano S, Nano X and Nano S Plus) that has been developed specifically to manage and secure swap operations (crypto-to-crypto transfer).

The trade between the provider and the user is secured by going through Ledger Live back-end, front-end and the Exchange app installed on the Hardware Wallet. The provider signs the trade data, in order to let the Ledger device (Nano S, S Plus, X or Stax) display it to the user. Since the Ledger device is the single source of truth, the user can trust and sign the transaction on the device, thus allowing the provider to complete the transaction. The provider is accredited by Ledger so that the device can trust the provider data.

Detailed flow

This is a C4 diagram that describe an overview of the exchange during the swap process.

Swap C4 diagram

Although the provider's LiveApp is embedded inside Ledger Live, we describe it as running in a separate environment because it is sandboxed.

Display quote information to user

Quote information flow Details on the quote API needed.

Swap transaction flow

Swap transaction flow

  1. Ledger Live opens the provider’s LiveApp through a deeplink. Example:

    The quoteId sent is the one coming from a previous request to the /quote endpoint of the Provider’s backend. This id is linked to the fromCurrency and toCurrency wanted by the user.

  2. The provider’s LiveApp starts Ledger’s swap process through a call to ExchangeSDK method call: swap.

  3. After asking the user to start the process, Ledger’s Swap Service will call the Provider’s backend to generate and sign the payload. The backend will also returns a swapId, for status tracking purpose.

  4. The Provider’s backend will generate the payload with Ledger’s currency id. This part is important as Ledger’s device only knows Ledger’s referential currency.

  5. The Provider’s backend will sign the payload with its private key. The public part must be previously sent to Ledger and must use secp256k1 curve.

  6. As soon as the user signs the transaction within his Ledger’s device, Ledger Live will broadcast the transaction.

  7. The transactionId is returned in the response of the swap method, called by the LiveApp.

  8. The LiveApp should call back Ledger Live with a deeplink. Example: ledgerlive://swap?status=COMPLETED&swapId=123

Check swap status flow

Check swap status flow

High level architecture

High level architecture

Did you find this page helpful?

How would you improve this page for developers?

What do we need?
Getting Started
Theme Features