High-volume
Launch target
Built for operator scale
White-label · Mobile money
Fedha.
White-label mobile money, delivered under your brand.
A branded mobile money platform for telcos, banks, and licensed issuers, bringing customer wallets, merchant payments, agent operations, admin controls, reporting, and APIs into one product you launch under your own brand.
fedha / workspacePreview
Configured around your marketPartner-led railsBuilt-in controls
Multi-surface
Operator workspaces
Customer, merchant, admin, BI, developer
Brand-led
Deployment model
Roles, data, rails, policy
Inside the Fedha workspace — how it works.
Illustrative interfaces with sample data show the workflows behind each surface — wallets, transfers, KYC, security, treasury, and settlement states that a buyer can follow before a walkthrough or implementation conversation.
Request Fedha demoFedha / Wallets
Wallets
Primary and secondary wallet views with held, available, pending, and created-wallet states.
Fedha / Send money
Send money
P2P send flow with fee, limit, security, review, and confirmation states.
Fedha / Account & security
Account & security
KYC summary, PIN status, passkey setup, sessions, and security controls for the customer account.
What Fedha does.
01
Branded mobile money launch
Telcos, banks, and licensed issuers can launch a customer-ready wallet experience with their own brand, roles, channels, and operating model.
02
Wallet and transaction core
Balances, transfers, fees, settlement, limits, receipts, and reconciliation are handled as one governed money movement layer.
03
Customer, agent, merchant, and biller journeys
P2P transfers, merchant tills, paybills, invoices, bill presentment, agent float, governed cash-in/cash-out, commissions, and super-agent hierarchies share one operating model.
04
Organizations and governed payouts
Branches, units, scoped staff, business wallets, maker-checker approvals, secure mobile decisions, and bulk payout imports support institutional operations.
05
Omnichannel delivery
Native customer and business apps, customer web, operator portals, POS, and dedicated customer, agent, and organization USSD serve smartphone and feature-phone users.
06
Compliance, audit, and reporting
KYC/KYB, AML rules, immutable audit events, retention, legal holds, reconciliation, reporting, and evidence exports are designed into day-two operations.
07
Developer and interoperability layer
API keys, webhooks, sandbox tooling, MiniApps, partner APIs, and national-switch interoperability foundations support integration-led deployments.
THE SYSTEM BEHIND THE EXPERIENCEHow Fedha
How Fedha
operates.
Fedha is structured for regulated mobile money deployments: a branded platform that can launch customer wallets, merchant acceptance, agent networks, settlement operations, admin workflows, and developer integration without rebuilding the operating backbone for every client.
FEDHA / CONNECTED ARCHITECTURESelect a layer to explore ↘
FedhaGOVERNED 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.
06 operating capabilities01Client-bounded setup+
Branding, roles, policies, data boundaries, rail configuration, and operating controls are scoped around each deploying institution.
02Balance integrity+
Posting, holds, reversals, account provisioning, duplicate protection, and projections are treated as the balance source of truth.
03Service contracts+
Customer, merchant, agent, organization, fee, notification, ledger, and transaction services communicate through explicit product contracts.
04Channel breadth+
Customer and business mobile, web portals, merchant and agent operations, POS, and role-specific USSD serve different users without forking the core.
05Security baseline+
Secure sign-in, transaction PIN, MFA, passkeys, role-bound access, audit events, and policy checks are designed into the flow.
06Launch maturity discipline+
Capabilities are tracked clearly through walkthrough, sandbox, pilot, and production readiness so buyers know what is available at each stage.
02/ 03
Connected to the way your business works.
Explore the product surfaces and workflows that extend the core into everyday operations.
06 product modules01Merchant acceptance+
Tills, paybills, payment links, QR, merchant statements, invoices, refunds, and settlement views are part of the operating surface.
02Agent network+
Agent hierarchy, float wallet, commission wallet, cash-in, cash-out, top-up, and offline-tolerant agent-app workflows support branch and field operations.
03Organization operations+
Branches, units, staff scopes, mobile approvals, payout batches, invoices, and operational reporting let institutions govern distributed teams.
04Biller operations+
Governed account-master imports, bill presentment, reference validation, invoices, payment collection, and settlement reporting support utilities and service providers.
05Settlement accounts+
Organization wallets, trust-account style movement, opening liquidity, journals, and paybill settlement support regulated operating patterns.
06Interoperability+
Partner APIs, webhooks, MiniApps, and national-switch foundations connect a Fedha deployment to approved external participants and rails.
03/ 03
Follow the design into the implementation.
Review the operating surfaces, service architecture, and implementation context behind the product.
03 evidence areas01Client-informed product core+
The reusable architecture has been exercised through a client-specific implementation while the public Fedha brand, configuration model, and client confidentiality remain separate.
02Multi-channel operating proof+
Customer and business mobile, web, USSD, merchant, agent, administration, reporting, and developer workflows have implementation and UAT evidence.
03Governed financial backbone+
Ledger, approvals, payouts, audit retention, biller operations, KYC/AML, notifications, interoperability, reconciliation, and recovery controls sit behind the product surfaces.
One product. Connected layers. Traceable by design.Follow the product journey
From signup to settled.
- 01
Provision
Set up the brand, market, regulatory pack, channel mix, workspace theme, data boundaries, and operating roles for the deploying institution.
- 02
Configure
Map wallets, KYC tiers, limits, paybills, merchant tills, settlement accounts, agent hierarchy, fees, approvals, and notification channels.
- 03
Operate
Run customer transfers, merchant payments, agent cash-in/cash-out, float purchases, payouts, statements, support, and admin decisions through the platform.
- 04
Reconcile
Turn transaction activity into customer, merchant, settlement, statement, journal, and BI views with audit-ready evidence.
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.
Workspaces
- Customer
- Organization
- Merchant & agent operations
- System admin
- Developer
- Reporting
Core platform
- Wallets
- Ledger
- Transaction routing
- Fees
- Settlement
Operator services
- Customer 360
- Biller operations
- Agent & super-agent networks
- KYC/AML
- Audit & reconciliation
Channels
- Native customer & business apps
- Web portals
- Customer / agent / organization USSD
- POS
- SMS / email / push
BEYOND THE INTERFACEWhat does Fedha
What does Fedha
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
- Wallet customers, agents, merchants, operations teams, compliance/admin teams
- Regions
- Multi-jurisdiction by configuration; regulatory packs and rails selected per client
- Rails
- Mobile money, trust accounts, merchant paybills/tills, bank interfaces, and partner-approved future corridors
- Integration surfaces
- Customer app, web app, APIs, webhooks, statements, reports, exports
Client boundary
Brand, roles, policies, data stores, rail configuration, and operating context stay explicit across product surfaces.
Transaction controls
KYC tiers, limits, duplicate protection, transaction challenges, passkeys/PIN, audit events, and ledger posting wrap money movement.
Ledger integrity
Posting, account provisioning, holds, reversals, duplicate protection, and projections form the balance source of truth.
Operator evidence
Customer, merchant, agent, organization, settlement, journal, statement, and admin views expose evidence for support, reporting, and review.
What to confirm before a pilot
- Fedha is for operators with a licensed or partner-backed route to run mobile money or e-money services.
- Walkthrough and pilot scope are aligned capability by capability so teams know what is ready, what is partial, and what needs market-specific work.
- Cross-border, card, CBDC, and approved digital-asset additions require separate licensing, risk, counterparty, and regulator review.
The next move is yours
Start with the Fedha demo.
Review the demo flow, then request the access path that matches your team: walkthrough, technical review, partner scoping, or implementation planning.