An order status or customs message should be checked through the known order entry instead of the short path alone. The practical comparison is between the message wording, the order entry, and any Ledger Wallet or device context that appears later.
Short paths should be copied before use
Record the visible path, sender label, requested field, and order context. A short path can be convenient, but the known order entry should be the place where the user confirms what the request is about.
The entry verification checklist helps keep message path, known entry, app state, and local record separate.
Order entry should frame the request
If the message asks for delivery or customs information, compare it with the known order path and only provide information that belongs to that order task. Device approval and backup content stay outside this delivery-message review.
- Record sender label and short path.
- Compare the task from the known order entry.
- Keep recovery phrase and PIN values out of delivery forms.
Device boundaries should not be mixed into delivery messages
When a device task appears, check it separately inside Ledger Wallet and on the device screen. The Clear Signing review checklist is useful when screen wording needs careful reading.
End with an order-message record
Close with message path, order entry, requested field, app context if relevant, and final decision. That keeps the article operational without making broad claims about delivery messages.
