[mattbee]

The author does seem to bang on about his "reasonable assumptions" for how much Wells and Apple Pay suck, so he should continue the call! Like he's just too clever to follow the advice he'd give everyone else to hang up and call back.

[mort96]

I didn't read it as explaining why she should continue the call, just why she did continue the call. She's explaining why those things didn't immediately trigger the scam alarm. Nowhere did I see her claim to be too clever to do anything.

I found it an interesting read which details an experience which is far removed from how you expect a scam call to occur. It's interesting to read the signs which should have been alarm bells, but which were dismissed because nobody is perfect all the time.

[mattbee]

The author very kindly addresses my comment in a PS:

I also, admittedly, allowed my cynicism toward my own industry and Wells Fargo to cloud my judgment; I didn't know the first thing about Apple Pay or Google Pay prior to this incident, but I don't have particularly positive experiences or feelings toward either company, and it's extremely common for the process of fixing someone else's mistake on large tech platforms to be nightmarishly convoluted.

Ultimately she did realise & fix her mistake - at some pace - lost nothing, and got an up-close view of a scam in progress.

[spicybright]

I'm honestly surprised he even wrote this if he claims to be an expert.

He literally ignored half of what the rep was saying because he was busy fiddling with the computer, then willingly gave up all his personal information because of the distraction.

You would think an expert would know how to properly use 2 factor auth too. Giving someone the code is exactly how you defeat it.