Trezor Safe 3: review a transaction before signing

Share
Physical cryptocurrency tokens lying on white fabric
Contents

At a glance

Use the Safe 3 menu to inspect account and fee information, revisit screens and cancel an unsigned request. Instructions follow firmware 2.13.1 documentation.

Prepare without changing your wallet

This guide is for an already configured Trezor Safe 3 whose navigation matches firmware 2.13.1. The firmware changelog dates that release to November 11, 2026. It is an explanation of the documented interface, checked on November 20, not a report of a new release today or a physical-device test. The goal is to review an existing transaction request and, when necessary, refuse its signature before approval.

Have your device, the Trezor Suite installation you normally use, and the independently obtained payment instructions available. Know which asset, account, recipient and network you intend to use before touching the confirmation controls. Do not create a payment solely to practise this article. If you have no legitimate pending transaction, read the controls first and use them when a real request next requires review.

Trezor says the navigation change does not change wallets, accounts or recovery words. Resetting the device or restoring a backup is therefore not a preparation step for learning the menu. If your screens differ, identify the model and firmware before continuing. [1][2]

Learn the menu before approving anything

On a screen labelled with the menu symbol, press the left button to open the context menu. It shows one item at a time. Read the item name and the counter rather than assuming the first entry is the option you want. Press the right button to advance, the left back control to return, and both buttons together to select the displayed item.

At the first menu item, the left close control exits the menu and returns to the preceding screen. Closing this menu is not the same action as cancelling the signing request. Trezor places cancellation at the end; during transaction or message signing the entry is called Cancel sign.

Verify each navigation action by looking at the new label on the device. A familiar button combination can have a different purpose on another screen. In particular, both buttons select a menu item or confirm certain warnings; they are not the new final transaction-confirmation gesture. [3]

Read the account and fee information

When a legitimate transaction request reaches the device, compare the recipient information with the instructions obtained independently from the intended recipient. Treat the computer display and the device display as separate places to inspect, not as interchangeable evidence. If the intended recipient, account or network is unclear, stop the process and resolve that uncertainty before authorizing anything.

On the recipient screen, open the menu and look for Account info. Select it with both buttons. Read the available account information; the updated interface exposes additional details through menus. Return to the review flow when finished. On the relevant summary screen, open the menu and select Fee info to inspect the fee details.

A fee is the transaction cost shown for that operation; it is not a certificate that the destination is trustworthy. This walkthrough does not prescribe a universal acceptable fee or assume every asset has identical screens. If a value or unit is unfamiliar, cancel and consult the asset-specific instructions rather than confirming to discover what happens. [4]

Go back with Shift instead of guessing

Where the left-button label appears in brackets, Shift provides backward navigation. Hold the left button until its label changes to Shift, keep it held, then press the right button. The documented behaviour is to scroll upward through pages, or return to the preceding screen when already on the first page. Check the resulting page before repeating the gesture.

This is different from a short press of the left menu button. If the label is not bracketed, do not assume Shift is available there. Read the current controls instead of repeatedly pressing buttons from memory. Page counters help distinguish movement within a long display from returning to an earlier step.

Long messages and contract data may span several pages. The menu can offer Confirm without review. For the review task described here, do not use that shortcut: it would skip the inspection you are trying to perform. If you cannot understand the requested action, cancel it. Seeing every page does not by itself establish that a contract interaction is safe. [5]

Cancel signing and verify the result

To refuse a request that has not been approved, open its menu with the left button, move to the final Cancel sign entry and press both buttons to select it. Follow any subsequent on-screen prompt according to its label. The expected outcome is that you leave that signing flow without completing its final approval. Check Trezor Suite for the request outcome before trying again; do not interpret merely closing the menu as successful cancellation.

At the final transaction summary, the new approval gesture is holding the right button for about one second while its progress indicator fills. Do not perform that gesture when your intention is to cancel. A short press, a two-button menu selection and a deliberate hold have different roles.

