She got a call from someone claiming to be Chase saying there was suspicious activity on her account, and everything about it looked real. The caller could send push notifications to her phone. They read off the suspicious charges and her recent transactions accurately. They walked her through what they were doing to block the fraud and delete any accounts created with her information. It sounded like a legitimate bank call, and she gave them her card information.
Then something started feeling off and she told the caller she wanted to hang up and verify by calling the number on the back of her card. The representative pushed back and kept insisting they were really Chase, offered to transfer her to a supervisor, and when she hung up anyway they called back repeatedly, blowing up her phone so aggressively she had to block the number just to free up the line and place her verification call.
💸 Take Back Control of Your Finances in 2025 💸
Get Instant Access to our free mini course
5 DAYS TO A BETTER BUDGET
When she finally reached Chase through the official number and explained what had happened, the representative said they couldn’t immediately see anything unusual but transferred her to the fraud department. The fraud representative started reviewing her recent transactions and mentioned the exact same suspicious charges the original caller had already identified. When she explained that someone claiming to be Chase had already contacted her about those charges and sent push notifications to her phone, the fraud representative said that was unusual because the bank typically doesn’t operate that way.
What the fraud department actually found
The fraud representative dug deeper into the account and found that the suspicious charges had already been blocked before she called. The push notifications she received during the original call were legitimate, not spoofed. There was clear evidence in the system that someone had been actively assisting her account before she picked up the phone to verify. What they couldn’t find was any record of the phone number that had contacted her, which the representative flagged as strange because they would normally be able to trace that information internally.
The number that called her had a 559 area code. When she looked it up afterward it appeared to be associated with a legitimate Chase branch in California. That detail made the whole situation more confusing rather than less, because it meant the number wasn’t obviously fake, and yet Chase’s own fraud team couldn’t locate it in their records.
Why this situation doesn’t fit either explanation cleanly
The two explanations available, legitimate Chase call or sophisticated scam, both have problems when held up against what actually happened. If it was a scam, the scammer had access to her real push notification system, her accurate recent transaction history, and somehow blocked fraudulent charges on her account before the call ended, which would require a level of access to Chase’s internal systems that goes well beyond what most fraud operations can pull off. If it was a legitimate Chase call, the fraud department’s inability to find any record of the number or the interaction is the part that doesn’t add up, because internal calls from bank representatives should be traceable.
The behavior when she tried to hang up is also worth sitting with. A legitimate bank representative verifying suspicious activity has no reason to call back repeatedly and blow up a customer’s phone when that customer says they want to independently verify the call. That’s the kind of pressure tactic that shows up in scam calls, not in standard bank fraud procedures, and it’s the detail she trusted her instincts about in the moment.
What she did right in a confusing situation
The instinct to hang up and call back independently was the right call regardless of who was actually on the line. Legitimate banks don’t discourage customers from verifying calls through official numbers, and any representative who pushes back on that request is waving a flag worth paying attention to. She acted on the discomfort even when the technical details looked real, which is harder to do than it sounds when someone is reading off your actual charges and sending notifications to your phone.
Canceling the card and changing her login credentials after the call was also the right move. Even if the original caller turns out to have been legitimate, she had already given her card information to someone during a call she couldn’t fully verify, and resetting everything removes the risk of that information being used regardless of who had it.
What she’s still dealing with
The outcome was fine in the sense that no fraudulent transactions went through and her account appears secure. But the experience left her anxious and without a clear answer about what actually happened, which is its own kind of unresolved problem. Not knowing whether she talked to her bank or a scammer sophisticated enough to mirror her bank’s systems almost perfectly means she can’t fully make sense of the experience or know what to watch for going forward.
Chase’s fraud department has the phone number and has flagged the interaction. Whether that leads anywhere or produces a clearer explanation for her is another question, but she did everything right by the time the call ended, and the account is in better shape now than it was before any of this started.
Featured on Cents + Purpose: