Rakyat ONE

One banking rail carrying three products: an app for members, an app for merchants, and a console for the branch network. Islamic by construction, bilingual by default, and demonstrable today as three working prototypes.

Tabung and Tabung HajiDuitNow QR and tap to pay Shariah screening in the openCDS with a training mode Screened digital assetsBahasa Melayu and English

The proposition

Bank Rakyat does not need to buy the trust every digital bank is spending to acquire. It needs a product surface worthy of the trust it already holds. Rakyat ONE builds the spine once, accounts, identity, payments and the Shariah engine, then puts three apps on it.

Rakyat ONE

Members

Digital card, freeze, virtual card, tap to pay
DuitNow QR with press and hold to confirm
Tabung jars, round up saving, Tabung Haji linked
CDS in two minutes, training mode first

Bisnes

Merchants and SMEs

Counter QR, charged QR, soundbox
Tap to Phone, no terminal to rent
Payroll with EPF, SOCSO, PCB and zakat
Financing priced off real settlement history

Command

Branches, sales, risk

Network view across every branch
Branch queue with a real approval limit
Shariah non compliance event register
Natural language questions on the network

Why it wins the room

Tabung Haji, linked. Balance, queue number and estimated year in the banking app, with auto save feeding it. No competitor can copy this without the same relationship.
Compliance you can read. Every product prints its contract, and a counter that fails the screen cannot be bought.
Training before risk. Virtual money against real Bursa prices. A bank is the only institution with an incentive to teach first.

What it moves commercially

Cheap, sticky deposits. Goal based saving turns intention into a standing instruction. Leaving means abandoning the goal.
Merchant acquisition and fee income. Tap to Phone removes the terminal, so each merchant joins the rail and becomes a financing customer with twelve months of proof.
Lower cost to serve, stronger standing. Applications leave the counter, and a live Shariah event register is what an examiner asks to see.

Shariah architecture, in three rules

Every product names its contract. The aqad is printed on the card, the jar, the offer and the receipt. If a feature cannot name its contract, it does not ship. In use: Wadiah Yad Dhamanah, Mudharabah, Tawarruq, Musharakah Mutanaqisah, Qard, Rahn, Ujrah, Wakalah, Bai al Sarf, Tabarru, Hibah.
Non compliance is blocked, not warned about. Securities Commission Shariah Advisory Council methodology: the activity benchmarks, plus cash and debt each below 33 percent of total assets. A failing counter cannot be traded, and the numbers behind the refusal are shown.
Tainted income separates itself. When a screen changes or a charge exceeds actual loss, the income is quarantined, raised as a Shariah event in Command, and disposed of on the Committee signature. Late payment is capped at ta widh; anything above is gharamah and goes to charity, never to income.

Delivery, in four phases

Phase 1Spine and customer app. Accounts, cards, QR, tap to pay, Tabung, zakat and the contract layer. A complete product on its own.

Phase 2Command, starting with the approval queue and the Shariah event register. Control before analytics.

Phase 3Bisnes and the merchant rail. QR, Tap to Phone, e Invoice and payroll. Financing once history exists to price from.

Phase 4CDS with training mode, the screened wallet, and Tabung Haji once the integration agreement is signed.

6Working surfaces

193Checks passing

2Languages

50Mapped features

The one risk we are naming first · Tabung Haji integration is not secured

Linked balance, queue number and contribution posting assume a data and settlement agreement with Lembaga Tabung Haji, the largest external dependency here. Without it the feature degrades to a savings jar named Haji. Scope it commercially before committing it to a roadmap.