UK: Duties Not To Facilitate Fraud

Last Updated: 23 March 2015
Article by Andrew Evans, Clare Burman and Oliver Abel Smith

Fraud and forgery have always been an issue for banks and customers alike in the transfer of money and these days, with the electronic transfer of money, the risks are even greater. This briefing paper explores what duties banks and their customers owe not to facilitate fraud.

What duties apply to banks and their customers to prevent fraud arising in banking transactions?

 With the widespread use of mobile and internet banking, there has been an increased focus on the need to mitigate the possibility of fraudulent activity in private banking transactions, with a duty of care placed on both a bank and its customers. Such duty of care has long been in existence, with statute granting certain protections to banks and numerous cases establishing the obligations owed by each party, particularly in relation to the drawing of cheques.

 The extent of the duty of care owed by each party however is predominantly dependent on the terms and conditions of the contract governing the bank account. For those banks which have signed up to the Lending Code, there is a requirement that terms are in compliance with them. In addition, both the Financial Conduct Authority's Banking Conduct of Business Rules and the Unfair Terms in Consumer Contracts Regulations ("UTCCRs"), impose a duty of fairness on the bank to its customer who is a consumer. Terms are regarded as unfair if, contrary to the requirement of good faith, they cause a significant imbalance in the parties' rights and obligations to the detriment of the bank's customer. Accordingly, a bank would be unable to exclude their liability by restricting the duty of care owed to their consumer customers. Common law has supported this approach, reiterating that a duty of care exists on both banks and their customers not to facilitate fraud.

To what extent does a bank owe its customer a duty of care not to facilitate fraud?

 Banks are expected to comply strictly with their customer's payment orders, issuing corresponding payment orders that precisely match that of their customer's. There are limited circumstances in which a bank is able to refuse a payment order, and in the case that it does, the bank must inform the customer at the earliest opportunity that it is doing so and, where possible, provide an explanation. In Bank of New South Wales v Laing [1954] AC 135 it was held that there was an obligation on a bank to comply with their customer's payment order so long as the account was in credit. Banks are also entitled to reject a payment order where the customer has breached the agreed terms and conditions governing the account, for example by not providing two signatures for a joint account payment, or where making the payment would be considered unlawful. 

 However, the duty to obey a customer's payment order can conflict with a bank's duty to exercise reasonable care and skill, in protecting its customer from the fraud of agents such as directors and partners in issuing a payment order. A conflict can occur where a bank is provided with what may appear to be an authorised payment order, but in fact was made as a result of fraudulent activity, raising questions as to the extent of the duty of care a bank owes to its customer in confirming the validity of the payment order instruction.

The Payment Services Regulations ("PSRs"), where they apply, address the issue of the misuse of a payment instrument.  They direct that a bank will only have the authority to make a payment or debit a customer's account if it can show that consent has been obtained from the customer.  The form and procedure for giving consent to the execution of a transaction must be set out in the information given to a customer before a transaction is concluded. If a bank cannot show that consent has been obtained the transaction must be regarded as unauthorised. As a result,  if a third party were to gain access to a customer's electronic payment device or were able to bypass it altogether and send payment instructions to a bank, the obligation on the bank to assess whether it had the consent to process the transaction would be dependent on the terms of the contract between the parties.

In situations where incorrect payment instructions are given to a bank as a result of fraud and a bank acts in accordance with those instructions, case law has sought to restrict the liability of a bank. In Tidal Energy Ltd v Bank of Scotland PLC [2014] EWCA Civ 1107 it was held that a customer's bank will not be liable for facilitating the defrauding of its customers, so long as it follows established banking practice. In this particular circumstance, the customer had provided the bank with the correct name but incorrect account number and sort code, having been subject to fraud. The bank complied with the payment order to the fraudulent third party and the payment was withdrawn from the account. It was held that as established banking practice did not require that a bank should match names to account numbers and sort codes, the bank was not under a duty of care to do so.