This cancellation procedure concerns an unsigned request. It is not a way to reverse a payment already signed or broadcast. If approval has already occurred, inspect the transaction state in Suite and use the relevant transaction documentation; repeating Cancel sign on a later request cannot undo the earlier one. [3][6]

Work through a mismatch without sending

Consider a legitimate payment you were already about to make, but the account information on the device is not the account you intended. This is a hypothetical worked example, not a test transaction to create or a real incident. First stop progressing toward the final approval. Open Account info and establish what the device actually displays. If necessary, use Shift where available to revisit the preceding information.

Do not choose a different account blindly on the computer while continuing the old request on the device. Cancel the current signing request through its final menu entry. Verify in Suite that the request was not completed, then resolve which account and recipient instructions are correct. Start a fresh review only if a legitimate payment is still required.

For a simple completion checklist, confirm that you located the account details, located the fee details when offered, understood how to return, and exited the unsigned request without the final approval hold. No transfer is needed to demonstrate understanding of the instructions. [3][4][5]

Troubleshoot different screens and preserve the boundary

If Account info or Fee info is absent, first check whether you are on the recipient, summary or another screen. Menus are contextual. If the whole layout differs, stop and compare your model and firmware with the current official guide. Do not apply Safe 3 button instructions to a touchscreen model merely because both devices belong to the same product family.

Do not enter the bootloader or factory-reset menu to fix a navigation misunderstanding. Trezor documents separate reset confirmation with both buttons, while transaction summaries use the right-button hold. Those exceptions are a reason to read the label on every screen, not to practise reset controls.

The setup tutorial teaches the new controls, but the documentation says Suite cannot currently replay it after setup. Consult the official guide or support instead of resetting to see it again. Keep recovery words private when requesting help. A useful description includes the model, firmware and screen label; it does not require sharing a wallet backup. Recheck this walkthrough when firmware or navigation documentation changes. [6][7]

Evidence & sources

Source record: · Checked:

Record limits · Use the Safe 3 menu to inspect account and fee information, revisit screens and cancel an unsigned request. Instructions follow firmware 2.13.1 documentation.

  1. [1]Source reported

    The navigation change preserves wallet data.

    Supporting excerpt: Trezor Safe 3 navigation guide

    Original quotation

    Your wallet, accounts and recovery words do not change.
    Trezor Safe 3 navigation guide ↗

    Source language: EN · Captured Nov 20, 2026

  2. [2]Source reported

    The release is dated November 11.

    Supporting excerpt: Trezor firmware changelog

    Original quotation

    11 November 2026
    Trezor firmware changelog ↗

    Source language: EN · Captured Nov 20, 2026

  3. [3]Source reported

    Cancellation is the final menu item.

    Supporting excerpt: Trezor Safe 3 navigation guide

    Original quotation

    Cancel is always the final item in the menu.
    Trezor Safe 3 navigation guide ↗

    Source language: EN · Captured Nov 20, 2026

  4. [4]Source reported

    The menu contains fee information.

    Supporting excerpt: Trezor Safe 3 navigation guide

    Original quotation

    Menu ≡ → Fee info
    Trezor Safe 3 navigation guide ↗

    Source language: EN · Captured Nov 20, 2026

  5. [5]Source reported

    Shift requires a bracketed left-button label.

    Supporting excerpt: Trezor Safe 3 navigation guide

    Original quotation

    Shift is available when the left button is shown in brackets: (≡) or (✕).
    Trezor Safe 3 navigation guide ↗

    Source language: EN · Captured Nov 20, 2026

  6. [6]Source reported

    Final confirmation requires holding the right button.

    Supporting excerpt: Trezor Safe 3 navigation guide

    Original quotation

    On these screens, you need to hold the right button for about 1 second.
    Trezor Safe 3 navigation guide ↗

    Source language: EN · Captured Nov 20, 2026

  7. [7]Source reported

    Suite cannot currently replay the setup tutorial.

    Supporting excerpt: Trezor Safe 3 navigation guide

    Original quotation

    Trezor Suite does not yet have an option to repeat it.
    Trezor Safe 3 navigation guide ↗

    Source language: EN · Captured Nov 20, 2026