Scam safety for seniors starts with the request

A scam does not have to look obvious to be dangerous. The safer first move is to pause when someone asks for money, gift cards, cryptocurrency, a wire, a payment app transfer, a one-time code, a password, remote access, personal information, secrecy, or urgent action.

Judge the request before arguing about the story. A real bank warning, family emergency, government notice, package issue, refund, prize, romance, or tech-support problem should still be verifiable through a known number, official app, statement, card, saved contact, or trusted second person.

Government fraud data shows why the pause matters. FTC and FBI IC3 reporting systems do not measure the same universe, and reported losses are not the same as total losses. But both show that older adults report large fraud losses, especially when pressure turns into fast payment, account access, or identity exposure.

Focus on what they want you to do

Scams can sound like love, help, authority, technical support, a family emergency, a bank warning, a prize, a tax problem, or an investment opportunity. The story may be emotional enough that arguing about it turns into a fight.

A better question is simpler: what are they asking for?

If the answer is money, a code, a password, a download, remote access, private documents, secrecy, or a move to another app, slow the situation down before anything changes hands.

Verify outside the contact

Do not use the phone number, link, QR code, attachment, reply thread, pop-up, or caller ID inside the suspicious contact to prove it is real.

Use a known number, official website, saved app, bill, statement, Medicare card, bank card, or trusted contact.

• If a caller says a bank account is in danger, hang up and call the number on the card or statement.
• If a text says a package, toll, account, or payment needs action, open the real app or website yourself.
• If a government message threatens arrest, lost benefits, or immediate payment, verify through the official agency.
• If a family member sounds panicked, call that person or another trusted relative using a number already saved in your contacts.

Caller ID is not proof. SSA OIG warns that scammers can spoof official numbers and use names, fake documents, or official-looking messages.

Slow down payments that are hard to unwind

A request for gift cards, cryptocurrency, a wire, Zelle, a payment app, bank transfer, prepaid card, gold, cash pickup, or mailed cash should stop the conversation until it is independently checked.

Gift cards are the clearest rule: gift cards are for gifts, not taxes, bank problems, tech support, family emergencies, romance requests, prizes, refunds, or account protection.

Bank impersonation can sound calm and professional. If someone says to move money to a safe account, reverse a transfer, keep a fraud case secret, or run a test transaction, call the bank through a known number and ask the bank to check the account directly.

Keep strangers away from screens, codes, and accounts

Tech support scams often start with a fake Microsoft, Apple, antivirus, internet provider, or security pop-up. They can also start with a phone call, fake invoice, renewal notice, refund offer, or search result that leads to a fake support number.

Do not install remote-access software, share a screen, read a code, or open online banking because of a pop-up, caller, invoice, or refund message.

If support is needed, contact the device maker, software company, internet provider, a trusted local technician, or a family helper through a known channel.

Use a second person for relationship and family-emergency pressure

Some scams build trust before they ask for anything. A romance, friendship, celebrity account, military story, travel problem, medical emergency, customs issue, business opportunity, or crypto investment can feel personal long before it becomes financial.

A relationship becomes higher risk when the other person asks for money, gift cards, crypto, bank help, account access, documents, secrecy, or a move to another app.

Family emergency calls deserve the same pause. FTC guidance warns that voice cloning can make a caller sound like a loved one. Call the relative or another trusted person using a number already saved in your contacts. A real emergency can survive a verification call.

Protect personal information and benefits

Some sensitive information is normal in legitimate settings. A doctor, bank, insurer, tax preparer, government agency, or benefits office may need information at the right time. The source and timing matter.

Pause before sharing Social Security numbers, Medicare numbers, bank details, card numbers, passwords, one-time codes, ID images, tax forms, account screenshots, recovery links, or direct deposit forms.

For accounts, start with email, banking, phone carrier, Apple, Google, Microsoft, Social Security, Medicare, and payment accounts. Use unique passwords, stronger sign-in protection where available, software updates, and recovery settings that respect the older adult's consent and independence.

Talk about the request, not the person

Do not lead with "You are being scammed." That can make someone feel embarrassed, judged, or controlled.

Start with the request: what are they asking you to send, buy, click, install, share, keep secret, or move?

Offer to verify together. Call the known bank number. Open the official account. Look up the real agency website. Contact the family member who supposedly needs help. Ask the platform or provider through its real support channel.

If the emotional story feels real to them, acknowledge that. A person can care about someone and still pause before sending money or private information.

What to save if something feels wrong

Save details without continuing the conversation. The goal is to keep enough information for a bank, payment provider, platform, agency, police department, or trusted helper to understand what happened.

• Phone numbers, caller names, company names, emails, usernames, profile links, and websites.
• Texts, emails, voicemails, letters, social messages, screenshots, pop-ups, QR codes, and invoices.
• Payment requests, gift card receipts, transaction IDs, wire details, wallet addresses, payment app records, and bank alerts.
• Dates and times of calls, messages, payments, account alerts, remote access, or requests.
• A plain note about what was requested and what was shared or paid, if anything.