Every question, answered once.

A way to get part of the wages you have already worked for before payday, for one small flat fee, arranged through your employer's payroll. Nothing else is added, and the amount comes off your next pay once.

Link to this answer

No. The money is yours already — you earned it in days you have worked in this cycle. The amount you took, plus the flat access fee you were shown, is deducted once from your next payslip by your employer. There is nothing extra, no ongoing charge, and nothing that grows with time.

Link to this answer

Through your employer. We go live company by company rather than through an app store, because your access depends on your payroll record — that is what tells us what you have earned and where to pay you. If your employer does not offer it yet, send them to us.

Link to this answer

A smartphone gives you the full screen, but it is not required. WhatsApp works, and a USSD code you can dial from any phone works with no data at all. All three do the same thing.

Link to this answer

A South African company built for South African pay cycles, working directly with employers rather than selling to individuals. Every rand that reaches an employee is recovered through that employer's payroll, which is why we can charge a small flat fee instead of a percentage.

Link to this answer

Open the app, choose an amount up to the figure shown on your home screen, pick whether you want it immediately or by the next working day, and confirm. Before you confirm you are shown exactly what you get, exactly what the fee is, and exactly what comes off your pay and when. Nothing moves until you agree to that.

Link to this answer

If you choose the faster option, usually within minutes. Otherwise by the next working day. It goes into the same bank account your employer already pays your wages into.

Link to this answer

Then you are charged nothing at all. The access fee is reversed along with the amount, nothing is deducted from your pay, and your available balance goes back to where it was. If you ever see a deduction for money that did not arrive, tell us — that is a fault, not a rule.

Link to this answer

No, because the payment is already on its way to your bank the moment you confirm. That is why the screen before it states the amount, the fee and the deduction date in full — take a second on that screen rather than needing to undo the next one.

Link to this answer

Usually up to four times per pay cycle, and your employer can set a different number. The total across all of them is still capped by what you have earned so far and by your cycle limit, so several small draws do not get you past the same ceiling.

Link to this answer

Access closes a few days before your employer's payroll cut-off. After that point the deduction cannot make it onto this month's payslip, and money that misses its own pay run would sit outstanding for a whole extra cycle. It opens again at the start of the next cycle.

Link to this answer

One flat access fee per draw, shown in rand before you agree to anything. It depends on the size band of the draw and on whether you want the money immediately — never on how many days are left in the month, and never as a percentage.

Link to this answer

No. The fee is fixed at the moment you confirm, and the figure you agreed to is stored with your authorisation. If the price on your screen was out of date for any reason, the request is refused and re-priced rather than quietly charged at a different number.

Link to this answer

Yes. We add up every access fee you have paid in the cycle, whatever speed you chose, and that one total is capped — however many times you draw. The ceiling is lower for next-day draws than for instant ones, so once you reach it a further next-day draw is free, while an instant draw can still carry a fee up to the higher ceiling. The terms give both figures, and the app tells you before you confirm if a draw has been capped.

Link to this answer

No. There is no fee to the employer, no setup charge and nothing on their balance sheet. They deduct on payday and remit, the same way they already handle other payroll lines.

Link to this answer

Because a percentage punishes the largest draws, which cost us no more to process, and it is hard to state honestly in six languages. A flat fee in rand is a number anyone can check against their payslip.

Link to this answer

A share of what you have already earned this cycle — commonly a quarter, set by your employer. The figure on your home screen is the real answer for you today, and it grows every day you work.

Link to this answer

Four things can hold your number down: the share of your earnings your employer allows, a cap for the whole cycle, a cap on a single draw, and a floor that keeps enough of your pay intact for payday. The 'Why this amount?' screen names whichever one is actually binding for you right now, rather than making you guess.

Link to this answer

Most employers set a minimum time on the job before access opens, often a month or two. It is on their policy, not ours, and it lifts on its own — your screen will tell you the day it does.

Link to this answer

Because you have already drawn some of it this cycle. Your figure is what you have earned so far, minus what you have taken, so it drops when you draw and climbs again each day you work.

