Skip to content

A UK retail bank you can run — without being one.

Malai is a complete reference platform for prospective bank operators: a banking core, customer portal, marketing surface, and infrastructure-as-code — wired together so you can evaluate the architecture, license what works, and commission what's missing.

Try the demo → Talk to us

What this bank does

Malai is a working retail bank: customers open accounts, fund them, send and receive Faster Payments, set up direct debits and standing orders, and read an auditable history of every move. The capabilities below are not screenshots of a roadmap — each one is live in the demo, behind the same signup the hero links to.

Malai customer app signed in, showing a current account at £1,247.83 and a savings account at £8,400.00 with quick actions to send money and manage payees

The customer app, signed in to the live demo.

  • Real-time payments (FPS)

    Send and receive Faster Payments end-to-end, with same-second settlement to the recipient.

    Step 3 of the walkthrough below sends one end-to-end.

  • Direct debits & standing orders

    Schedule recurring debits and standing orders; cancel, amend or replay them at will.

    Scheduled runs settle through the same ledger as one-off payments.

  • Confirmation of Payee

    Every new payee is name-checked against the receiving bank before any money leaves the account.

    Watch the name-match resolve in step 4 of the walkthrough.

  • Double-entry ledger

    Every transaction debits one account and credits another — money never appears or vanishes.

    Step 5 of the walkthrough reads the hash-chained ledger record.

  • Multi-rail settlement (BACS, SWIFT)

    Real-time rails for retail-speed payments; batch rails for direct debits; cross-border rails for international.

    The same payment domain drives each rail; one mental model, three settlement paths.

  • Themeable mobile-first app

    The customer app is designed mobile-first; visual theming swaps the brand without a rebuild.

    Open the demo on a phone — registration is one thumb-reach.

  • Modular feature additions

    Each banking capability is a discrete module; new ones plug in without rewiring the rest.

    Accounts, payees, payments, direct debits and standing orders each ship as their own bounded module.

  • Auditable money movement

    Every ledger entry is append-only and hash-chained; movements can be replayed and verified end-to-end.

    The audit chain is the source of truth — reporting, reconciliation and disputes all read from it.

Follow the money

  1. Registration screen asking for first name, last name and email, filled in and ready to create an account
    Step 1

    Open an account

    Self-register in the demo and land in a fresh sandbox account.

  2. Inbound payments simulator crediting £250.00 to the current account from a catalogue counterparty over FPS
    Step 2

    Fund the account

    Credit your sandbox balance so the rest of the flow has money to move.

  3. Review-and-send step of a transfer: £25.00 from the current account to a saved payee with reference Dinner split
    Step 3

    Make a Faster Payment

    Send a real-time payment to another payee inside the demo.

  4. Confirmation of Payee verdict while adding a payee: on record as Transport for London, you entered Transport for London UK, with the option to use the on-record name
    Step 4

    Run a Confirmation of Payee check

    Add a new payee and watch the name-match resolve before the payment is allowed.

  5. Account detail screen with the current balance and a day-grouped transaction history of payments, direct debits and card spend
    Step 5

    Read the audit entry

    Open the account ledger and see the hash-chained record of every move.

Run this flow yourself — register in the demo →

Built for the security review

Standards-language claims with the evidence sitting beside each — identity, data, edge, and operations — so a security review can start from facts, not faith.

Read the security posture →

How it's built

Module-fenced services, idempotent writes on sync and async paths, three-pillar observability, and infrastructure-as-code per environment — the patterns a buyer's platform team would inherit.

Read the architecture →

The fastest read on whether this fits your bank is to use the demo, then read how it's built.

Try the demo → Talk to us