Launching a Neobank Across Borders: Localization Is a Product Problem

5 MINS

At Arab Bank I helped launch and scale Reflect, a digital-first neobank operating across Palestine and Jordan. Two markets, two regulatory frameworks, one product. The experience taught me that localization is not a translation task you hand off at the end, it is a product problem you design for from the first flow.

Onboarding is where regulation meets the user

A neobank lives or dies on onboarding. If a new customer cannot open an account in minutes, nothing else you built matters. But onboarding is also where every regulatory requirement lands hardest, eKYC, identity verification, compliance checks, and account activation that a regulator has to approve.

I owned digital onboarding across both markets, partnering with compliance, risk, and engineering to deliver activation that was seamless for the user and approved by the regulator. The lesson: you cannot bolt compliance onto a finished flow. The flow has to be designed around the compliance reality of each market from the start.

Same product, different rules, different journeys

Palestine and Jordan are not the same regulatory environment, and pretending they were would have broken the product. Onboarding steps, document requirements, and eligibility logic all had to differ by market, while the core experience still had to feel like one coherent neobank.

That is the real localization challenge: making two compliant journeys feel like one product. We kept the underlying systems shared and varied the rules, the copy, and the steps at the edges. Cross-market localization is mostly the discipline of deciding what stays the same and what has to flex.

Translating policy into an in-app experience

Expanding Reflect into credit, BNPL, credit cards, and salary advances, meant turning underwriting policy into something a user could actually move through. Eligibility logic, risk thresholds, and operational workflows are written for risk teams, not for tenants tapping through an app at midnight.

A big part of my job was sitting between the policy and the screen: taking dense underwriting rules and turning them into eligibility a user understands, journeys they can complete, and workflows operations can run. The policy is the constraint; the experience is the product.

Foundations first, growth second

It is tempting to chase the exciting features, rewards, credit, engagement loops. But a neobank without rock-solid account opening, card management, payments, and transaction flows is a marketing campaign, not a bank. We launched the foundational features first and earned the right to build loyalty and credit on top.

The flashy features get the attention. The foundations get the trust. In a regulated market, trust is the only thing that compounds.

Research In, Data Out: How I Keep Product Decisions Honest

Digitizing Rent: Lessons From Building Dubai's First Fully Digital Rent Collection

Akram skipped presentations and built real AI products.

Akram G. Humaidi was part of the April 2026 cohort at Curious PM, alongside 18 other talented participants.