Sending assets
How to create a transfer out of an Account on Ledger Enterprise: recipient, amount, fees, notes, and approving it.
Role: Operators.
Sending is a Request. You complete the form, approve it with your own key, and the transfer executes once your governance is satisfied.
Start the transfer
From the Accounts list, use the Send action on the Account's row.
From the Account page, use the Send action at the top.
Either way the form opens with the Account already set.
Choose the recipient
What you may enter depends on the Whitelists attached to your Account's send Rules.
Every send Rule has a Whitelist
Pick a whitelisted destination. You cannot type a free address
Only some send Rules have a Whitelist
Pick a whitelisted destination, or type an address
No send Rule has a Whitelist
Type an address
Where more than one Whitelist applies, the picker shows which Whitelist each destination belongs to. That matters, because the Whitelist a destination comes from can determine which Rule your transfer falls under, and therefore who approves it.
The form checks the address format for the network as you type. When you select Review, the transaction is screened against sanctions lists. The screening applies to every recipient, whitelisted or typed. A sanctioned recipient blocks the transfer with the message "Keeping you safe: the transaction to this address cannot be processed."
Important: A whitelisted destination expresses governance intent, that this counterparty is permitted. It is not a statement that the destination is safe. Verify a new counterparty's address through a channel other than the one that sent it to you.
Recommended practice: before the first large transfer to a new address, send a small test amount. Then ask the counterparty to confirm receipt. The test transfer is a separate Request, with its own approvals and its own fee.
Set the amount
The amount field opens in the asset, or in the currency you used last. It shows the countervalue beneath. Where the asset has a price, a switch lets you type the countervalue instead. The value is preserved when you switch.
An amount above the available balance, or an amount plus fee above it, is handled in one of two ways:
No other approval is needed, or no Rule matches. It is an error, and it blocks the Request. The form shows "Amount exceeds your available balance" or "Not enough balance to cover amount plus fee". On a token Account, the fee is checked against the parent Account: "Fee exceeds parent account's available balance".
Other approvals are needed. The amount shows as a warning. When you select Review, the Insufficient funds dialog opens. Select Proceed anyway to continue. The transaction fails to broadcast if the funds are still insufficient at the final approval.
These errors also block the Request:
The amount falls outside every send Rule that applies to you, so no Rule authorizes it. The form shows "No matching rule found for the given amount and recipient"
The fee could not be retrieved
On Bitcoin, the amount is below the minimum that the network relays. See Bitcoin
When the amount is valid the form names the matching Rule. That Rule states how many approvals this transfer needs.
Check the fee
The fee is estimated when both the amount and the recipient are entered. It is estimated again when either one changes. It shows in both the network's asset and the countervalue. On Bitcoin and Ethereum, a refresh button next to the fee estimates it again on request.
The figure is a maximum, the ceiling authorized for this transfer, not a prediction. The network usually takes less and the difference is not deducted. If the network needs more than the ceiling at execution, the transfer fails with a fee error rather than silently costing more. A native TRX transfer is the exception: it carries no fee ceiling.
Only Bitcoin and the EVM networks offer a choice of speed: Normal, Fast, Urgent or Custom. See Transaction fees and Networks.
Transaction Check
On Ethereum and EVM Accounts, Transaction Check screens the transfer for risk before you create the Request. Where it does not apply, the form shows no Transaction Check result. Transaction Check also screens contract interactions, Ethereum staking transactions and dapp transactions.
The check starts when the recipient, the amount and the fee are complete. While it runs, the form shows Checking this transaction… under the fee, and Review is unavailable. A change to the recipient, the amount or the fee starts a new check.
No issue
BENIGN
The recipient is not flagged as a risky address
Nothing more is asked
Risk
RISK
The risk-screening provider flagged this transaction as risky
The Risk detected dialog opens
Threat
THREAT
The risk-screening provider flagged this transaction as a likely threat
The Threat detected dialog opens
Unverified
UNAVAILABLE
The security check could not complete, with Retry
The Transaction Check unavailable dialog opens
The result can also show the provider's message, and a Full report link to the provider's report.
A dialog for a flagged or unverified result has Full report, Cancel and Proceed. Select Proceed to continue to your Ledger device. Select Cancel to stop. No Request is created.
When more than one warning applies to a transfer, the dialogs open in this order:
Similar transaction already submitted
Insufficient funds
The Transaction Check dialog
What the platform enforces
The Request records the result that you accepted. The platform checks the transaction again when it creates the Request. If the new result is worse than the one you accepted, the Request ends Failed (FAILED).
The platform checks the transaction once more just before signature. If this check stops the transaction, its failure reason reads "The transaction was stopped by a security check." Nothing is signed or broadcast.
Each Approver sees the result from creation, and must acknowledge a flagged or unverified result before the device step. See Requests and approvals.
Where the results appear
The Request details and the operation details show a Transaction checks section. Its title gives the latest result, for example Transaction checks (Risk). It has one row for each check: At creation and Pre-signature re-check. When the second result is worse than the first, the title starts with Transaction checks: escalated.
Over the API
An API user can set maxAllowedRiskLevel on a transaction Request on Ethereum and EVM networks. It takes one of the API values above. If the check at creation gives a worse result, the Request ends FAILED. Without the field, the check at creation never stops the Request. Other networks refuse the field. See the API documentation.
Add a note
Optional, up to 1,000 characters in the interface, visible to everyone who reviews the Request. The note is the only context an Approver sees on the Request. State what the payment is for, and the internal reference it settles.
Approve the transfer
When the form is valid, select Review. In the interface, the transfer's details appear on your Ledger device and you confirm them there. An API user signs the Request instead.
If yours is the only approval required, the confirmation reads "All approvers have reviewed the request, it will be processed shortly."
If others must approve, the confirmation states how many approvals remain.
In both cases, Copy link to request copies a link to the Request. Closing the confirmation returns you to where you started.
If something blocks the transfer
The Send action is disabled, with a tooltip that names the condition, when:
The Account has no available balance
The Account has a pending edit Request: "You cannot perform transactions while this account has a pending edit request."
No send Rule on the Account lets you send: "You don't have the permission to send"
A pending transaction Request on the same Account does not block a new transfer. When you select Review, the form checks this Account for a send with the same recipient and amount. If one is still in progress, or was confirmed in the last 24 hours, the warning Similar transaction already submitted opens. Select Submit anyway to continue.
Note: The device display is the authoritative one, not the browser. See The security model.
Related
Last updated