For FNB Development Team: When a card is placed on hold as a fraud prevention measure, the legitimate card-holder has no access to their account and thus this should only be done when a reasonable concern is raised. A single online purchase for $39 does not qualify as unusual activity, no matter where the vendor may be physically located. I would like to convey two things to you: 1) Please examine why the card in question was placed on hold after this single attempt at an online purchase; 2) Please provide some sort of real-time ability to approve a purchase by the card holder using their phone number on file. This can be an automated call with "1 for yes", for example. It is a very serious concern that a card might be placed on hold during an emergency when being used to deal with that emergency, and nobody is answering the phone at customer service due to the hour. I want to convey to you the sense of looming panic I feel due to FNB constantly holding our debit cards for what have got to be normal card use. I also suspect this is going to be a real manpower issue as your customer service people become swamped with calls questioning this practice. As a software professional myself, I know that our job is to automate human practices, not to increase the human workload. A faultily tuned flagging algorithm runs that risk, and certainly my circumstance renders your flagging algorithm suspect. And I have no doubt that many more cardholders are suffering from this practice. Your obvious objective is to reduce chargebacks, as the current practice clearly protects FNB at the expense and inconvenience of the card holder. I ask that this feedback be routed in such a way that these issues can be considered at the technical and business level. Thank you, Walt Bennett
My home page. That's Kali.