Version 2.0.0. Effective 15 June 2026.
Scope: this Payout Policy explains how Worker earnings reach a Worker's South African bank account. It applies to every Worker who uses Sizoro on web or mobile. Read it together with the Worker Terms, Payment Policy, Dispute Policy, Acceptable Use Policy, and Privacy Policy.
1. What gets paid out
Worker earnings on each booking are the labour subtotal minus the 5% Worker commission (rounded up to the nearest whole rand), plus 100% of any tip the Employer added to that booking. Tips are not subject to commission and are not rounded. Earnings settle per booking — there is no batch and no separate payout cycle.
2. Worker earnings are a payable, not a stored-value product
Worker earnings are a payable for a real-world service rendered. They are not stored value, not a holding account, and not money the Worker can spend inside Sizoro or transfer to another user. Sizoro does not hold the funds at any point; Paystack routes the Worker's share directly to the Worker's Paystack subaccount at capture, and Paystack settles the subaccount to the Worker's South African bank on its standard cycle.
3. Automatic per-booking settlement
Worker earnings settle automatically per booking. When a booking is captured — either because the Employer confirms completion or because the 24-hour auto-confirm window has elapsed — Paystack executes a single capture-with-split that routes the Worker's share (labour subtotal minus 5% commission, plus any tip) directly to the Worker's Paystack subaccount and the Sizoro fees to Sizoro's main account in the same transaction. The Worker's subaccount balance is then settled to the Worker's bank on Paystack's standard settlement cycle, typically T+1 (the next South African business day). Workers do not initiate payouts. There is no payout schedule, no cutoff, and no minimum payout amount.
4. Bank details and subaccount provisioning
A Worker enters bank details once in the in-app bank-details screen. Workers must (a) have verified identity through our identity verification partner; (b) provide a South African bank account in their own legal name (joint accounts and third-party accounts are not supported in MVP); and (c) confirm the bank details are correct. Saving bank details immediately provisions a Paystack subaccount in the Worker's name; the subaccount ID is stored on the Worker profile and is what Paystack routes captured funds to. When a Worker changes their bank details, the subaccount is updated in place. When an account is suspended or closed, the subaccount is deactivated so no further captures route to it. There is no separate payout initiation flow.
5. Cleared and pending earnings
Earnings on a booking only settle to the subaccount once the booking is captured (Employer confirms or the 24-hour auto-confirm window elapses). Earnings on bookings that are still in their confirmation window, under dispute, or pending an admin resolution are shown as "pending" in the Worker's in-app summary. Pending earnings are not yet payable and are not stored value.
6. What can delay settlement
Settlement of a Worker's share to the Worker's bank can be delayed for: an active dispute tied to the underlying booking; a tier-5 (`EMPLOYER_AFTER_START`) cancellation under admin review; incomplete or failed bank-detail verification; identity re-verification still in flight; the Worker's account being suspended under the AUP, in which case the subaccount is deactivated; suspected fraud, money laundering, or sanctions screening under FICA; payment reversal risk from a Paystack chargeback or bank reversal of the original capture; a Paystack outage; or records still required for SARS, FICA, or POPIA compliance review. We tell the Worker in-app where a settlement is held and what is needed to release it.
7. Settlement method
Worker share is captured into the Worker's Paystack subaccount and settled by Paystack to the Worker's verified South African bank account. Settlement is made in ZAR only. Where a Worker holds a foreign bank account, settlement is not supported in MVP and the Worker must register a South African account. Sizoro does not settle by cash, mobile-money, cryptocurrency, or any other channel.
8. Failed settlements
If Paystack fails to settle the subaccount to the destination bank because the bank rejected the account, the account was closed, or the bank reports an irregularity, the funds remain in the Worker's Paystack subaccount and Sizoro asks the Worker to correct the bank details. Once the Worker updates and re-verifies the bank details, Paystack retries settlement on its next cycle. Sizoro does not charge a separate per-retry fee — Paystack's standard fees apply and are disclosed in-app.
9. Earnings statements
For every completed booking, Sizoro generates a downloadable PDF earnings statement that lists: the booking reference; the Paystack capture reference; the Worker's subaccount reference; the bank, branch (where applicable), and last four digits of the destination account; the booking date and amount; the labour subtotal, the 5% Worker commission, and any tip; and the cumulative year-to-date totals. The statement supports the Worker's SARS personal-tax return and bookkeeping. Workers can also export a consolidated period statement from the in-app earnings screen.
10. Tax treatment
Worker earnings are paid gross of any Worker income tax. Sizoro does not deduct PAYE, UIF, SDL, or COIDA from a Worker's earnings (workers use Sizoro as independent contractors — see the Worker Terms clause 1). The Worker is responsible for declaring the earnings to SARS and meeting any VAT or income-tax obligation. Where SARS requires Sizoro to issue IT3(b) or similar third-party reporting, Sizoro will do so and notify the Worker.
11. Set-off and recovery
Sizoro may set off, against pending or future Worker share captures, any amount the Worker owes Sizoro that is supported by clear, documented evidence — for example, an admin-ordered correction under the Dispute Policy, a duplicate capture the Worker received in error, or a Paystack reversal applied to that Worker. Set-off is recorded in the next booking earnings statement with a clear description. Set-off does not extend beyond proven amounts and does not draw on the Worker's bank account; it is implemented by reducing the Worker's share on a future capture or by direct Paystack adjustment of the subaccount.
12. Account closure
A Worker may close their Sizoro account at any time. Earnings already captured to the Worker's Paystack subaccount remain payable to the Worker and Paystack will settle them on its standard cycle. Open bookings are closed out under the Cancellation and Refund Policy and Dispute Policy. Once the account is closed, the Paystack subaccount is deactivated so no further captures route to it. Records of earnings, captures, settlements, and statements are retained per clause 13.
13. Records and retention
Worker earnings records — booking reference, Paystack capture reference, Paystack subaccount reference and audit trail, settlement reference, set-off, hold reason, and audit log — are retained for at least seven (7) years to support SARS, FICA, and POPIA compliance.
14. Worker recourse
If a Worker disagrees with an earnings outcome, the Worker should raise it with Sizoro Support (see Support Policy) and may escalate under the Dispute Policy. For unresolved consumer-protection complaints, the National Consumer Tribunal and the National Consumer Commission are available routes. Privacy complaints may be escalated to the Information Regulator.
15. Changes to this Payout Policy
We may update this Payout Policy. Material changes are notified through the app or by email at least 14 days before they take effect.
16. Contact
Earnings support: support@sizoro.com. Privacy: support@sizoro.com.
