|reply to rradina |
said by rradina:Bill payments at banks can be reversed even months after they have been executed.
If bank web sites don't already have this feature, add a configurable maximum bill pay amount or when the amount is over say, $500, ask the customer to enter the amount twice. However, a configurable limit is probably safer because the customer may have assumed the decimal was automatic like some ATMs/calculators.
I know because I work at a bank and the I had to learn the grunt work before assuming my position.
Heck I still do it for my clients from time to time, it's faster to do it myself than ask a teller. Though I don't know the real technical aspects behind it, I just send a detailed request to a huge back office and a few days later the client is refunded. It never ever fails (Unless you entered the wrong information in the request submission).
So ya... no need for those safeties. It would be unreasonable to ask programmers to pre-set limits on certain types of bills. 500$ is a lot for TV/Phone/Internet, but very little for a monthly credit card bill.
I work on a public web site for a large corporation. It's not unreasonable to allow the customer to set a configurable limit. In fact, it's no trouble at all and would likely pay for itself in mitigating customer service issues before they are issues.
What you describe is a reactive solution to the problem. I suggest a proactive solution and I believe it's a heckuva lot smarter than cleaning a mess after it's been created.
Reversing a payment to a biller might actually cause them to charge you some kind of a processing fee.