Your customer already opened WhatsApp. Your invoice didn’t.
Sole traders book the work, agree the price and handle the aftermath in one thread. Then payment asks everyone to go somewhere else.
Watch how a one-person business actually gets hired. A message arrives — a referral, a reply to a story, a forwarded number from someone who knows someone. The job gets described in two or three messages. A price is agreed in one more. The date is confirmed with a thumbs up. None of this happens in a CRM, a portal, or an inbox. It happens in a chat thread, on a phone, usually between other jobs.
Then the work gets done, and everything changes. Suddenly the customer is asked to leave the conversation they were perfectly happy in. Open an email. Find a link. Enter a card. Or worse — read a sort code out of a message and type it into a banking app, digit by digit, hoping neither of you has made a mistake.
The hardest part of getting paid is rarely the payment. It is the handover — the moment the conversation stops and admin starts.
The sort code message
Almost every sole trader has sent this message. Sort code, account number, name on the account, and the amount. Often followed by “let me know when it’s gone through”, because there is no other way to find out.
It works, in the sense that money sometimes arrives. But look at what it actually asks of the customer: transcribe two numbers correctly, open a separate app, set up a new payee, complete a security check, and then remember to come back and tell you. Every one of those is a place the payment can quietly stall — not out of bad faith, but because someone got distracted halfway through.
And for the trader, the record of what happened is a chat thread. Which means reconciliation is scrolling.
Why the channel matters more than the button
Messaging is where a large share of UK adults already spend their day, and WhatsApp is consistently reported by Ofcom as one of the most-used communication apps in the country. That is not a marketing detail. It is the difference between a payment request that gets seen in ten minutes and one that sits unopened in a promotions tab.
A request that arrives in the thread where the job was agreed carries context with it. The customer does not have to work out what it is for, or whether it is genuine. They are already talking to you. They were expecting it.
What changes when payment stays in the thread
- The customer never leaves the conversation. One tap, their own banking app, done.
- Paying by bank happens inside the customer’s own banking app, so there are no card details to mistype.
- The receipt lands back in the same thread, so both sides have the same record.
- Chasing becomes a reply rather than a fresh, awkward conversation.
None of this is about making payments exciting. It is about removing the seam — the point where a friendly exchange turns into a task. Sole traders do not need a finance department. They need the last step to be as easy as the first four.
Vcents turns the thread into a payment.
Ask for money in plain English. Your customer taps once, authorises in their own bank, and the receipt lands back in the chat.
How receiving payments works