A customer saying, “Send me your bank details and I’ll transfer it later” can sound like a sale completed. For many businesses, it is actually the point where uncertainty starts. Payment requests versus bank details is not simply a choice of how money is received. It is a choice between asking a customer to complete a manual task and giving them a clear, trackable route to pay.
For a £50 purchase, the difference may be minor. For a £1,000 deposit on a bathroom installation, a £3,500 vehicle repair or a staged invoice for professional work, it can affect cash flow, diary planning and margin. The right approach depends on the payment amount, the customer relationship and how much time your team spends following up transfers.
What sharing bank details asks the customer to do
A manual bank transfer begins with your business sending an account name, sort code, account number and usually a payment reference. The customer then needs to open their banking app, enter or copy the details accurately, choose the amount, add the reference and authorise the transfer.
It is familiar and can work well for repeat customers who know your business and pay regularly. There is no checkout to explain, and some customers prefer the directness of it. But the simplicity is mostly on the business side. The customer still has several steps to complete, and the business has limited control over what happens next.
The amount can be entered incorrectly. The reference may be missing or unclear. A customer might intend to pay after work, then forget. Your office may see money arrive but need to search the bank feed to work out which job or invoice it relates to. None of these issues are unusual, but they create admin at precisely the moment you need certainty.
Sharing bank details also leaves your team with a familiar chasing cycle: sending the details, checking whether the customer has paid, sending a reminder, checking again and reconciling the payment once it arrives. For businesses collecting several larger payments each week, that process soon becomes an operational cost.
How payment requests change the collection process
A pay-by-bank payment request sets out the payment before it reaches the customer. Your business creates a request with the agreed amount and a reference, then sends it by WhatsApp, SMS, email or as a QR code. The customer opens it, selects their bank and authorises the payment securely in their own banking app.
The key difference is control. Instead of expecting the customer to reproduce your payment instructions correctly, you present a specific payment for them to approve. The amount and reference are already attached to the request, which reduces the risk of an underpayment, a missing reference or a transfer being allocated to the wrong job.
Once authorised, the payment moves directly between bank accounts. You receive a clear status update and confirmation, making it easier to release goods, book a fitting date, close a job or send a receipt without waiting for someone to interpret a bank statement.
This does not make a customer pay if they have changed their mind or do not have available funds. No payment method removes that commercial reality. It does, however, remove avoidable friction between a customer agreeing to pay and completing the payment.
A practical example
Imagine a window company collecting a £2,500 deposit before ordering materials. With bank details, the salesperson may write them into a WhatsApp message and ask the customer to use a job number as the reference. The customer may pay that evening, pay the wrong amount or leave the task for the weekend.
With a payment request, the sales team sends a £2,500 request labelled with the customer and job reference before leaving the appointment. The customer authorises it in their own bank app. The business can see the outcome and move the order forward with far less ambiguity.
Payment requests versus bank details for larger payments
The case for a controlled request becomes stronger as the payment value rises. A larger deposit or invoice usually has a clear purpose: reserving a slot, ordering stock, beginning a project or completing work. It deserves a payment process that reflects that importance.
Card payments can be convenient, but percentage-based processing fees can become meaningful on substantial transactions. Manual bank transfers avoid those card-style fees, yet can be slow to collect and harder to reconcile. Pay-by-bank requests sit between the two: they retain the direct bank-to-bank payment route while adding a structured payment journey.
For businesses that commonly collect £250 or more, predictable pricing matters too. A fixed per-payment charge is easier to account for than a fee that rises with every larger job. The exact cost is only one part of the decision, but it should be assessed alongside time saved on chasing, reconciliation and payment queries.
There are cases where plain bank details remain perfectly reasonable. A long-standing trade customer paying a monthly account may already have your details saved and a reliable process in place. If they pay accurately, on time and with a clear reference, introducing a new step may add little value.
But for one-off consumers, deposits taken at the point of sale, final balances after work is completed and overdue invoices, a request provides useful structure. It gives the customer a professional prompt and gives your business a record of what was requested, when it was sent and whether it was paid.
The customer experience matters as much as the method
Some owners worry that asking a customer to use open banking will feel unfamiliar. The best explanation is a straightforward one: the customer is taken to their own bank app or online banking service to approve the payment. They use the security checks already set by their bank, and your business does not see or handle their bank login details.
That is often more reassuring than asking someone to type account information into a message, especially for a high-value payment. The request should clearly show who it is from, what it is for and the amount due. A branded payment page, sensible description and prompt receipt all help the customer feel confident they are paying the right business.
Choice still matters. Some customers will want to scan a QR code in person; others will prefer a WhatsApp message after a quote is accepted. A payment process that works across SMS, email and WhatsApp lets your team use the channel that suits the conversation already taking place.
Build payment collection into the job process
The strongest results come when payment requests are part of the workflow, not an emergency tool used only after an invoice becomes overdue. Decide where a payment needs to be confirmed before the next commercial step happens.
For example, a home-improvement firm may send a deposit request when the quotation is accepted, a second request before materials are ordered and a final request at handover. A garage may send one when the repair is approved and another when the vehicle is ready for collection. A clinic or professional-services firm may use a request to secure an appointment or settle an agreed invoice.
The wording around the request should be direct. Tell the customer what the payment covers, the amount and what will happen once it is received. “Your £1,200 deposit secures your installation date. Please use the payment request below and we will confirm your booking once payment is approved” is clearer than “Please transfer when you can”.
Real-time status tracking also changes how your office works. Rather than asking colleagues whether a payment has arrived, the team can check the request status, send a reminder if needed and keep the payment record alongside the relevant job. Receipts, reporting and CSV exports then make reconciliation less dependent on scattered messages and manual notes.
Choosing the right approach for your business
Ask a simple question: how often does sending bank details create a delay, a query or an admin task? If the answer is rarely, and your payments are small or largely recurring, your current process may be sufficient. There is no value in changing a process that is genuinely working.
If your team is regularly chasing deposits, matching unreferenced transfers or absorbing high card costs on larger jobs, a payment request is worth considering. It gives you a defined amount, an identifiable reference, an approval route through the customer’s bank and a clear record of the result.
Kube Pay is built around this practical need: create a request, send it through the channel your customer already uses, let them approve it securely in their bank app and receive confirmation to move the job on. For working businesses, that is less about payments technology and more about getting paid with fewer loose ends.
The next time a customer is ready to commit, do not leave the payment as an open task on their to-do list. Give them a clear request, make the next step obvious and let your team get on with the work that payment makes possible.