Standard banking practice requires that in order to confirm a payment instruction, a bank must provide to its customer details of transactions made from their account, including the date of the transaction, the amount of the transaction, the name of the payee or payer and a reference so that the payment can be easily identified. More stringent requirements have been proposed in the form of a Fourth Money Laundering Directive and revised Wire Transfer Regulations.

In the event that there has been a misdirection of payment, the Code of Best Practice ("Code") published by the Payments Council provides guidance on payments made via BACS, CHAPS and Faster Payments. It directs that both the sending and receiving banks would be expected to investigate the misdirected payment in line with the Credit Payment Recovery process and associated timeframes. The receiving bank will also be expected to inform the sending bank of the progress and outcome of any error recovery request. If the receiving bank is not a subscriber to the Code or a payment scheme member it should still follow the recovery framework processes, and seek information from its sponsor scheme member on these. The sending bank, however, may refer it to the Code and request it to contact its customer within two working days.

 Difficulties may, however, surface where a bank complies with standard banking practice, but fails to comply with its own internal procedures for the verification of the authority of a payment order. This could be problematic in situations where a bank's internal procedure provides a more rigorous requirement on the bank to verify the payment order, than that set by standard banking practice. On the one hand, it could be considered that so long as the bank complies with standard banking practice there should be no expectation that they meet a higher threshold by complying with their own internal procedure. However, it is likely that a court would not look favourably upon a bank which has failed to comply with its internal procedures, in facilitating fraud on a customer's account, regardless of whether its conduct met standard banking practice. In order to satisfy the duty of care owed to its customer, a bank would be well advised to comply with its internal procedures, in addition to standard banking practice.

To what extent does a customer owe its bank a duty of care not to facilitate fraud?

A customer also owes its bank a duty of care: the duty to refrain from drawing cheques or other payment orders in such a manner as to facilitate fraud or forgery (following the House of Lords' decision in London Joint Stock Bank Ltd v Macmillan [1918] A.C. 777, 789);and the duty to inform the bank of any forgery of a cheque as soon as he becomes aware of it (following the House of Lords' decision in Greenwood v Martins Bank Ltd [1933] AC 51). Whilst these duties were stated in relation to the drawing of cheques, they are applicable to payment orders through all mediums.

 The PSRs provide that a bank's customer would be liable for all losses arising from the unauthorised use of a 'payment instrument' if he has intentionally or with 'gross negligence' failed to comply with his statutory obligations, for example by not complying with the terms and conditions of the use of the payment instrument, failing to notify the bank without 'undue delay' (and no later than 13 months after the date of the transaction) of its loss, theft, misappropriation or unauthorised use, or failing to take reasonable steps to keep the personalised security features of the payment instrument safe.

However, the Financial Conduct Authority has indicated that while a customer is obligated under the PSRs to take all reasonable steps to keep the personalised security features of his payment instrument safe, a contractual term which prohibits the customer from writing down or recording a password or PIN in any form goes beyond 'reasonable steps' and may potentially be unfair under the UTCCRs. A term specifying that a customer will be liable for any unauthorised transaction if he records his password or PIN, will be inconsistent with the UTCCRs and is likely to be considered unenforceable. What constitutes reasonable steps will depend on the circumstances, but payment service providers must specify the steps they expect customers to take in their pre-contract disclosure information.

 Under the PSRs, the bank bears the burden of proof where a customer's claim that a transaction is unauthorised is rejected. A rejection must be supported by sufficient evidence to prove that the customer is guilty of fraud, gross negligence or intentional breach, and the bank must provide an explanation for the rejection to the customer.

It is worth noting, however, that whilst a customer would be liable for all loses incurred due to his 'gross negligence', if there is no element of culpability on behalf of the customer, the customer could only be liable for the first Ł50 of the loss.

Conclusion

Both banks and their customers have a duty not to facilitate fraud on the customer's account and care must be taken by both parties to ensure they meet their legal obligations.  Where a private bank is dealing with individuals it needs to ensure that it complies with all its internal procedures as well as standard banking practice, otherwise it could find that, in the event of fraud, a court would not allow it to rely on any exclusion of liability clause in its standard terms and conditions.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.