Fintechs and lenders rarely talk openly about a particular kind of friction, even though it affects a significant and growing portion of their customer base. A customer completes full KYC in one country with documents verified, biometrics matched, risk assessment passed, and an account opened.
Then they move, so the moment they engage with a financial institution in their new country, the verification record disappears. They are a stranger again, and the process starts from zero.
This is the identity portability gap, and it is not a niche edge case. There are over 280 million international migrants worldwide today, and permanent-type migration to OECD countries hit a record in 2023, with 6.5 million new entrants, a 10% year-on-year increase.
Digital businesses now operate without borders, but customer verification has not kept pace with this global reach. People move between countries for work, education, family, and economic opportunity at a scale the financial system was not designed to accommodate. Every time they cross a border, their verified financial identity stays behind.
For fintechs and lenders building products for a mobile world, this gap has three distinct costs: operational, commercial, and compliance-related. Understanding all three is the starting point for solving it.
Why KYC Does Not Follow the Customer
KYC is designed around regulatory requirements. A financial institution needs to establish who its customer is, understand the relevant risks, and meet the obligations of the jurisdiction it operates in.
Depending on the market, this can involve government-issued documents, biometric verification, sanctions screening, address confirmation, and other checks. The challenge is that these requirements, and the systems built to satisfy them, are not identical everywhere.
Countries have different regulations, identity documents, databases, data protection requirements, and approaches to what digital identity verification looks like in practice. FATF provides international standards for anti-money laundering and customer due diligence, but individual countries implement those standards through their own legal, administrative, and operational frameworks.
As a result, the compliance landscape looks materially different from one market to the next, even when the underlying intent is the same. That means a successful KYC check in one market does not automatically become a reusable verification record in another.
The customer may have to provide their documents again, complete another biometric check, and go through another full round of screening, not because anything about them has changed, but because the infrastructure that verified them the first time is not connected to the infrastructure that needs to verify them now.
The problem is not that verification is unnecessary. It is that verification is often difficult to carry forward, even when it has already been done to a high standard.
Consider a customer who has already built a financial life in one country and then moves abroad. They may have a verified identity, an established banking relationship, and years of interactions with financial institutions that know them well.
When they enter a new market, however, the institution serving them may have limited access to the identity information that already exists. From the business's perspective, the customer is effectively new, regardless of their actual history. This creates a disconnect between who the customer is and what the new institution can access, and that disconnect costs both sides.
It is also why identity portability should not be confused with simply accepting another institution's KYC decision at face value. Portable identity does not mean verifying once and accepting it everywhere without question.
It means creating trusted, structured ways to reuse identity information or credentials when appropriate, while still allowing the receiving institution to meet its own regulatory and risk requirements.
FATF's digital identity guidance describes portability as the ability to use digital identity credentials to prove official identity with new organisations without requiring personal data to be obtained and verified from scratch each time.
That nuance matters a great deal for financial services, where regulatory obligations are real, and the consequences of getting verification wrong run both ways.
What the Portability Gap Costs Businesses
For fintechs and lenders, repeated verification is more than a customer experience issue. It creates friction and cost at multiple points in the business, some of which are visible in budgets and some of which are not.
Operational friction
Compliance and operations teams end up handling extra documents, verification exceptions, and manual reviews simply because a customer's identity doesn't fit neatly into the systems already in place.
This adds time, adds headcount pressure, and introduces inconsistency, because manual review at scale is never as consistent as a well-designed automated process.
Onboarding friction
Every additional step gives a customer another reason to delay or abandon an application. Traditional KYC processes lose a high percentage of applicants during identity verification when friction is high.
For customers who have already been through this process in their home country and expect a smoother second time around, friction is not just an inconvenience. It is a conversion problem, and for digital financial businesses competing on speed and ease of use, conversion problems have a direct commercial impact.
Cost of expansion
A fintech entering a new market may need to connect to different identity sources, support additional document types, and adapt its verification workflow to local requirements.
Rather than extending an existing identity layer into a new geography, the business often ends up rebuilding parts of its KYC infrastructure market by market. That cost accumulates quickly across three, five, or ten markets, slowing how fast a global fintech can realistically grow.
For lenders specifically, the issue can also affect how quickly they can build confidence in a new applicant. If identity information is incomplete or difficult to verify through existing systems, the application may require additional evidence or manual intervention before the lender can proceed.
This pushes out decision timelines and adds underwriting cost at a moment when the lender is still trying to determine whether the relationship is worth building.
The result is a familiar and frustrating pattern. The customer is global, but the verification process remains stubbornly local.
Portability Does Not Mean Removing Local KYC
There is a temptation to frame identity portability as a way to eliminate repeated KYC entirely, to verify once and be done with it. That is not the right objective, and it is worth clarifying why.
Financial institutions will continue to have their own regulatory obligations regardless of what has happened in another jurisdiction. A customer's circumstances can change between markets, and identity information can become outdated.
Different financial products carry different levels of risk and therefore require different levels of due diligence. A mortgage is not the same as a prepaid card, and a customer verified for one product in one country has not necessarily been verified for a different product in another.
The goal should be to make the process more connected and reusable without compromising those requirements, not to remove them. That could mean validating trusted identity credentials across systems rather than collecting and verifying them from scratch.
It could mean connecting to identity sources in multiple jurisdictions so a lender entering a new market doesn't have to build data relationships from scratch.
It could also mean using infrastructure that adapts the verification process to the specific requirements of the market where the customer is being onboarded, rather than applying a single domestic workflow everywhere and hoping it holds.
In other words, the future of cross-border KYC is not necessarily less verification. It is less unnecessary repetition, and the two are very different things.
Building Identity Infrastructure for a Mobile Financial World
This matters because financial services are no longer confined to the same borders as their customers, and the gap between where customers are and where verification infrastructure reaches is only growing.
A person may be born and verified in one country, bank in another, work in a third, and access financial products somewhere else entirely. Businesses are also expanding into new markets faster than ever, creating customer journeys that cross jurisdictions by design, not by accident.
Identity infrastructure needs to reflect that reality, rather than treating every new geography as a fresh start. For fintechs and lenders, this means moving beyond a model where every market has its own isolated verification process with no connection to what came before.
A more connected approach brings together several layers that need to work in sync:
- Global identity sources to establish who the customer is, drawing on government databases and bureau records across the markets they come from
- Biometric and document verification to confirm that the person presenting the identity is the legitimate holder, not a fraudulent actor using a real identity
- Fraud and sanctions checks to support appropriate risk controls, calibrated to the specific fraud vectors that cross-border onboarding exposes
- Local compliance requirements to ensure that the verification process remains relevant and defensible in the destination market, not just in the source one
Critically, the infrastructure should fit into the business's existing onboarding journey rather than requiring a full rebuild every time the business enters a new market.
Businesses that get this right will treat global identity as a shared layer their entire product stack can draw on, not a separate project to scope and rebuild in each geography.
From Local KYC to Portable Identity
The financial system was largely designed around customers having a strong, stable relationship with a single jurisdiction. That assumption held for a long time.
It holds less and less as global mobility accelerates, and businesses that keep building their verification infrastructure around it will find themselves increasingly out of step with the customers they are trying to serve.
As people move between countries and businesses expand across markets, identity needs to become more connected without losing the regulatory controls that make KYC important in the first place.
The opportunity for fintechs and lenders is not to abandon local verification. It is to build infrastructure that can carry trusted identity information further, across borders, across markets, and across the increasingly complex financial journeys that mobile customers are living.
At Zeeh Global, this thinking drives ZeehID. ZeehID provides global identity verification, combining document and biometric verification with identity data and fraud signals in a single infrastructure layer.
The goal is to help businesses verify customers across markets without building a completely separate identity stack for every country they operate in, because when customers move across borders, their identity shouldn't have to start from scratch.
If your business serves customers across multiple markets, talk to our team about building a more connected approach to global identity verification.
