Kaspi.kz Super App UI Clone in React Native

What kind of super app is Kaspi, exactly?

A payments-first one, which changes the whole clone. Most super-app clones start from food delivery or ride-hailing and bolt on a wallet; Kaspi.kz grew the other way, from a bank and a payments network outward into marketplace and services, so the home screen is built around money, not a feed. The scale explains the ambition: in one reported year, 1.6 billion payments totaling KZT 15.2 trillion moved through Kaspi.kz, which is the kind of volume that makes a QR code the primary interface for a whole country.

The honest framing before any code: you are cloning the UX patterns, not the bank. Kaspi’s actual product is regulated financial infrastructure; a clone reproduces the three-pillar structure and the payments-first flows on top of licensed providers, never real banking rails you do not hold a license for. Build it as a regional super-app template, and the payments pieces route through a licensed PSP, the same standing rule as every fintech build.

What are the three pillars, and how does the shell hold them?

Kaspi organizes around Payments, Marketplace (Shop), and Travel/Services, and the navigation is the clone’s first real decision:

Pillar	What lives there	Home-screen role
Payments	QR pay, P2P transfers, bills, the wallet	The default tab; the reason people open it daily
Shop	Marketplace, the buy-now-pay-later flows	The revenue surface
Services	Travel, government payments, utilities	The stickiness that makes it a super app

The shell that holds three heavy products is a tab bar where Payments is the center of gravity, not an equal peer. The home tab leads with the QR scan-and-pay action and the wallet balance, because a payments-first super app is judged on how fast you can pay, the same scanner-as-home-screen logic as the Paytm QR scanner clone. Each pillar is effectively its own app inside the shell, so the architecture is feature-module navigation with a shared wallet and identity layer underneath, the multi-module pattern any super-app clone lives or dies on.

What does the payments home actually need?

The fastest possible path from open to paid, plus honest money state. The QR payment flow is the spine: open, the camera is one tap (or already live) away, scanning a merchant code resolves to a confirm-amount-and-pay screen, and the payee name renders before confirmation as the fraud check (the same QR-swap defense the genre requires). P2P transfers mirror it, recipient by phone number, amount, a who-paid record afterward.

Two money-honesty rules carry the home screen. The wallet balance is the truth the user came for, so it renders immediately and updates after every transaction, with a clear pending state for transfers in flight (never an optimistic “sent” before confirmation). And buy-now-pay-later, central to Kaspi’s marketplace, is a disclosed credit product, not a frictionless button: the installment terms, the total cost, and the schedule show before commitment, because BNPL UIs that hide the cost are exactly what regulators are tightening on.

What makes it feel Kazakhstani rather than a generic super app?

Localization that goes past translation. The app speaks Kazakh and Russian (a real bilingual toggle, not one language with the other bolted on), formats currency in tenge with local conventions, and treats government and utility payments as first-class, because in this market the super app is how people pay the state, not an afterthought. Phone-number identity over email, QR over card entry, and cash-adjacent flows reflect how the market actually transacts.

The clone’s screens, the payments home, the QR confirm, the marketplace grid, the BNPL schedule, the services hub, come as free VP0 designs an agent generates the feature modules from, so the work lands on the integration (licensed PSP, shared wallet state, the bilingual layer) rather than reinventing a three-pillar shell from a blank prompt. The marketplace half is no afterthought: Kaspi reportedly captures about 70% of Kazakhstan’s online retail market, and the build follows the same Indonesian-and-beyond commerce patterns as the Tokopedia build, COD-adjacent options, voucher rails, server-truth on anything time-sensitive. Route the money through a licensed PSP and treat buy-now-pay-later as the disclosed credit product it is.

The Filipino wallet-plus-bank variant of the same payments-first model is built in the Maya digital bank clone.

Key takeaways: a Kaspi-style super app

• Payments-first, not delivery-first: the home screen is built around the QR pay and wallet, with Payments as the tab bar’s center of gravity.
• Three pillars in a feature-module shell: Payments, Shop, Services, each its own app over a shared wallet and identity layer.
• Clone the UX, route money through a licensed PSP: the real Kaspi is regulated infrastructure, not something a clone reproduces.
• BNPL is disclosed credit: terms, total cost, and schedule before commitment, never a frictionless button.
• Localize for the market: real Kazakh/Russian bilingual support, tenge, phone-number identity, government payments as first-class.

Frequently asked questions

How do I build a Kaspi.kz-style super app in React Native? Start from a free VP0 design for the three-pillar shell (Payments, Shop, Services) and have Claude Code or Cursor generate feature modules over a shared wallet and identity layer, with a payments-first home built around QR scan-and-pay. Route all money flows through a licensed payment provider, since the real Kaspi is regulated banking infrastructure.

What makes Kaspi different from other super apps? It is payments-first: where most super apps grow from delivery or ride-hailing and add a wallet, Kaspi grew from a bank and payments network outward into marketplace and services. So the home screen centers on the QR pay action and wallet balance rather than a content feed.

Is it legal to clone a fintech super app like Kaspi? Cloning the UX patterns and building a regional super-app template is fine; reproducing actual banking or payment-transmission functions is not without licenses. The legitimate build routes payments through a licensed PSP and never holds or settles funds itself.

How should buy-now-pay-later appear in the UI? As disclosed credit: the installment terms, total cost including any fees, and the full repayment schedule shown before the user commits. BNPL is central to Kaspi’s marketplace, and hiding its cost behind a frictionless button is exactly the pattern regulators are tightening on.

What localization does a Kazakhstani super app need? Genuine Kazakh and Russian bilingual support (a real toggle, both first-class), tenge currency formatting, phone-number identity over email, QR over card entry, and government and utility payments treated as core features rather than extras, because in this market the super app is how people pay the state.