Areas of Consensus and Controversy
There are areas of consensus in the final rules that should be celebrated, including requirements for clear and meaningful consumer disclosures and robust data security requirements for all parties handling sensitive financial data. However, controversies persist regarding many policy choices in the final rules. For example, the rules only subject certain financial products to disclosure, including credit cards and deposit accounts, while excluding a host of other financial products, including mortgages, auto loans, and investments. The rules also place significant restrictions on third parties receiving data by requiring that all use and retention be limited to what is “reasonably necessary” to deliver a consumer’s requested product or service—an amorphous standard that could be read to restrict innovative secondary uses. And while screen scraping is viewed critically as a risky and outdated practice, it remains permissible under the rules, placing the burden of managing its consequences on data providers. There are also strategic and technical decisions data providers and third parties must make, from API design to bilateral agreements that properly allocate liability for errors, fraud and data breaches, and risk management protocols. Banks may experience an influx of requests for data from authorized third parties, and their third-party risk management practices will need to adapt to assess the unique risks presented by these third parties.
The CFPB’s final rules also rely on “recognized standard setters” to develop “consensus standards” for data formats and access protocols, which are intended to promote interoperability, making it easy for a third party to obtain and digest similar data from multiple data providers. However, the coexistence of multiple data formatting standards (and proprietary formats from data aggregators) complicates this effort to achieve seamless interoperability.
Lastly, the integration of payment initiation data, such as bank account numbers and routing numbers used for ACH transactions, into open banking frameworks introduces opportunities for “pay by bank” services to challenge existing card networks. But these advancements also raise fraud concerns, requiring innovative solutions such as tokenized account numbers (“TANs”) to enhance security.
The Path Forward
Challenges lie ahead for the sound regulation of open banking in the US. A national banking trade association filed suit to stop the rule from taking effect the day it was finalized, and shifts in the CFPB’s leadership and regulatory priorities could cause the agency to amend the final rules in the near term. Notwithstanding these regulatory controversies and headwinds, the demand for consumer-authorized data sharing is expected to continue growing, driven by market forces and consumer expectations for greater control over their financial data.
Data providers will need to identify and document the “covered data” in their control or possession that is subject to disclosure, design compliant APIs, and establish robust third-party risk management protocols. Third parties accessing data, including fintechs and data aggregators, must evaluate their compliance strategies, consumer-facing experiences, and approaches to managing data use and retention. Questions around liability for errors, means of achieving accuracy and interoperability, and minimum contractual terms for third party access remain critical.
This is a transformative moment for open banking and the consumer financial services industry more broadly. Banks, fintechs, standard-setting organizations, and regulators are being pushed to work together in new ways. Now it is incumbent upon them to find common ground to support innovation, manage the operational and regulatory risks presented, and deliver real value to consumers.