We’d like to remind Forumites to please avoid political debate on the Forum.
This is to keep it a safe and useful space for MoneySaving discussions. Threads that are – or become – political in nature may be removed in line with the Forum’s rules. Thank you for your understanding.
📨 Have you signed up to the Forum's new Email Digest yet? Get a selection of trending threads sent straight to your inbox daily, weekly or monthly!
Monzo have taken my money following advice from HSBC
Comments
-
You would still not get a yes or no answer to that question now - although you'd get some thing a lot more intelligent than the repeated uttering of an abbreviation. Unless you want to make a payment to a person, you have no right to know who a given account belongs to, without the account holder agreeing that you should know. Not that it's a question too many people would be asking in the first instance unless they need to make a payment to the account holder.grumbler said:
Just imagine (in pre CoP times) coming to a branch (or using telephone) and asking politely "Can you tell me, please, whether your account xx-xx-xx yyyyyyyy belongs to Mr J.Smith? The answer would be something like "DPA.... DPA.... DPA .... DPA........"eskbanker said:grumbler said:eskbanker said:
Only if they're prepared to breach the Data Protection Act (so they won't do this)!grumbler said:Banks aren't arbiters. If you don't agree to return the money, your bank will give your details to the sender so that they could try to recover it by other means, e.d. Small Claims Court.Well, how wrong I was believing that this nonsense changed at last when new safeguards were introduced!
Assuming you're referring to Confirmation of Payee, this protocol was presumably implemented within the bounds of what DPA, sorry, the 'stupid DPA', permits, as it was never likely that the data protection legislation would be amended specifically for this purpose! CoP obviously falls some way short of full disclosure of the payee's details, even though it does confirm a partial or full match with the name of the account holder....grumbler said:Some time ago it was impossible to check whether some bank account belonged to some particular person - allegedly because of the same stupid DPA. Now it's easy to do. Was the DPA changed accordingly?0 -
eskbanker said:
Your point being....?grumbler said:
Just imagine coming to a branch (or using telephone) and asking politely "Can you tell me, please, whether your account xx-xx-xx yyyyyyyy belongs to Mr J.Smith? The answer would be something like "DPA.... DPA.... DPA .... DPA........"eskbanker said:grumbler said:eskbanker said:
Only if they're prepared to breach the Data Protection Act (so they won't do this)!grumbler said:Banks aren't arbiters. If you don't agree to return the money, your bank will give your details to the sender so that they could try to recover it by other means, e.d. Small Claims Court.Well, how wrong I was believing that this nonsense changed at last when new safeguards were introduced!
Assuming you're referring to Confirmation of Payee, this protocol was presumably implemented within the bounds of what DPA, sorry, the 'stupid DPA', permits, as it was never likely that the data protection legislation would be amended specifically for this purpose! CoP obviously falls some way short of full disclosure of the payee's details, even though it does confirm a partial or full match with the name of the account holder....grumbler said:Some time ago it was impossible to check whether some bank account belonged to some particular person - allegedly because of the same stupid DPA. Now it's easy to do. Was the DPA changed accordingly?My point being that something that was impossible allegedly because of DPA suddenly became possible without any amendments to DPA.
0 -
I don't see any inconsistency here myself - it seems perfectly reasonable to me for a bank to have a policy of instructing and training staff not to divulge personal details of others in conversations with customers, while also participating in an industry-wide initiative (that will presumably have been carefully reviewed by legal and compliance teams) that entails auditable validation of limited personal data in certain controlled circumstances.grumbler said:My point being that something that was impossible allegedly because of DPA suddenly became possible without any amendments to DPA.1 -
Band7 said:
You would still not get a yes or no answer to that question nowgrumbler said:
Just imagine (in pre CoP times) coming to a branch (or using telephone) and asking politely "Can you tell me, please, whether your account xx-xx-xx yyyyyyyy belongs to Mr J.Smith? The answer would be something like "DPA.... DPA.... DPA .... DPA........"eskbanker said:grumbler said:eskbanker said:
Only if they're prepared to breach the Data Protection Act (so they won't do this)!grumbler said:Banks aren't arbiters. If you don't agree to return the money, your bank will give your details to the sender so that they could try to recover it by other means, e.d. Small Claims Court.Well, how wrong I was believing that this nonsense changed at last when new safeguards were introduced!
Assuming you're referring to Confirmation of Payee, this protocol was presumably implemented within the bounds of what DPA, sorry, the 'stupid DPA', permits, as it was never likely that the data protection legislation would be amended specifically for this purpose! CoP obviously falls some way short of full disclosure of the payee's details, even though it does confirm a partial or full match with the name of the account holder....grumbler said:Some time ago it was impossible to check whether some bank account belonged to some particular person - allegedly because of the same stupid DPA. Now it's easy to do. Was the DPA changed accordingly?You will get even more than yes/noThis account is registered to John Smith- Barclays. And what I entered was just J Smith.
0 -
I can assure you that what you'd hear from the frontline CS would be DP ACT , not policy.eskbanker said:
I don't see any inconsistency here myself - it seems perfectly reasonable to me for a bank to have a policy of instructing and training staff not to divulge personal details of others in conversations with customers, while also participating in an industry-wide initiative (that will presumably have been carefully reviewed by legal and compliance teams) that entails auditable validation of limited personal data in certain controlled circumstances.grumbler said:My point being that something that was impossible allegedly because of DPA suddenly became possible without any amendments to DPA.
0 -
And?grumbler said:
I can assure you that what you'd hear from the frontline CS would be DP ACT , not policy.eskbanker said:
I don't see any inconsistency here myself - it seems perfectly reasonable to me for a bank to have a policy of instructing and training staff not to divulge personal details of others in conversations with customers, while also participating in an industry-wide initiative (that will presumably have been carefully reviewed by legal and compliance teams) that entails auditable validation of limited personal data in certain controlled circumstances.grumbler said:My point being that something that was impossible allegedly because of DPA suddenly became possible without any amendments to DPA.
It'll be a policy designed with DPA compliance in mind, but expecting frontline customer-facing staff to be experts on the rationale behind all of their work instructions is optimistic....
Anyway, this is all getting further away from OP's concern about reversal (or not) of a transfer, so would suggest that if you want to keep digging further into data protection principles then doing so in another thread would probably be polite!1
Confirm your email address to Create Threads and Reply
Categories
- All Categories
- 352.2K Banking & Borrowing
- 253.6K Reduce Debt & Boost Income
- 454.3K Spending & Discounts
- 245.2K Work, Benefits & Business
- 600.9K Mortgages, Homes & Bills
- 177.5K Life & Family
- 259K Travel & Transport
- 1.5M Hobbies & Leisure
- 16K Discuss & Feedback
- 37.7K Read-Only Boards