Feedback from prospective customers indicates that requiring them to move payroll to a specific bank creates significant resistance.
This is a switching-cost problem, not necessarily a product-quality problem.
HR approves payroll
│
▼
Dexwin calculates totals
│
▼
Customer transfers total payroll
to settlement account
│
▼
Funds reconciled
│
▼
Partner bank distributes salaries
through Ghana payment rails
Customer signs debit mandate
│
▼
Payroll approved
│
▼
Partner bank debits customer account
│
▼
Settlement account funded
│
▼
Payroll distributed automatically
This provides a better customer experience but requires ACH/direct debit capabilities through the banking partner.
interface PayrollDisbursementProvider {
validate();
createFundingRequest();
submitPayroll();
getStatus();
cancel();
}
Today's implementation:
PartnerBankProvider
Future implementations:
EcobankProvider StanbicProvider FidelityProvider HubtelProvider ...
This keeps payroll calculations, tax, approvals, and payslips independent from payment providers.
| Phase | Goal |
|---|---|
| 1 | Pre-funded payroll using existing customer banks. |
| 2 | Add automatic funding via debit mandates. |
| 3 | Add multiple banking partners behind the same interface. |
| 4 | Evaluate direct payment-rail participation only if payments become strategic. |
The bank should be an implementation detail—not a prerequisite.
The easier it is for customers to adopt Dexwin Payroll without changing existing financial processes, the larger the addressable market and the faster adoption is likely to be.