Use Cases
Kanall is domain-blind — it does not know what a distributor, driver, student, or vendor is. It provisions accounts, records payments, and tracks ownership. What those things mean is entirely your business logic.
FMCG and trade distribution
Hundreds of distributors paying into a shared account means daily manual matching. With Kanall, each distributor gets a dedicated NUBAN. When they pay an invoice, the payment lands in their account and a webhook fires instantly — invoice cleared, next delivery approved.
Who this fits: Distributors, FMCG manufacturers, pharmaceutical wholesalers, agri-supply chains.
Logistics and freight
Collections from drivers or owner-operators get lost in a shared settlement pool. With Kanall, each driver gets their own account. Payments land with full attribution and weekly payouts settle directly from the confirmed ledger.
Who this fits: Trucking platforms, courier networks, last-mile delivery, freight aggregators.
Gig economy and marketplaces
Matching buyer payments to the right service provider across a large pool is a reconciliation nightmare. With Kanall, each provider has a virtual account. Earnings land directly, balances are visible in real time, and payouts initiate from confirmed funds.
Who this fits: Freelance marketplaces, on-demand service platforms, creator payout systems.
E-commerce checkouts
For one-off order payments, Kanall's one-time accounts let you issue a dedicated NUBAN per checkout. The account closes automatically once the exact payment arrives — no open window, no payment mismatch.
Who this fits: E-commerce stores, invoice-based businesses, ticketing platforms, order payment flows.
School fee collection
Thousands of students paying through a shared account means daily manual matching to student records. With Kanall, each student gets a dedicated NUBAN. Fee payments land attributed, and your system marks the term paid the moment the webhook fires.
Who this fits: Schools, universities, EdTech platforms, exam-fee collection systems.
Savings groups and cooperatives
Monthly member contributions come in through one account and someone reconciles manually every cycle. With Kanall, each member or group gets a virtual account. Contributions land attributed, balances are visible in real time, and payouts go out when the cycle closes.
Who this fits: Cooperative societies, ajo/esusu platforms, group savings apps.
Rental and subscription billing
Rent or lease payments from multiple tenants land in one pool and arrears are tracked in a spreadsheet. With Kanall, each tenant gets a dedicated account. When payment arrives, the ledger records it and your platform marks the lease current — late payers have a visible gap.
Who this fits: Property managers, car rental fleets, equipment leasing, SaaS billing platforms.
The pattern
Every use case above shares the same structure:
- One entity → one virtual account — provision a NUBAN per entity at onboarding
- Payments arrive with attribution — no matching, no reference codes
- The ledger is the truth — confirmed balances are auditable and never lie
- Payouts from the ledger — settle to any Nigerian bank account when ready
The domain changes. The primitive does not.