Share

Middle East BaaS Revenues to reach $28 Billion by 2031

Arthur D. Little: Market to reach 4% of total banking income by 2026
Middle East BaaS Revenues to reach $28 Billion by 2031
BaaS

Arthur D. Little (ADL), a prominent management consulting firm, released an exclusive report exploring banking as a service (BaaS) and its competitive opportunities for the Middle East (ME) region. To date, the BaaS market has remained relatively small and largely at the preserve of digital banks, FinTechs and digital nonfinancial platforms. However, as their traditional markets and margins come increasingly under threat from disruptors, BaaS will be the route to salvation for many incumbent banks.

The report, titled ‘Banking as a Service: at the Heart of the Bank of Tomorrow’ outlines the many signs that BaaS is being adopted by small and midsize banks operating at subscale and, as more do, this segment of the market will grow at a compound annual growth rate (CAGR) of approximately 25%. That would mean that, by 2026, revenues in the region from BaaS could stand at $5 billion or approximately 4% of the total banking income in the Middle East.

For banks that use BaaS, new levels of cost reductions open up as they can completely restructure their cost base — reducing the cost base overall and turning the remainder into a much more variable cost: BaaS should be considered by banks in the region as a key enabler of their transformation to embrace the disruptive forces, presuming that regulators will play the catch-up

The BaaS potential

 

Following this expansion, a secondary growth spurt is likely driven by the arrival of larger incumbent banks that have concluded that to remain competitive they, too, need to use BaaS solutions. BaaS revenues should reach $28 billion by 2031, which would amount to about 17% of total banking income in the Middle East. Developed alongside a bank’s core business, BaaS becomes a solid platform from which it can start to rebuild lackluster market valuations, pleasing investors as a result. At the center of the initial growth will be payments and accounts since these products can be most easily embedded. This will likely be followed by movement into consumer lending, as products such as “buy now, pay later” gain more traction.

ADL categorizes providers into four primary segments, differentiated by banking license and breadth of offering:

  • license pure players. These providers are primarily traditional regional banks, typically with weak technology and application programming interfaces (APIs) capabilities. They provide their license to digital banks or BaaS partners.
  • modular license and API “hybrid” players. These providers have strong technology, API capabilities, and a banking license, which is how they can offer BaaS.
  • modular API tech players. Because they are focused on a particular area, such as payments or cards, and have strong APIs and technology propositions, these are attractive partners for BaaS license providers.
  • monolithic BPaaS tech players. With their focus is on business process as a service (BPaaS), these are the providers of traditional core banking systems that give banks their technology backbone. Only those in categories 2 and 3 can really be considered modern BaaS providers.

Implementing BaaS

 

Some incumbent banks may be hesitant about using BaaS because of concerns about the service robustness of a third-party provider or a loss of independence. For instance, it might be contractually difficult to add new features to a product or to discontinue it. They may also be required to share fees with a technology provider. However, such concerns are often overstated and are far outweighed by the benefits that come from being able to focus on core capabilities — front office and the management of balance sheet and risk management — because responsibility for non-core areas has been passed to the most competent provider.

To mitigate risks, banks should have strategically flexible contracts that allow for provider switching, a strong compliance control framework, a clear partnership governance model, and a strong API management process, as well as perform rigorous due diligence upfront. Running pilot projects to eliminate potential disruptions can also ensure implementation goes as smoothly as possible.

The stories on our website are intended for informational purposes only. Those with finance, investment, tax or legal content are not to be taken as financial advice or recommendation. Refer to our full disclaimer policy here.