Embedded finance is often discussed as a single global trend moving in one direction. In practice, the term covers a wide range of models.
In one market, embedded finance may mean payments and credit built into a super-app used for transport, shopping and everyday services. In another, it may appear through an e-commerce platform, vertical software provider or marketplace offering financial services to its merchants.
The technology can look similar from a distance, but the commercial logic is often very different. Distribution, regulation, payment habits and customer expectations all shape how the model works.
So while embedded finance is a singular term, it takes different shapes in different markets. Global adoption does not necessarily produce a global business model. The concept travels easily. The conditions that make it successful remain highly local.
Distribution Shapes The Model
Embedded finance depends heavily on where the customer relationship already sits.
China provides one of the clearest examples. Alipay and WeChat Pay grew from large digital ecosystems in which payments became part of everyday activities rather than a separate financial destination. Together, they still account for the vast majority of Chinese retail mobile-payment volume. From payments, these platforms extended into other financial services because they already had frequent customer interaction and enormous distribution.
That model should not automatically be treated as the template for every market.
In the US, embedded finance has developed strongly through another route: software used by businesses. Vertical SaaS platforms increasingly embed payments and financial products directly into the software restaurants, retailers, and service businesses already use to run their operations. BCG reported in 2025 that more than half of relevant independent software vendors in North America already offered embedded payments.
A restaurant platform, for example, can combine order management, point-of-sale software, payment acceptance and financing because it already sits inside the merchant’s daily workflow. The financial service is valuable partly because of where it appears.
These are both examples of embedded finance, but their distribution logic differs sharply. One grows from consumer platforms with enormous daily engagement; another from specialised business software with deep access to a particular commercial activity.
The route to the customer helps determine which financial products make sense, how frequently they will be used and how the provider can make money from them.
Regulation Changes The Economics
The customer may experience embedded finance as something simple, but the regulatory structure behind it rarely is.
Licensing requirements, safeguarding rules, interchange economics, lending regulation, data access and consumer-protection standards all affect who can provide a service and what it costs to do so. These conditions differ substantially between markets.
Europe is a good example of regulation helping shape the available model. PSD2 established regulated access to payment-account data and payment initiation, opening the way for businesses to build services around bank connectivity rather than relying solely on cards. The European Commission is now pursuing a broader open-finance framework that would extend regulated data sharing beyond payment accounts.
The US has historically developed differently. Sponsor banks, Banking-as-a-Service providers and technology platforms play an important role in allowing non-bank businesses to offer accounts, cards and other financial services. Current US models therefore often require close relationships between the technology company and regulated banking partners.
Those differences are not technical details added after a product has been designed. They affect the economics from the beginning.
A financial proposition that depends heavily on card interchange, for instance, will not produce identical economics in markets with different interchange rules. A product built around open-banking access assumes regulatory and technical conditions that may not exist elsewhere.
Regulation is therefore part of product strategy, distribution strategy and revenue strategy at the same time.
Local Payment Habits Matter More Than Global Product Ambitions
Technology may cross borders quickly. Financial behaviour usually does not.
Brazil illustrates this particularly well. Pix, created by the Banco Central do Brasil, allows instant payments between different types of accounts around the clock and has become usable across person-to-person transfers, merchant payments, e-commerce and recurring payments. The central bank has continued expanding its functionality, including Pix Automático and contactless use through digital wallets.
That creates a very different starting point for an embedded-payment proposition from a market where cards remain the default digital payment instrument.
China followed another path. QR-based mobile payments became widespread partly in an environment where merchant credit-card acceptance had been comparatively limited and mobile platforms could offer a lower-friction alternative. That helped Alipay and WeChat Pay become financial access points inside much broader digital ecosystems.
Compare that again with the US, where card acceptance is deeply established and embedded payments have become particularly important inside commerce and vertical software. Platforms such as Shopify can place payments, merchant financing and other financial capabilities directly inside the tools merchants already use to operate their businesses.
These differences influence far more than checkout design. They affect pricing, risk, acquisition costs and which financial services customers are willing to use through a non-financial company.
This is why localisation cannot mean simply changing currency, language or interface.
A business entering Brazil needs to understand Pix. A European proposition may need to account for open banking and local account-to-account payment behaviour. A US SME product may find its strongest distribution through software platforms and card-based commerce. A consumer proposition in parts of Asia may be entering markets where financial services already sit inside large digital ecosystems.
The question is not simply, “Can we offer this product in another country?” It is, “Does this product make sense inside the way that country already uses money?”
The Infrastructure Can Be Global Even When The Product Is Local
None of this means an international business should build an entirely separate operating model for every market.
That would create its own problem.
A company can use common infrastructure for treasury, compliance workflows, reporting, reconciliation and access to several payment methods while allowing the customer proposition to vary by country. The aim should be to standardise what genuinely benefits from standardisation without pretending local markets are interchangeable.
This becomes increasingly important as businesses expand across jurisdictions. Maintaining a completely separate technology stack, treasury setup and operational process for each country creates duplication and cost. But imposing one rigid financial model across every market can be equally limiting.
A business may want one operating environment while supporting SEPA transfers in Europe, Pix in Brazil, card-heavy commerce in the US and other local payment methods elsewhere.
That is where modern financial infrastructure has a particularly important role. Its value is not making every market behave alike. It is allowing a business to manage differences without rebuilding itself every time it crosses a border.
The local product and the international operating model do not need to be the same thing.
Expansion Requires Adaptation, Not Replication
International growth is often described as a question of scale. In embedded finance, that can be misleading.
A model that performs well in one market cannot always be copied into another with only minor changes. Regulation, payment habits, distribution channels and customer expectations may require the proposition itself to be reconsidered.
The better approach is to separate what should remain consistent from what must change.
Technology, operational controls, reporting and treasury may be managed across several markets. Pricing, payment methods, product design, partnerships and distribution may need to remain much more local.
That distinction matters because some of the most expensive international mistakes begin with a reasonable assumption: if customers valued a financial product in one country, customers elsewhere will probably value the same thing.
But embedded finance succeeds precisely because finance appears in the right place, at the right moment and in a form that makes sense to the user. Change the market and each of those conditions can change with it.
The success of Pix in Brazil, super-app finance in China, open-banking-led services in Europe and vertical SaaS finance in the US does not point towards one global embedded-finance model.
It points towards the opposite conclusion.
Embedded finance is becoming global because financial services can now be placed inside almost any digital experience. But what gets embedded, where it appears, who provides it and how it makes money will continue to differ.
For businesses expanding internationally, the objective should therefore not be to export a successful financial model unchanged. It should be to build an organisation capable of supporting several successful models at once.
The companies that understand that distinction will not merely take embedded finance across borders. They will know what has to change when they get there.
Comments are closed.