Pay the workers your bank can't reach
In South Africa and across emerging markets, a significant share of workers don't have bank accounts. Your payroll system can't pay them. Your bank can't pay them. SOLnova does — through wallets, prepaid cards, and alternative payout rails — with the same review and approval controls as every other batch.
| Beneficiary | Amount | Status |
|---|---|---|
| AVAnya Volkova | R 12 480,00 | OK |
| MCMarius Coetzee | R 8 920,00 | New line |
| TMThandi Mbeki | R 15 100,00 | IBAN changed |
| JPJohan Pretorius | R 6 540,00 | OK |
The payouts nobody else solves
Payroll software requires a bank account
If a worker doesn't have one, they don't get paid.
Bank portals require a bank account
Same problem, different layer.
Cash is unsafe and untraceable
Withdrawing cash to hand out to workers exposes everyone — and leaves no audit trail.
Alternative rails exist but are fragmented
Wallets, prepaid cards, and instant-payout providers each have their own portals, files, and approval flows.
One workflow, three rails
Unified payout in one batch
A single batch can pay bank-account workers, wallet recipients, and prepaid card holders — together.
Same controls as every batch
New-beneficiary flagging, change tracking, risk scoring, audited approval. Not a weaker workflow.
Auditable across rails
One audit log covers bank, wallet, and card payouts — same record, same reviewers.
Unbanked workflow — one approval, three rails
Source data flows through the same review, tracking, and approval steps. The approved batch then routes per beneficiary to bank, wallet, or prepaid card.
Key features
- Per-beneficiary rail preference, stored once.
- Multi-rail batch execution from a single approved file.
- Wallet provider integrations (partner-specific).
- Prepaid card issuance integration on request.
- One audit log across all rails.
Common questions
Are wallet and card payouts subject to the same compliance as bank payments?
Yes. Every partner rail is regulated; SOLnova enforces KYC and AML checks per partner requirements.
Can a single batch mix bank, wallet, and card payouts?
Yes. That's the core feature of this use case.
What if a worker switches from cash to wallet to bank account over time?
Each worker has a rail preference that can be updated. The change is logged in the audit trail; the next batch routes correctly.