Banking as a service
 | This article may be written in a style that is too abstract to be readily understandable by general audiences. (January 2018) |
.svg)
Banking as a service (BaaS) is the provision of banking products (such as deposit accounts, loans and credit cards) to customers through non-bank or non-financial third party partnerships. The bank provides the balance sheet management, including capital, liquidity and credit risk management, while the partner company (typically a fintech) interacts directly with the customer via their proprietary app, often accessing the bank's systems and data via APIs.
API-based stack
[edit].png)
Skinner suggested a 3-layer representation of the BaaS stack.[1] In this stack, the underlying infrastructure-as-a-service is provided by a traditional, licensed and regulated bank. Above this bank would be the centralized middleware layer that Skinner refers to as "bank as a service". Added on to the bank as a service is a group of decomposed banking services consisting of an ecosystem of fintech startups and service providers.
With this technology, based on the BaaS-platform, it is possible to create fintech banks, which could improve banking processes and provide increased convenience for banking clients. In such a constellation, fintech banks are enabled to compete directly with banks by offering core banking services without having to build all the products that would be needed. The API-based bank as a service platform serves as the back-end that hosts standalone independent fintech startups and integrates seamlessly with any existing back-office of traditional banks. This allows non-banks to cost-effectively launch additional financial products and expand into additional markets.[1]
Potential consequence
[edit]The consequence of having a decomposed stack is that there are multiple ways that the customer's front-end could be presented. One way would allow the BaaS provider to appear directly as a bank to its customers. This necessitates the provision of a front-end user interface to the end-customers including user authentication and other features. The bank would appear as any other online bank where all banking services are presented and seamlessly integrated in a single user interface. Another option is that the bank will operate as a white label bank, which will then have a software as a service provider on top of the partner operating as the front-end to the end-customer.
Regulations
[edit]Europe
[edit]In Europe, BaaS for fintechs is overseen by the Payment Services Directive (PSD, 2007/64/EC) and its 2nd amendment (PSD2) that was adopted in November 2015.[2] Banking licenses are overseen by competent national authorities in accordance to Directive 2013/36/EU and Article 14 of Regulation (EU) No 1024/2013.[3] The eIDAS regulation provides requirements for authentication and electronic identification and trust services for electronic transactions throughout the entire end-to-end process.[4] Additional oversight for financial and insurance transactions are provided through Directive 2004/39/EC [5] and Directive 2016/97/EU.[6]
United States
[edit]In the United States, banking-as-a-service arrangements are regulated at both the state and federal levels. Banks remain responsible for oversight of third-party partners, including compliance, consumer protection, anti-money laundering controls, and operational resilience. U.S. regulators have issued supervisory guidance on bank-fintech partnerships, and several enforcement actions have involved BaaS programs.
The collapse of middleware provider Synapse in 2024 led to disruption and loss of funds for users of many BaaS platforms leading to increased scrutiny of record-keeping and partner oversight in BaaS models.[7]
Brazil
[edit]In Brazil, BaaS is regulated by the Brazilian Central Bank within the rules of a Payment Institution.[8] The best known BaaS' fintechs providers in Brazil are Matera, Zoop, Dock, and S3 Bank.[9]
India
[edit]In India, BaaS is regulated by the Reserve Bank of India (RBI). On Nov 7, 2023 RBI published Master Direction on Information Technology Governance, Risk, Controls and Assurance Practices with an objective to tighten the governance framework for technology within banking segment.
See also
[edit]
References
[edit]- 1 2 Skinner, Chris. "Overview of APIs and Bank-as-a-Service in FinTech" (PDF). ASAP Agency Moscow. Archived from the original (PDF) on 24 February 2024. Retrieved 16 January 2017.
- ↑ The European Parliament and the Council. "Directive (EU) 2015/2366 on payment services in the internal market, amending Directives 2002/65/EC, 2009/110/EC and 2013/36/EU and Regulation (EU) No 1093/2010, and repealing Directive 2007/64/EC". Official Journal of the European Union. Retrieved 17 January 2017.
- ↑ The European Parliament and the Council. "Directive 2013/36/EU on access to the activity of credit institutions and the prudential supervision of credit institutions and investment firms, amending Directive 2002/87/EC and repealing Directives 2006/48/EC and 2006/49/EC". Official Journal of the European Union. Retrieved 17 January 2017.
- ↑ Turner, Dawn M. "Understanding eIDAS". Cryptomathic. Retrieved 17 January 2017.
- ↑ Commission of the European Communities. "Commission Directive implementing Directive 2004/39/EC of the European Parliament and of the Council as regards organisational requirements and operating conditions for investment firms, and defined terms for the purposes of that Directive" (PDF). European Commission. Retrieved 17 January 2017.
- ↑ The European Parliament and the Council. "Directive (EU) 2016/97 on insurance distribution (recast)". EUR-Lex. Retrieved 17 January 2017.
- ↑ Mason, Emily. "Is Your Money Really Safe In An 'FDIC-Insured' Fintech Account?". Forbes. Retrieved 2026-07-21.
- ↑ bcb.gov.br/ O que é instituição de pagamento?
- ↑ globallegalchronicle.com/ Banco BV’s Investment in S3 Bank
