Driver payments
Pay your drivers on a schedule everyone can see
Drivers request what they are owed. You approve it. One Direct Debit collects the run and every driver is paid automatically once it clears — with a date they were told in advance and a record of every decision along the way.
For licensed private hire operators. Driver payments is switched on per operator, by us.
How a payment reaches a driver
- 1
The driver asks
A driver submits what they are owed from their dashboard, with a job reference and any evidence. It lands in the operator's queue with the pay run it is heading for already attached.
- 2
The operator decides
Approve it, adjust it with a reason, or reject it. Every move is stamped with who did it and when, and the driver sees the outcome and the reason. Once you approve, it is a commitment — an approved request goes into the run.
- 3
The run closes
Approved requests collect into a scheduled pay run. It stops accepting on its cut-off date, and the operator confirms it in one click — one Direct Debit for the whole run, not one per driver.
- 4
Everyone gets paid
Once the collection settles, each driver is transferred their amount automatically. Not before — money only moves to drivers out of funds that have actually cleared.
For operators
One run, one collection, one record
- One collection, not twenty
- A pay run is a single Direct Debit off your account, however many drivers are in it.
- A queue instead of a WhatsApp thread
- Requests arrive in one place with job references and evidence attached, and nothing is approved twice.
- A schedule your drivers can read
- Set the cadence and the cut-off once. Every driver is told their payment date when they submit, not after.
- An audit trail you did not have to keep
- Every approval, adjustment, rejection and payment is recorded against the request, permanently.
For drivers
Know what is owed, and when it lands
- A date, up front
- The payment date is shown when the request is accepted, and it is the date the money can actually arrive — not the day it was approved.
- One account, every operator
- Set up payouts once. The same account receives from every operator you work with.
- You can see where it is
- Requested, accepted, processing, paid — with the reason attached if an amount changed.
- A way to push back
- If an operator adjusts your amount, you have 14 days to dispute it. Nothing is collected on a disputed request until it is resolved.
Why should I use it?
Paying drivers is not hard. It is just slow, repetitive, and easy to get wrong when there are twenty of them and it is Friday night.
Far less admin
One list to review and one click to pay everyone in it. No spreadsheet, no bank transfers one at a time, and no working out who you have already paid this week.
One place to see what you owe
What has been asked for, what you have approved, what is going out on the next run and what has already been paid — with the totals, on one screen.
No manual payments
You never key in a sort code or an account number. Your drivers set up their own account once, and each run pays every one of them the right amount on its own.
Fewer messages asking where the money is
Drivers can see their own requests and the date they will be paid. Most of the chasing stops because the answer is already in front of them.
Money leaves on a date you know
One Direct Debit for the whole run, on a schedule you set. Far easier to plan around than a scatter of transfers going out whenever someone asks.
A record, if a payment is ever questioned
Every request, every change to an amount and every payment is kept against the driver and the job. If someone queries what they were paid months later, the answer is already written down.
Easier to keep good drivers
Drivers talk about who pays properly and who does not. Paying on a schedule they can see, with a date they were told in advance, is one of the cheapest reputations to earn.
Timing and cost
The bits worth knowing before you commit
- About 4 working days
- From confirming a run to the money reaching your drivers. Bacs counts working days, not calendar days. Your first run on a new Direct Debit takes longer — around seven — because the mandate has to activate first.
- A percentage, per payment
- A platform fee is deducted from each driver's payment, and it is shown on every line of the run so both sides can see it. You are collected the gross; the driver receives the net. The rate is set per operator when your account is opened.
- A Direct Debit, not a card
- You set up one Bacs mandate from your business account. Drivers are paid into their own accounts through Stripe, which they connect themselves — you never handle their bank details.
Getting set up
There is no self-serve signup for this one. We open operator accounts by hand, so that every business collecting money through the platform is one we have checked.
- 1
Claim your company
Find your listing in the directory, or add it. You will be asked for licence details and documents.
- 2
We verify and approve the claim
That is what makes you the owner of the listing, and it is the thing everything else hangs off.
- 3
We switch driver payments on
Your operator account is created and the driver request queue opens.
- 4
Set up your Direct Debit and invite your drivers
One mandate from your business account, then share your invite code. Drivers connect their own payout account.
Already claimed it? Check its status.