Link to this answer

Anything you have drawn comes off your final pay, which by design is always enough to cover it — that is exactly what the limits are there to guarantee. You will not be chased for a shortfall our own rules should have prevented.

Link to this answer

Access pauses when your employment status changes, because the payslip it is recovered from may no longer be there. Your employer's payroll record is what decides this, so their payroll office is the place to correct it if the status is wrong.

Link to this answer

With the mobile number on your payroll record. We send a one-time code to it and that is the whole sign-in — there is no password to remember or lose, and no way for someone to guess one.

Link to this answer

Give it a minute and ask for another one — codes can be slow on a busy network. If nothing comes, the usual cause is that your payroll record has a different number from the one you are typing, and your employer's payroll office is the only place that can fix that.

Link to this answer

Tell your employer's payroll office and it will reach us on the next payroll import. We cannot change it for you: your number is how you sign in, so moving it on a phone call is exactly how somebody else's wages would be handed to whoever asked.

Link to this answer

Yes. Your account settings hold your language preference, and messages we send you follow it. The formal deduction authorisation you sign is currently shown in English wherever we cannot yet guarantee a reviewed translation — a document that important should not be machine-translated.

Link to this answer

Your display name and your language, in account settings. Your mobile number, your bank account and your pay figures all come from your employer's payroll record and can only be changed there — that is deliberate, and it is what stops anyone redirecting your money by contacting us.

Link to this answer

Sign out when you are done — the button is at the top of every screen. Your session stays on that phone until you do, and anyone holding it would see your pay figures.

Link to this answer

Because a staff account can read a whole workforce's pay. Employer and platform staff sign in with an email address, a password and a code from an authenticator app; employees do not need one, because a phone-only account can only ever move that employee's own wages to that employee's own payroll account.

Link to this answer

Contact us and we will reset it after checking who you are. There is deliberately no self-service route: anyone who could reset a second factor from the sign-in screen would not need the second factor.

Link to this answer

Never. We take your payment destination from your employer's payroll record and there is no screen anywhere in this product where an employee can type a bank account number. If anyone asks you for those in our name, by any channel, it is not us.

Link to this answer

The total to deduct from your pay on payday, and that you used the service — the same way they see a medical aid line. They do not see what you needed the money for, and they cannot approve or refuse an individual request.

Link to this answer

They set the rules for everyone — the share of earnings, the caps, how long you must have worked there — and they can stop offering the service. What they cannot do is approve or refuse one person's draw, or see it before it happens.

Link to this answer

We never store it in a readable form. It arrives on the payroll file, is immediately turned into a one-way fingerprint used only for matching, and only the last four digits are kept so support can confirm who they are speaking to.

Link to this answer

Encrypted, and used only by the part of the system that pays you. It appears on no screen anywhere in the product — support and your employer both see only the last four digits.

Link to this answer

Support can enter an employer's portal to help with a problem, and while they are in it they can only read — every mutating action is switched off for them, and both entering and leaving are recorded against their name.

Link to this answer

One extra line on your payroll run each cycle. We send you a file listing what to deduct per employee, you process it with the rest of payroll, and you remit what you withheld. There is no approval queue for you to work through and no money of yours at risk.

Link to this answer

None on your balance sheet. We pay the employee, and we recover it from the payroll deduction you already process. Your finance team's only new obligation is remitting what was withheld.

Link to this answer

Usually under three weeks. Most of that is one payroll export being mapped correctly and your policy decisions being agreed; the rest is telling your staff it exists.

Link to this answer

The share of earned wages your staff may access, the cap per cycle and per draw, how many draws a cycle allows, how long someone must have worked for you before access opens, and how much of a payslip must remain intact. Those settings are versioned, so a draw taken last month can still be explained by the rules that applied then.

Link to this answer

Any of them, through a CSV or SFTP export — that is the first connector and it is deliberately generic, because it works on day one for everybody. Direct integrations with the major South African payroll platforms follow.

Link to this answer

Everyone on the payroll file who meets your rules. People who have left, who are serving notice or who are suspended are excluded automatically, because their status comes across on the same file.

