Innomerc One useful thing to do today
Check bank activity directly, not through a screenshot sent by another person.
More everyday safety lessonsChoose your depth. Learn at your own pace.
Understand it
Use your bank’s official app or a saved, verified address. Before approving a transfer, read the recipient and amount on the bank’s own confirmation screen. A familiar name in a message is not enough.
Treat requests to move money to a “safe account” as a reason to stop and call the bank independently. If money or account details were sent to a scammer, contact the provider promptly and ask what can be blocked, recalled or disputed. Recovery is not guaranteed.
Under the hood
A user can authenticate correctly while being deceived about the purpose of a transfer. Transaction authorization and login authentication are different checks. A receipt screenshot is not proof that funds arrived; verify within the receiving account.
Practitioner perspective
Design payment approvals to show meaningful transaction details and use independent verification for beneficiary changes. Review new recipients, recovery changes and unusual flows together. Avoid training that treats successful MFA as proof that a transfer was informed or legitimate.
Watch it work
A fictional, simplified model. Select a component to inspect it, or follow the steps in order.
Where do your card details go?
Compare an unexpected request with a payment you chose. All details are fictional; never enter real payment information here.
A refund story can conceal an attempt to obtain payment information.
How to use this example
Select Next step to read at your own pace, or Animate step to watch one exchange. Nothing advances until you choose.
What it means
Everyday example
State in this scenario
Inspect components & read every step
- You
The person making the decision in this fictional example.
Example: You decide whether to share information, approve a request or check it first.
- Unknown caller
Someone contacting you whose identity you have not independently checked. A familiar name on the screen is not proof of who is calling.
Example: A caller says they are from your bank and asks for a photo of your card. End the call and use a contact route you already trust.
- Verified checkout
The payment process for a purchase you deliberately chose through a merchant you checked. A padlock alone does not prove a seller is honest.
Example: You open a known shop yourself and pay for the item you selected. This differs from sending a card photo to a caller.
- Your bank
The institution that manages your account or issued your card. Contact it using its official app or a known number.
Example: If you shared card details, contact the issuer promptly to discuss blocking the card and reviewing transactions.
Unexpected caller
A refund story can conceal an attempt to obtain payment information.
- Unknown caller You: Refund claim. An unknown caller requests a photo of your card.
- You Unknown caller: Card photo. Sending both sides exposes payment details to the caller.
- Unknown caller Your bank: Payment attempt. The caller may attempt a payment; additional checks vary.
Purchase you chose
Only submit necessary payment details through a verified checkout for an intended purchase.
- You Verified checkout: Chosen purchase. You checked the seller and chose this purchase.
- Verified checkout Your bank: Payment request. The payment provider routes an authorization request to the issuer.
- Your bank You: Check details. If challenged, read the bank’s stated amount, payee and action.
- You Your bank: Your decision. Approve only an action you started and understand.
- Your bank Verified checkout: Payment result. The issuer returns a result; the seller’s honesty is a separate matter.
Already shared details
Contact the actual issuer promptly; a card lock and recovery options depend on the provider.
- You Your bank: Report exposure. Use the official app or number on your card, not the caller’s number.
- Your bank You: Protect + review. Discuss locking, replacement and any transactions needing review.
- You Your bank: Activity checked. Provide transaction references through the verified support route.
Fictional teaching trace. One moving dot represents an exchange, not a measured network capture.
Open the detailed lesson walkthrough
Explore the system
Alarm
A caller claims savings are at risk.
Read every step without animation
Caller directs payment
- Alarm. A caller claims savings are at risk.
- New recipient. The caller supplies an account.
- Transfer approved. Money is sent to that recipient.
The security story concealed an outgoing payment.
Bank contacted directly
- Stop transfer. Do not approve under pressure.
- Known number. Call through the bank’s app or card.
- Account reviewed. The real provider checks the activity.
Independent contact is more useful than debating the caller.
What could go wrong
A caller uses fear of fraud to persuade a customer to authorize a real outgoing transfer.
What you can do
- Check bank activity directly, not through a screenshot sent by another person.
- Use the issuer’s official fraud channel; preserve transaction references and messages privately.
Common mistakes
- Banks do not need you to move money to a stranger’s account to make it safe.
- A successful code check does not make the payment’s purpose legitimate.
Check your understanding
Active recall: explain this idea in 30 seconds
Use your bank’s official app or a saved, verified address. Before approving a transfer, read the recipient and amount on the bank’s own confirmation screen. A familiar name in a message is not enough.
Now give an example and name one limitation. Revisit the explanation if you get stuck.
Primary sources
Original explanations informed by these specifications and official resources. Source versions and lesson review are separate from product updates.
- FTC: What to do if you were scammed
- FTC: Verification codes and impersonation
- FTC: Tech support scams
Content reviewed 2026-09-10. Read the editorial policy.