Going Global: Why FinTech Licensing Should Be Managed as a Portfolio

Introduction

A payments infrastructure provider expanding from its home market into Sub-Saharan Africa and Southeast Asia will eventually ask an obvious question: how do we get licensed in each new market? That question needs an answer. But it is usually not the right place to start. It treats each market as an isolated regulatory challenge rather than as one part of a broader expansion strategy.

The better question is: what is the most efficient regulatory architecture for entering our next five markets over the next three years? This is not simply a licensing question. It is a strategic one. International expansion should therefore not be managed as a queue of individual license applications. It should be managed as a regulatory expansion portfolio. Five decisions determine whether that portfolio is commercially and operationally viable: Sequence, Route, Operating Model, Execution and Scale.

These decisions are closely connected. A choice in one dimension changes the options available in the others.

1. Sequence: Where should we enter first, and what does that enable next?

Consider a payments FinTech targeting Singapore, the UAE, Kenya, Nigeria and South Africa. If management ranks those markets solely by revenue potential, it may arrive at one sequence. Once regulatory route, local substance requirements, existing group capabilities, partner availability and execution capacity are considered, the optimal sequence may look very different.

The first market should therefore be assessed not only on its standalone commercial potential. Management should also consider what capabilities, operating experience and regulatory track record it can create for the markets that follow.

This distinction matters because regulatory transferability is easy to overstate. A license obtained in one market will generally not provide automatic access to another. Kenya, for example, does not currently provide general recognition of payment licenses issued in other jurisdictions. A provider already licensed elsewhere must still satisfy the applicable Kenyan requirements.

There are, however, signs of greater regional cooperation. In March 2026, the Central Bank of Kenya and the National Bank of Rwanda signed a memorandum of understanding to develop a license-passporting framework for payment service providers as part of broader regional payment integration. This is a concrete step towards mutual recognition, but not yet a general passport on which a FinTech can base its market-entry strategy.

What can often be transferred more readily is operational precedent. The AML and sanctions framework developed for the first market, governance documentation, application processes and the institutional experience gained through an authorization can all create reusable capabilities.

Regulatory recognition and operational transferability are therefore different. A sound sequencing strategy needs to understand both.

2. Route: Do we need to own the license?

The choice of regulatory route is one of the most commercially significant decisions in the portfolio. Yet companies can default to an own-license strategy without fully comparing the alternatives.

The rationale is understandable. Owning the license provides control. But it can also require more time, capital, local substance and management capacity than other routes. In many markets, the realistic options sit on a spectrum. They may include an own license, an agent or partnership arrangement with an already licensed entity, the acquisition of a licensed local business, or a staged model that begins with a partner and moves to an own license once the market has demonstrated sufficient potential.

Each option creates a different balance between speed, control, capital and flexibility.

Licensing timelines vary considerably depending on the market, license category and quality of the application. A partnership may provide a faster route to market than obtaining an own license. In return, the FinTech accepts commercial and operational dependency on the partner, including its continued regulatory standing and willingness to support the business.

The appropriate route should therefore be determined market by market rather than through a single group-wide assumption. A jurisdiction that is central to the long-term strategy may justify the investment required for an own license from the outset. A market that is primarily being tested may call for a different approach.

3. Operating Model: What must we build locally, and how reversible is the model?

Every regulatory route implies an operating model. It determines how much local staffing, governance, infrastructure and control the business needs. It also determines how easily that model can be changed later. This is where reversibility becomes important.

A partner-led model may require less upfront investment, but it is not necessarily easy to unwind. If the FinTech later decides to obtain its own license, questions that appeared secondary at market entry can become critical. Who owns the customer relationship? Who controls the data? Can customers be migrated to another legal entity, and on what basis? Which controls are performed by the partner? Can transaction histories be transferred in a form the new license holder can use? Which technology components would need to be rebuilt? Do the contractual termination and transition provisions work operationally as well as legally?

A partner model that appears flexible at entry can become expensive to change if the partner controls capabilities that the FinTech later needs to internalize.

An own license requires greater upfront investment, but generally gives the FinTech more direct control over its customer relationships, data, technology and regulatory operating model. That does not make a future restructuring simple. It does, however, provide greater control over the assets and capabilities required to execute one.

The operating-model question is therefore not only what is required to enter the market today. It is also whether today’s structure preserves the company’s strategic options for tomorrow.

4. Execution: How many markets can we realistically execute at once?

Licensing programs are often planned market by market. Several applications are then run in parallel because the project timelines appear to allow it. The limiting factor, however, is often not the calendar. It is organizational capacity.

Four parallel licensing processes do not create four independent workstreams. They draw on the same Legal, Compliance, Finance, Operations and senior-management resources. If several regulators request substantive responses at the same time, those shared resources can become the critical path for the entire expansion program. As a result, delays are not always concentrated in the least attractive or least important market. They tend to emerge wherever regulatory demands coincide with limited internal capacity.

This is also where Sequence and Route affect Execution. A portfolio consisting of one own-license application, two partnership arrangements and an acquisition creates a very different execution burden from four simultaneous own-license applications. Management should therefore treat internal execution capacity as a portfolio constraint when deciding how many markets to pursue at once.

5. Scale: What should be global and what must remain local?

The first four decisions determine how a FinTech enters multiple markets. The fifth determines whether that international footprint becomes a scalable platform or an increasing management burden.

Regulatory requirements differ across jurisdictions. AML risk classifications, reporting requirements, governance expectations and regulatory thresholds may all vary. A FinTech operating in five markets under five independently designed compliance frameworks can therefore end up with more than five sets of local requirements. It can also end up with five different interpretations of risk. That fragmentation may not be apparent during the initial expansion phase. It becomes visible when group management needs a consolidated view of the company’s risk exposure and discovers that comparable classifications or metrics mean different things in different jurisdictions.

The answer is not to impose a rigid global standard regardless of local law. A group framework must accommodate jurisdiction-specific requirements. The objective should instead be to establish a global core with controlled local variation.

The global core can typically include the group’s risk appetite, AML methodology, sanctions principles, governance standards, control architecture, policy hierarchy and underlying technology. The local layer can then address jurisdiction-specific definitions, regulatory reporting, thresholds, MLRO and safeguarding requirements, local governance and regulator-specific documentation.

Determining this boundary early creates an architecture that can be reused as the business expands. Waiting until several markets are already operational can require the group to redesign fragmented structures while they are already supporting live business.

Conclusion: The portfolio question that matters

These five decisions are not sequential. The Route determines elements of the Operating Model. Execution capacity can change the optimal Sequence. The decision about what remains global and what becomes local needs to be made early enough to shape subsequent market entries rather than being addressed after fragmentation has occurred.

The next license should therefore not be assessed in isolation. Its value depends on the regulatory portfolio it helps create.

For FinTech leadership teams, the practical starting point is not the next application. It is determining where to enter, which regulatory route to use, what operating model that route requires, how much expansion the organization can execute at once, and which capabilities should be built once at group level rather than recreated market by market.

International expansion should not be managed as a queue of license applications. It should be managed as a regulatory portfolio.