Device With PIN or Recovery Card Check | Official Flow, Screen State, and Backup Boundary

A device that arrives with a PIN note or recovery card should be reviewed through the official setup flow and screen state. The central question is whether the user is creating and controlling the backup during setup, not whether a handwritten note looks convenient.

Device with PIN or recovery card check with official flow screen state and backup boundary

PIN and recovery cards should not define setup

Record what the card says without copying private values into the article record. A setup flow should not depend on a PIN or recovery words prepared outside the user's own device workflow.

The recovery phrase explainer is the stable reference for private backup creation and storage.

Device screen should show the actual state

Read the screen before continuing: welcome flow, PIN request, recovery phrase step, update prompt, or connection prompt. If the screen state does not match a fresh setup path, pause and compare it with Ledger Wallet context.

  • Record that a card exists without copying secret values.
  • Compare device state with Ledger Wallet setup context.
  • Keep backup words and PIN values private.

Official flow keeps backup control with the user

The setup path should leave the user in control of backup words and device approval. The Secure Element explainer gives background for why device-side confirmation remains separate from outside notes.

End with setup-state decision points

Close with card presence, device screen, Ledger Wallet context, backup boundary, and final decision. That keeps the article focused on setup state rather than on any sales-channel judgment.