
Start with the email account that receives your bank's password resets. Give it a unique password and a second sign-in step, and check that you can recover it if your phone is lost. Then look at the bank and payment accounts that depend on that address. The first improvement is often knowing how to reach the bank independently, even if you receive a convincing call or text. This guide walks through setting that up, practicing an account recovery, and responding to a suspicious alert. The FTC phishing guide explains common signals and why to contact an organization using a route you already trust.
Draw a simple account recovery map
Write down the accounts you rely on and the recovery route for each. In a private inventory you might list “main email: trusted device and provider recovery process,” “bank: verified phone number, current mailing address,” and “password manager: emergency instructions stored securely.” Keep the inventory somewhere you can reach without your usual phone. Put actual passwords, backup codes, and recovery keys in a secure place designated for them rather than in this overview. Avoid emailing yourself an unprotected copy of everything you would need to sign in.
| Account or device | What to confirm | A small safe rehearsal |
|---|---|---|
| Main email | Its own password and current recovery choices | Locate the provider's recovery instructions and confirm which devices are signed in. |
| Password manager | You understand the account recovery and export options | Find the recovery instructions without exporting your whole vault or signing out everywhere. |
| Bank and payment apps | A verified way to contact support and current contact details | Find the bank's phone number from its app, your card, or a statement you already trust. |
| Mobile carrier | You understand how to restore service or replace a lost SIM | Find the carrier's official support route and ask about account and number-transfer protections. |
Look for a loop. If your password manager requires a code from your email, and the only place you can find the email password is the locked manager, follow both providers' official recovery guidance and set up a way to break that loop. Test whether you can find the instructions while your phone is put aside. Do this while you still have a working sign-in on a trusted device. You do not need to remove your current methods to rehearse the plan.
Set up separate sign-ins and usable backup methods
If two accounts share a password, start with the email that can reset other logins, then the password manager, bank and payment services. Use a unique password generated by your manager or the service's supported passkey option. A passkey or hardware security key can resist many attempts to trick you into signing in on a lookalike site. Check which of your devices support the method and how you would recover it. Where a provider offers other types of multifactor authentication, choose a method you can use reliably, then keep a recovery route. The NIST authentication guidance explains how phishing resistance works.
Try this before you replace a phone: read the provider's migration and recovery guide while the old device still works, add or verify the new device using the provider's process, and test one ordinary sign-in. Confirm that transaction alerts reach you. Only remove a no-longer-trusted device after you know the replacement and recovery routes work. If you think a device has been stolen, use a trusted device and follow the account provider's lost-device guidance. Contact your bank if a payment method or account access could be affected.
Walk through an unexpected charge alert
Suppose you receive “We blocked a $412 charge” with a prompt to confirm it by following a link. Leave the message unopened or back out of it. Open the bank app you already installed through your usual route, check the account activity and any alerts inside it, and look for a pending charge or an unfamiliar transaction. If you cannot tell what happened, call the bank using a number you independently retrieved. You can say, “I received an alert about a $412 charge. Can you check whether it came from you and tell me what appears on the account?” You do not need to click the alert to do that.
If you recognize the merchant, compare the amount, date, any pending authorization, and the receipt. A merchant label can look different from the name on the storefront, so check your own records. If you do not recognize it or a person on the phone asks you to share a sign-in code, approve an unfamiliar prompt, or transfer money to a “safe” account, end the conversation and reach the bank through the independent route. Use the FTC guidance on unexpected calls about your money as a reminder. For a new request to change a familiar payee's bank details, verify the change with the payee through a known number or prior contact channel before paying.
Use a VPN for the connection it actually covers
HTTPS encrypts the connection to the site you opened. That does not tell you who controls the site: a convincing copy can use HTTPS too. A VPN protects traffic between your device and the VPN provider and changes who you trust along that part of the route. It does not resolve a lookalike domain, undo an approved transfer, or replace account recovery. The FTC public Wi-Fi guide explains how encryption and trusted connections fit together.
If you need to view an account away from home, use an app or bookmark you already know and check what the device has connected to. You can wait or use a connection you control if the network or sign-in screen looks unusual. When comparing managers, check account recovery, supported devices, and whether you can move your data without leaving an unprotected export. If you compare VPNs, check supported devices, the provider's privacy terms, and what happens when the VPN disconnects. NordPass and NordVPN are existing partner offers; these checks also work for any other service you consider.
Make the first ten minutes after a mistake count
If you only opened a link, close the page and avoid entering anything. If you entered a password or code, shared bank details, or approved a payment, contact the bank or service promptly using its verified channel. Say what you shared, when, and what action appeared. Ask what transactions are pending and what account protections or dispute steps apply. If a password was exposed, change it from a trusted device using the real account site, starting with any email that can reset the affected accounts. Review recent sign-ins and recovery settings. Follow the provider's instructions before discarding an existing session you might need for recovery.
Record the timestamps, amounts, payment references, and support case number in a private note. Redact account details if you need to share a screenshot with someone other than the relevant institution. The FTC's reporting site takes U.S. scam reports, and IdentityTheft.gov provides recovery steps when personal details were used. A report is useful evidence; the bank or payment provider is the place to ask about a particular transfer or card charge. Check the account again with the bank's advice and keep your follow-up date with the case notes.