Security & compliance
Security & compliance, by design.
Financial services live or die on correctness and control. PesaBridge bakes a balanced ledger, KYC, AML, limits, reversals and a full audit trail into the core — not bolted on after launch.
The pillars
Controls that satisfy a regulator and a CFO.
Know Your Customer (KYC)
Configurable tiers from a basic phone-number wallet up to full ID + selfie verification, with per-tier transaction and balance limits, document capture and a review workflow.
AML & monitoring
Sanctions/PEP screening hooks, velocity and threshold rules, and flagging — so suspicious activity surfaces for review and reporting.
Authentication & limits
PIN on every money action, wallet locking after failed attempts, per-transaction and daily ceilings, and biometric prompts on the apps.
Reversals
A single reversal engine unwinds any department — P2P, paybill, buy-goods, agent cash, B2C, float, savings — with a full reason trail.
Audit & reporting
Immutable ledger entries and transaction history, statements and exports, plus regulator-ready report packs.
Data & access
Role-based access in the admin, your own per-operator deployment and database, and signed (HMAC-SHA256) webhooks partners can verify.
The control catalog
Every control, by area — the set a regulator asks for.
These aren't aspirations — each control below is enforced in the platform today and configurable per deployment. Show this list to your central bank.
Per-class ceilings enforced at the single ledger choke-point — no API or app path can bypass them. Every value is operator-configurable per deployment.
Minimum balance (float floor)
A wallet class can be barred from going below a set floor — e.g. agent/merchant liquidity.
Maximum balance cap
Inbound funds are rejected once a wallet would exceed its class ceiling.
Maximum per transaction
The largest single outbound amount, per wallet class.
Daily amount & count limits
Caps on both the total moved and the number of outbound transactions per day.
Monthly amount & count limits
Rolling monthly ceilings for amount and transaction count.
KYC-tier customer limits
Tier 1/2/3 each carry their own per-transaction, daily and balance limits.
Compliance, not theatre
KYC, limits and audit a regulator accepts.
Compliance isn't a screen you add at the end. In PesaBridge it's enforced by the ledger, on every transaction.
KYC is tiered. A customer can open a basic wallet with just a phone number, capped to low limits; raising the cap requires an ID and a selfie, captured and reviewed in the app. Each tier carries its own per-transaction and daily ceilings, enforced before any money moves — so limits aren't a suggestion, they're an invariant. Money cannot leave a wallet without basic identity verification, by design, because account opening with a valid ID is the floor a central bank starts from.
Above that sit AML controls — sanctions and PEP screening hooks, velocity and threshold rules that flag unusual behaviour for review — and a complete, immutable audit trail. Every transaction, reversal and KYC decision is recorded and exportable, with regulator-ready report packs.
And because each operator runs their own deployment and database, your customers' data stays yours: no shared tenant, no shared super-admin, no co-mingling with another institution.
KYC tiers
Security & compliance
Trust is the product.
Financial services live or die on correctness and control. PesaBridge bakes both into the core.
Double-entry by construction
Every movement posts balanced debits and credits — the books reconcile to zero, always.
PIN, KYC & limits
Configurable KYC tiers, per-transaction and daily limits, PIN attempts and wallet locking.
Idempotent & reversible
Idempotency keys stop double charges; a unified reversal engine unwinds any department.
Signed webhooks
HMAC-SHA256 signatures and retries so partner systems can trust every callback.
Full audit trail
Immutable ledger entries and transaction history for regulators and disputes.
Per-country compliance
ID types, KYC rules and tariffs switch with the market, from configuration.
Balanced by construction
The ledger can't drift.
Every transaction posts balanced debits and credits. The sum of the books is always zero — there is no code path that creates or destroys value. Retries carry an idempotency key, so a dropped network call never double-charges. When something must be undone, the reversal engine posts the mirror entries and leaves the original intact for audit.
Σ debits = Σ credits
─────────────────────
deposit agent.float −250
alice.wallet +250
send alice.wallet −100
bob.wallet +100
─────────────────────
net = 0.00 ✓ alwaysWhen something goes wrong
How a reversal is handled.
Nothing is ever deleted. A reversal posts mirror entries through one engine, leaving the original transaction intact for audit — across every department.
Countries you can launch in
Native apps, one platform
Channels — App · USSD · Web · API
Double-entry, always balanced
FAQ
Questions, answered.
Is PesaBridge a platform I share, or my own?
Your own. PesaBridge is a product BridgeERP resells — every operator gets their own deployment, branded and configured for them. No shared database, no shared super-admin.
Which countries and currencies are supported?
Any. Country, currency, language and KYC rules are configuration drawn from the full ISO set — not hardcoded. We have live markets today and stand up new ones without a rewrite.
Does it work on feature phones?
Yes. The full wallet runs over USSD — send, withdraw, pay bill, buy goods, airtime, balance and statements — settling on the same ledger as the apps.
Can I connect my own banks and payment rails?
Yes. Rails are pluggable adapters — banks, mobile money, cards and PSPs — so you connect only what your market needs.
How fast can we go live?
Weeks, not years. Configure your brand and country, wire your rails, then ship your apps, USSD code and web portals from one platform.
Is it secure and auditable?
Every movement is double-entry and balanced to zero, PIN- and KYC-gated, with signed webhooks and a full audit trail for regulators.
Which apps do operators and their customers get?
Four native apps (Android + iOS): a User app for customers, an Agent / Super-agent app for cash-in/out and float, a Merchant app to accept and settle, and a Corporate app for bulk disbursement with maker/checker approvals.
How does settlement and reconciliation work?
Funds settle to the relevant wallet in real time. Every transaction produces balanced ledger entries you can reconcile, with statements and exports, and a GL bridge for your accounting system.
Can it handle loans, savings and group finance?
Yes — overdraft credit, MFI loans with schedules and portfolio-at-risk, goal savings, and savings groups (chama / merry-go-round) are part of the platform and switch on per market.
Do you support bulk disbursement for payroll, aid or subsidies?
Yes. The Corporate app and API run bulk disbursement to thousands of wallets with maker/checker approvals, payee books, scheduling and full reconciliation.
What does it take to run it day-to-day?
A single operator admin console runs brand, tariffs, KYC, the agent and merchant network, the ledger, reversals, support and KPIs — no code required for everyday operations.
Who owns the deployment and the data?
You do. Each operator runs their own deployment with their own database — branded and configured for them. It's a product you resell as your own, not a shared SaaS tenant.
Ready to launch your wallet?
Book a demo and we'll stand up your brand, country and rails — and walk you through the apps, admin and API.