Selling on WhatsApp
How to Take Payments Through WhatsApp: A Guide for Small Businesses
By Phesky
For many UK small businesses, WhatsApp is where sales actually happen. Customers ask about availability, agree a price and book a slot in a chat, then the conversation stalls at the awkward question of how to pay. Bank details typed into a message are easy to get wrong, and asking someone to call with their card number is neither safe nor convenient.
A WhatsApp payment link solves that gap. This guide explains how payment links work in a chat, gives a step-by-step example, and covers the clear messaging, payment confirmation, scam awareness and record-keeping that keep both you and your customers confident.
How a WhatsApp payment link works
WhatsApp itself is the messaging channel; the payment happens on a separate checkout page. You create a payment request with your payment provider, copy its link and paste it into the chat. When the customer taps the link, a checkout page opens showing the amount and description, and they pay using a method their device supports.
Because the link is just a web address, the same approach works in SMS, iMessage, email and social-media direct messages. That makes payment links for small businesses a flexible way to collect payments online in the UK without a shop front or a website.
WhatsApp may show a preview card with a title or image under the link, but whether that appears is up to the app. Previews can be missing, delayed or out of date, so your message should make sense on its own.
A step-by-step example
Imagine a mobile beauty therapist agreeing a home appointment with a new client over WhatsApp.
1. Agree the details first
Confirm the service, date, time and price in the chat, and explain whether you are asking for a deposit or the full amount. Share your cancellation and refund terms at this point, before any money changes hands.
2. Create the payment request
Open your payment app and create a request for the agreed amount, with a short description the client will recognise, such as the service name and date.
3. Send the link with context
Paste the link into the chat with a short message: who it is from, what it is for and how much it is. Keep it brief and specific.
4. Check the result yourself
Wait for the payment to show as successful in your own dashboard. Then reply to confirm the booking. If it is still processing or has failed, say so politely and wait rather than assuming it went through.
Using payment links for orders, appointments, deposits and remote sales
Orders: a baker taking a custom cake order can send a link once the design and collection date are agreed. Appointments: a tutor can send a link for a block of lessons after confirming the timetable. Deposits: a decorator can request a deposit to secure a start date, with the balance requested later. Remote sales: a seller who lists items on social media can send a link to a buyer who has asked to purchase.
In each case the link follows a clear agreement. Sending unexpected links to people who have not asked for them is more likely to confuse customers and to look like spam.
Writing clear payment instructions
A good payment message answers the customer's questions before they ask. Include your business name, what the payment is for, the amount, whether it is a deposit or the full price, and what happens next once they have paid. For example: "Hi Sam, here's the link for your £25 deposit for Saturday's 10am appointment. Once it's paid I'll confirm your booking."
Avoid sending several links for the same order, as customers may pay twice. If you need to change the amount, say clearly that the old link should not be used. If the customer cannot see a payment button, suggest opening the link in their phone's main browser rather than inside the chat app.
Confirm payment from your dashboard, not from screenshots
A screenshot of a success screen is easy to fake and can come from an earlier or different payment. The only reliable signal is the status your payment provider records once it has confirmed the payment.
Make it a rule that you deliver goods, release a booking or mark an invoice as paid only after the payment shows as successful in your own account. If a customer insists they have paid but nothing appears, check again later and ask them to contact you rather than accepting the screenshot as proof.
Trust, scams, privacy and refunds
Taking payments on WhatsApp means thinking about safety on both sides of the chat.
Help customers trust your links
Send links only in an ongoing conversation, use the same business name and profile each time, and keep the amount matching what you agreed. Tell regular customers how you take payments so they can spot anything unusual.
Watch for scams
Be wary of buyers who overpay and ask for money back, who insist on paying outside your normal method or who send their own links for you to open. Never share security codes or sign-in details with anyone.
Protect personal data
Keep chats to what you need to complete the sale, and do not ask customers to send card numbers or other sensitive details by message. A hosted checkout means card details never pass through the chat.
Plan for refunds
Explain your refund policy before payment, and refund through your payment provider rather than by a separate bank transfer so the record matches the original payment.
Keep good records
Chats are not a bookkeeping system. Use your payment dashboard as the record of what was paid and when, and note the customer and order alongside it if your tools allow. Matching each payment to a request makes it much easier to answer questions, handle refunds and prepare your accounts.
Taking WhatsApp payments with Phesky
With Phesky, you sign in, connect your own Stripe account, open Get Paid and enter the amount. You can add a product name, a photo and an optional tip prompt. Phesky creates a payment link you can share straight into WhatsApp or any other app that accepts links, along with a QR code for the same request.
Phesky checkout supports Apple Pay and Google Pay only; there is no form for typing in card numbers. A wallet button appears only when the customer's device, browser and wallet set-up support it and Stripe confirms it is eligible. Some in-app browsers, such as those inside messaging and social apps, restrict wallets, so customers may need to open the link in Safari or Chrome.
When the customer confirms in their wallet, Stripe processes the payment as a direct charge on your connected Stripe account. Phesky updates the payment's status from verified Stripe information, not from the customer's screen, and the payment appears in your dashboard. Stripe pays out to your bank on your payout schedule, so payment confirmation is not the same as money in your bank.
Phesky's application fee is £0.16 on a successful payment below £30, and 0.60% on a payment of £30 or more. That is only Phesky's share: Stripe's processing fees apply separately under your Stripe terms, so Phesky's fee is not your total cost. The pricing page shows worked examples that add both together for £10, £30 and £100 sales.
A quick checklist before you send your first link
Before you start taking payments on WhatsApp, make sure your business profile shows a recognisable name and photo, and that your payment account is fully set up so links can actually be paid. Write a short template message you can reuse, with gaps for the service, date and amount, so every request looks consistent.
Decide your deposit and refund rules and keep them somewhere easy to paste into a chat. Test a link on your own phone so you know what customers will see, including what happens if it opens inside the WhatsApp browser. Finally, agree with anyone who helps you that a booking is only confirmed once the payment shows as successful in your dashboard.
Conclusion
A WhatsApp payment link turns an agreed conversation into a simple, secure checkout. Agree the details first, send one clear link with context, confirm payment in your own dashboard and keep refunds and records inside your payment system. To try it, read Phesky's guide to payment links, check the pricing examples and create a free account.