Layered, not siloed
Channels never own a second database. The application services own products; the ledger owns money.
Architecture
One ledger under every channel
Staff desks, the client portal, USSD, and the API are not separate products. They are channels onto a tenant-scoped core built for Ghanaian credit operations.
Channels, application services, tenant-scoped Postgres, and Ghana payment rails.
What this layer does
- Staff portal, HP specialist desks, and white-label client apps post to the same accounts.
- Origination, collections, hire purchase, savings, payroll, and BoG packs share one client file.
- Postgres row-level security plus branch RBAC — institutions never share a customer record.
- Paystack, MoMo, SMS, Ghana Card, bureau files, and GPS events arrive as ledger postings.
- Geo-redundant hosting and edge caching keep field officers productive on 3G.
- Idempotency keys on disbursements and collections so payment retries never double-post.
Channels, application services, tenant-scoped Postgres, and Ghana payment rails.
- One client, many products
- Honest PAR from posted receipts
- Examiner samples from the audit trail
Tenant-scoped Postgres
Every table carries tenant_id. RLS policies enforce isolation even if an application query is wrong.
Evented integrations
Webhooks and inbound receipts are durable. A dropped MoMo callback can be replayed without duplicating cash.
Stateless app tier
Horizontal scale for month-end and collections blasts without moving the book of record.
Geo-redundant
Multiple availability zones, automated failover, and a 99.99% uptime target.
Dual control built-in
Disbursement, reversal, and configuration changes require the second pair of eyes your policy already demands.
Watch
Product walkthrough
Ninety seconds through origination, collections, the client portal, and month-end — filmed as a visual tour of the operating model.
Step 1
Onboard with Ghana Card KYC
Capture identity, photos, and next-of-kin once. Reuse the file across loans, savings, and hire purchase.
Step 2
Originate and schedule
Price reducing-balance or flat-rate products, lock a schedule, and disburse with dual control.
Step 3
Collect in the market
SMS, USSD, MoMo, and field queues post to the same instalment so PAR is honest.
Step 4
Let customers self-serve
The client portal shows the live savings balance, loan due, and HP statement — then takes payment.
Step 5
Close the month on the same ledger
Provisions, MPR packs, payroll, and the GL share one book examiners can sample.
Ready to modernize your institution?
Start a 14-day trial or talk to sales about hire purchase, microfinance, and multi-branch cores.