Skip to content
Public surfaces operational

Fedha, Hazina and Zent are live — new products on the way. Build with us →

Hazina · Digital banking

Banking and treasury without borders.

A white-label digital banking platform — customer wallets and savings, lending and BNPL, remittance, merchant acquiring, and a business treasury workspace — deployable under your brand from one governed core.

  • Multi-entity, multi-currency
  • Approvals & payment runs
  • Quoted FX & reconciliation
Multi-currency
Account model
Balances per entity, project, and currency
Continuous
Reconciliation
Event-driven matching with exception queues
API
Partner-led rails
Integrates with regulated providers

Inside Hazina

The workflows your teams run every day.

Real Hazina layouts, filled with demo data. Your deployment carries your brand, your products and your rules — the controls and evidence come built in.

Request Hazina demo
01 / 02

Approvals

Maker-checker release of a bulk payment, with pre-release checks, funding impact, and each approver's decision recorded.

02 / 02

FX & conversions

A held USD to KES quote with mid-market spread, settlement accounts, the 30-day rate, and progress against the monthly conversion plan.

Product interfaces shown with demo data.

What Hazina does.

01

Customer banking surfaces

Branded wallets, savings, transfers, bill pay, cards, and QR payments in a customer app and web console.

02

Lending and BNPL

Loan origination, limits, repayments, credit scoring, savings-as-collateral, and overdraft options.

03

Remittance corridors

Cross-border send and payout with collection, settlement, and reconciliation built in.

04

Merchant acquiring

Merchant onboarding, products and orders, payment links, terminals, and settlements.

05

Business treasury workspace

Multi-entity accounts, maker-checker approvals, payouts, collections, and continuous reconciliation.

06

API + Console

Engineering teams get APIs. Operators get a beautiful console. Same data layer.

THE SYSTEM BEHIND THE EXPERIENCE

How Hazina
operates.

Hazina is structured as a white-label digital banking platform: customer accounts, savings, lending, remittance, merchant services, and business treasury controls share one governed core, with each deployment configured for the operator's brand, market, roles, rails, and regulatory path.

HAZINA / CONNECTED ARCHITECTURESelect a layer to explore ↘
HazinaGOVERNED PRODUCT CORE
Experience → Governed core → Connected operationsArchitecture illustration · not live activity
01/ 03

The foundation beneath every action.

The account model, controls, and service boundaries that keep the product connected.

07 operating capabilities
01Multi-currency account model

Balances are segmented by entity, project, vendor, currency, and reserve purpose.

02Continuous reconciliation

Ledger, bank, mobile-money, and payment-provider events run through continuous matching and exception queues.

03Approvals and RBAC

Maker-checker policies, limits, roles, and approval history are the reason finance teams buy.

04AML and policy decisions

Single and batch AML screening, provider health, centralized authorization decisions, and versioned OPA policy bundles keep controls explicit and deployable.

05KYB and beneficial owners

Entity onboarding captures directors, owners, operating purpose, and ongoing monitoring state.

06Payouts and collections

Vendor, payroll-like, batch, and referenced inbound payments are visible from API and console.

07Accounting exports

Statements, chart-of-account mapping, audit packs, and accounting export paths sit inside the close workflow.

One product. Connected layers. Traceable by design.Follow the product journey

From signup to settled.

  1. 01

    Open

    Multi-entity onboarding — incorporate-ready KYB packs reviewed in days, not weeks.

  2. 02

    Configure

    Set policies, approval flows, vendor lists, and FX hedging rules in one console.

  3. 03

    Operate

    Issue payments, receive collections, run payroll — across rails, currencies, jurisdictions.

  4. 04

    Close

    End-of-month reports auto-generated. Audit packages ready for your accountant.

Built across the rails that matter.

Composes with the chains, rails, custody partners, and signing providers institutional teams already trust — and bring your own when the brief calls for it.

Account rails

  • Bank accounts
  • Mobile money
  • Card networks
  • Partner payout rails

Settlement

  • Partner-led bank settlement
  • Trust-account operations
  • Reconciliation & exports

Finance & accounting

  • Statement exports
  • Audit packs
  • Webhooks & API
  • Accounting connectors (roadmap)
BEYOND THE INTERFACE

What does Hazina
look like in your business?

Start with the people, markets, and connections that shape your operating model. Then review the controls and deployment scope in detail.

Operating profile

Primary users
Retail customers, merchants, finance teams, and operator admins
Regions
Configured per licensed partner, banking rail, and corridor
Rails
Bank accounts, mobile money, card networks, and partner payout rails
Integration surfaces
Treasury console, payment APIs, approval events, accounting exports
01

KYB and roles

Entity onboarding, operator roles, approval limits, and maker-checker duties are mapped into the access model.

02

Payment controls

Vendor, payroll, FX, and batch payments are designed around configurable approval policies.

03

Reconciliation

Bank, payment, ledger, and accounting events are matched continuously with exception queues.

04

Audit evidence

Export packs, approval history, policy changes, and settlement evidence are included in the operating model.

What to confirm before a pilot
  • Banking availability depends on entity location, partner approval, and compliance review.
  • Treasury environments require named administrators, role model, and payment approval matrix.
  • Accounting and ERP integrations are scoped by connector availability and data mapping.
The next move is yours

Start with the Hazina demo.

Review the demo flow, then request the access path that matches your team: walkthrough, technical review, partner scoping, or implementation planning.