A customs or additional-information message should be reviewed through the order-entry path, not through the message alone. The useful check is whether the message wording, order context, Ledger Wallet state, and device-screen boundary all make sense together.
Message wording should be copied before acting
Record the sender, visible link text, requested information, and stated order context. Do not treat urgency or familiar branding as the decision point. The next step is to return to the known order or support entry and compare the task from there.
The entry verification checklist helps keep message path, entry path, and local record separate.
Order entry should be the reference point
If the message asks for delivery or customs information, compare it with the known order path and the information already visible there. A Ledger device task normally does not need to be mixed into a delivery-message review.
- Record the message path and requested field.
- Use the known order or support entry for comparison.
- Keep recovery phrase and PIN content outside delivery forms.
Device-screen boundaries remain unchanged
A delivery message may mention timing or documents, but device approval is still reviewed on the hardware screen when a device task exists. The Clear Signing review checklist gives a separate screen-reading reference when wording must be compared.
Keep the record narrow and practical
Close the check with message sender, requested field, order entry, Ledger Wallet context if relevant, and final decision. That gives the reader a stable process without turning delivery messages into broad claims about channels.
