Had a disturbing event yesterday.
Did you know Canadian banks let companies override "stop-payment" orders?
On advice from a financial advisor I put in a stop-payment order at the TD Trust, got charged $25 for it. Checked my bank statement a few weeks later and found the charge was still coming off.
"They (companies) can do that" said the bank. And being a Canadian bank it blamed the customer. "You should have told them you wanted to stop the payment"
"Then why am I paying you $25 if I have to be the one to actually get the payment stopped ?" All the bank would do was refund half of $25!
I closed my account. It's the only way to guarantee a stop-payment. And it's free.
Someone may bring up the fine point that "stop payment" is different from "revoke authorization", but no payments were ever stopped.
Further more the bank teller and bank manager said, "We see this all the time. They (the companies) just have to change one thing at their end to do this".
Now, this made me think: is it a SQL injection into the bank's database? As you know this is long-standing weakness of databases that must be accounted for - that is, it can be prevented - by the database developer. And why has no one addressed this matter before?
Did you know Canadian banks let companies override "stop-payment" orders?
On advice from a financial advisor I put in a stop-payment order at the TD Trust, got charged $25 for it. Checked my bank statement a few weeks later and found the charge was still coming off.
"They (companies) can do that" said the bank. And being a Canadian bank it blamed the customer. "You should have told them you wanted to stop the payment"
"Then why am I paying you $25 if I have to be the one to actually get the payment stopped ?" All the bank would do was refund half of $25!
I closed my account. It's the only way to guarantee a stop-payment. And it's free.
Someone may bring up the fine point that "stop payment" is different from "revoke authorization", but no payments were ever stopped.
Further more the bank teller and bank manager said, "We see this all the time. They (the companies) just have to change one thing at their end to do this".
Now, this made me think: is it a SQL injection into the bank's database? As you know this is long-standing weakness of databases that must be accounted for - that is, it can be prevented - by the database developer. And why has no one addressed this matter before?






