Maya Digital Bank UI Clone in React Native

What kind of app is Maya, and what shapes the clone?

A digital bank wearing an e-wallet’s clothes, which is the key tension. Maya (formerly PayMaya) reached 44 million registered users and over $1 billion in processed transactions, and became, by its own account, the Philippines’ number-one digital bank, sitting in a market with an estimated 58 million active e-wallet users where GCash is the giant it competes against. So a Maya-style clone is not just a wallet UI; it is the wallet-plus-bank hybrid that defines the Filipino market: pay-with-QR daily, but also a real deposit account with interest, in one app.

The honest frame first: you clone the UX patterns of a digital-bank-plus-wallet, not the bank. The actual Maya is a licensed bank under Bangko Sentral ng Pilipinas supervision; a clone reproduces the screens and flows on top of a licensed provider, never real deposit-taking or payment rails you do not hold a license for. Build it as a regional fintech template, money routed through a licensed PSP.

What does the home screen owe a wallet-plus-bank user?

Both jobs at once, without burying either. The Filipino market opens this app to pay (QR scan, send money, buy load/airtime, pay bills) and to bank (see the savings balance, the interest earned), so the home leads with the available wallet balance and the primary actions, with the savings/deposit surface a clear, separate tier rather than a tab nobody finds:

Surface	What lives there	Home-screen role
Wallet	Balance, QR scan-to-pay, send, bills, load	The default; daily reason to open
Savings/Deposit	Interest-bearing account, rate, earned	A distinct, visible tier, not hidden
Cards	Virtual/physical card, freeze, details	One tap from home
Vouchers/Deals	Cashback, promos	The engagement layer

The QR pay flow is the daily spine, and it follows the Philippine market reality: QR Ph (the national interoperable QR standard) means scanning works across providers, and the payee name renders before confirmation as the fraud check, the same scan-confirm discipline as the Paytm QR scanner clone. Buy-load (mobile airtime top-up) is a first-class action in a way Western wallets never have, because prepaid is how most of the market’s phones work.

What does the digital-bank half require that a wallet doesn’t?

Honest money state and real account semantics. The savings balance is a deposit, so the UI shows the interest rate plainly, the interest earned over time, and any deposit insurance framing accurately (in a real bank, deposits are insured up to a limit; a clone should never imply protection it does not have). Transfers between the wallet and the savings account are their own clear flow, and the distinction between “spendable wallet balance” and “savings balance” must never blur, because a user who thinks their savings are spendable at the QR scanner is a support ticket and a trust break.

The same pending-not-optimistic rule governs every money movement: a transfer shows “processing” until the backend confirms, never an instant “sent” the network might contradict, the standing fintech discipline behind builds like the Kaspi super app. KYC is tiered the way the regulations require: a basic wallet opens with light verification, while the bank account and higher limits trigger full identity checks, surfaced before the user hits the wall rather than mid-transaction.

What makes it feel Filipino?

Localization past translation. The app handles pesos with local formatting, treats buy-load and bills (utilities, government payments) as core daily actions, supports the remittance reality (OFW families receiving money from abroad is a massive use case), and speaks the market’s bilingual English-Filipino register naturally. Vouchers and cashback are heavy engagement drivers here, so the deals surface is prominent, not an afterthought.

The screens, the wallet home, the QR pay, the savings dashboard, the card management, the buy-load flow, come as a free VP0 design, so an agent generates the wallet-plus-bank modules onto a real structure, with the licensed-PSP boundary and the wallet/savings separation already in the model rather than bolted on. The broader pattern, render the fintech UX, route money and deposits through licensed providers, is the same one behind every regional neobank and super-app clone.

The Latin American checkout variant, where installments and cash are first-class, is built in the Mercado Pago checkout UI.

The European single-purpose neobank variant, clean and IBAN-first, is built in the N26 bank app clone.

The Thai receive-code variant, generating a standards-compliant national QR, is built in the PromptPay QR generator.

The card-control surface of a super-app’s fintech, freeze as state not intent, is built in the RappiPay card management UI.

Key takeaways: a Maya-style digital bank clone

• It is a wallet-plus-bank hybrid, not just a wallet: daily QR pay alongside a real interest-bearing deposit account, both visible on home.
• Clone the UX, route money through a licensed PSP: the real Maya is a BSP-licensed bank; a clone never takes deposits itself.
• Never blur wallet balance and savings balance: spendable and deposited are different, and confusing them breaks trust.
• QR Ph and buy-load are first-class: interoperable QR pay and prepaid airtime top-up are daily Filipino-market actions.
• Tiered KYC and honest money state: light wallet verification, full checks for the bank account; processing-not-optimistic on every transfer.

Frequently asked questions

How do I build a Maya-style digital bank UI in React Native? Start from a free VP0 design for the wallet-plus-bank shell and generate modules with Claude Code or Cursor: a wallet home with QR Ph scan-to-pay, send, and buy-load, plus a distinct savings/deposit surface showing the rate and interest earned. Route all money through a licensed PSP, since the real Maya is a BSP-licensed bank.

What makes Maya different from a regular e-wallet? It is a digital bank and a wallet in one: alongside the daily QR pay, send, and bills, it offers a real interest-bearing deposit account. The clone must surface both jobs on the home screen and keep the spendable wallet balance clearly separate from the savings balance.

Is it legal to clone a digital bank like Maya? Cloning the UX patterns and building a regional fintech template is fine; taking deposits or transmitting payments is not without licenses. The real Maya operates under Bangko Sentral ng Pilipinas supervision, so a clone routes money through a licensed provider and never holds funds itself.

What Philippine-specific features does the app need? QR Ph interoperable QR payments, buy-load (prepaid mobile airtime top-up) as a first-class action, bills and government payments, remittance support for OFW families, peso formatting, and a heavy vouchers/cashback layer, all reflecting how the Filipino market actually transacts rather than a Western wallet’s assumptions.

How should the app handle the savings versus wallet distinction? As two clearly separate balances with an explicit transfer flow between them: the spendable wallet balance drives QR pay, while the savings balance is a deposit shown with its interest rate and earnings. Blurring them, so a user thinks savings are instantly spendable, is a direct trust break.