Link to this answer

Whoever runs payroll needs an admin account — they build and sign off the deduction file. Finance usually takes a view-only account. Both are invited by us; there is no self-service sign-up, deliberately.

Link to this answer

That they can use wages they have already earned, before payday, for one small flat access fee that is shown to them in rand before they agree to anything; that it comes off their pay in the same cycle; that they sign in with the phone number on their payroll record; and that nobody from us will ever ask them for bank details or a PIN.

Link to this answer

The deductions page shows the schedule as it stands today: one line per employee, however many draws they took. It keeps moving until access closes for the cycle, and the page says so — the figure is only final at the cut-off.

Link to this answer

Because they are three different acts. Building the file is arithmetic and can be redone all week. Approving is a person taking responsibility for money coming off other people's wages — it freezes the contents and is the only step that cannot be undone. Downloading is just a copy.

Link to this answer

A CSV with one row per employee, using your own employee reference, with plain decimal amounts and every field quoted. It is written that way so a spreadsheet cannot reinterpret a name containing a comma or read an amount as a different number entirely.

Link to this answer

Report what you actually recovered. Whatever is left stays open and is added to the next cycle's file automatically, once and only once. Nothing is written off quietly and nothing is asked for twice.

Link to this answer

Send back the file with the recovered amount per employee. Where a person's payment covers more than one draw, it is applied to the oldest one first, so the earliest closes cleanly rather than leaving everything half-settled.

Link to this answer

Recover what you can from their final pay; that is what the access limits are sized to make possible. Anything genuinely unrecoverable is ours to absorb, not yours, and it never becomes a debit against your account.

Link to this answer

Start on the deductions page: it shows every employee on the schedule and the draws behind each line, and it is the same figure the overview reports — the two are one query, so they cannot disagree with each other. The advances page has the individual transactions with times. If those still disagree with what payroll captured, send us the cycle and we will reconcile it with you.

Link to this answer

Check the mobile number on their payroll record first — it is the only thing they sign in with, and a mistyped digit is nearly always the cause. Correct it in payroll, import again, and ask them to try once more. Nobody can be given access any other way, which is exactly what stops a stranger getting an account.

Link to this answer

Mark them as terminated in your payroll and import it. Access stops immediately, and anything they already drew stays on the schedule for the cycle they drew it in, so it comes off their final pay. We never delete an employee record — their history has to stay explainable.

Link to this answer

The rest of the file still imported — a bad row never blocks a workforce. The import screen lists each rejected row with the reason, usually a missing branch code or an unreadable number. Fix those in your export and upload again; rows that have not changed are left alone.

Link to this answer

Never. People who disappear from a file are marked as no longer employed, not deleted, and a partial file cannot mark anyone at all. A truncated export would otherwise freeze a whole workforce out of their wages.

Link to this answer

Whether anything needs a person: failed payouts, jobs that have given up, connectors in error. Totals come after that, because a figure nobody has to act on should never be above a problem somebody does.

Link to this answer

Because nothing has been scheduled or reported on yet. An empty cycle showing a perfect rate would be the single most misleading number on the platform, so it stays blank until there is something real to divide.

Link to this answer

A new payout is created under a new reference and the advance is posted afresh. It is not a retry of the old one: a failed payout has already been unwound, so re-sending it would move real money against a balance that no longer exists. It is refused after the deduction cut-off, and it passes the same limit checks as a fresh draw.

Link to this answer

A failed job is already scheduled to run again, and the delay before it does exists because something downstream is still broken. Only a job that has given up entirely needs a person, so that is the only one offered a button.

Link to this answer

Read. Entering swaps your view for the employer's, and every action that changes anything is switched off centrally rather than screen by screen. You cannot enter a second tenant without leaving the first, and both moments are recorded against your name.

Link to this answer

That should be unreachable — the database refuses an unbalanced posting at commit time. If it ever appears, treat it as the database's own guard having been removed rather than as an accounting question, and stop writing before investigating.

Link to this answer