MMoney Problem Solver™
Sample cases
Sample caseFictional example written to demonstrate the format. Not advice about a real situation, and not one of your problems.
Scam

Suspicious bank text message

Resolved

Text claiming a blocked card, with a shortened link and a request to confirm a debit card number.

Problem-Solving Engine

Step 7 of 7

Track — How do I keep a record?

  1. Identify — complete
  2. Verify — complete
  3. Understand — complete
  4. Compare — complete
  5. Protect — complete
  6. Act — complete
  7. Track — current

The bottom line

Banks do not ask for a full card number or a one-time code by text. Treat this as an attempt to collect your details, and verify only by calling the number printed on your card.

3

Red flags

0

Options

3/3

Steps done

Part 1

Your action plan

  1. Do this first

    Do not tap the link or reply

    Completed

  2. Then do this

    Call the number printed on the back of your card to confirm account status

    Completed

  3. Then do this

    Report the message to your bank and delete it

    Completed

Part 2

Red flags and risks

  • Requests a one-time passcode, which a real bank never does.
  • Uses a shortened link in place of the bank's domain.
  • Creates urgency about a blocked card.

Part 3

What we know

  • The message asks for a card number and a one-time code.
  • The link does not use the bank's own domain.

Part 4

Still needs verifying

  • Whether there is any genuine hold on the account — confirmed only by calling the number on the card.

Part 5

Questions to ask

  1. 1.Is there an actual hold on my account? (Ask the bank, using the number on your card.)

What the customer told us

Show
Channel
SMS
Requested
Card number and one-time code
Link
Shortened URL, not the bank's domain
Money sent
None

Documents (example)

  • Screenshot of message

Have a problem like this?

Start a problem