How to Request Payment from a Customer — Without Awkward Follow-Ups

Marcus drives a mobile dog grooming van across South London. After every job he sends the owner a quick text — his Venmo handle, or his bank details — and then he waits. Sometimes the payment comes through in ten minutes. More often he sends a second text two days later. Then a third. Last month he was owed £340 across four clients. All perfectly friendly people who simply hadn't got around to it.

"I feel stupid chasing them," he says. "We've literally just had a nice conversation about their dog. And then I have to turn into a debt collector."

Marcus doesn't have a payment problem. He has a timing problem. The fix is simpler than he thinks.

The Payment Gap

The moment a service ends is the moment a customer's willingness to pay is at its absolute highest. They've just seen the result. The dog smells of lavender, the car is gleaming, the garden looks immaculate. If you can collect payment right then, you'll almost always collect it.

Every hour that passes makes payment harder. Not because customers are dishonest — most aren't — but because life intervenes. They get back to work. Something comes up. They intend to pay later and then genuinely forget. A payment request that arrives three days after the job is competing with twelve other notifications, and the memory of the transaction is already fading.

Most small service businesses have no clean way to collect at the right moment. A point-of-sale terminal works fine for a shop but it's impractical for a mobile operator. Invoicing software sends a PDF to an email inbox the customer has to open on a different device. Bank transfer requests land in a thread separate from the conversation. None of these are bad, exactly. They're just slow. And slowness is expensive.

How a Payment Request Workflow Works

The fix is straightforward. When Marcus finishes a job, he opens his conversation with that customer — the same thread where they arranged the appointment — and triggers a payment request from it. He sets the amount. The customer receives a secure Stripe or Square checkout link directly inside that conversation.

The customer taps the link. They're already in the conversation. The job is fresh. They pay in under 30 seconds, using a card saved on their phone. A receipt is generated automatically and delivered to their email. Marcus gets a notification that the payment has cleared.

No POS terminal. No separate invoice. No follow-up text.

Here's the thing: the payment lives where the relationship lives. The customer doesn't have to open a different app, log into a portal, or track down an invoice email. The link is right there, in the thread where they told Marcus their dog is nervous around clippers. Friction drops low enough that most people just pay.

Fixed Amount vs. Open Amount

Payment workflows can run in two modes. Understanding the difference saves confusion.

Fixed-amount mode is for standard services with a set price. Marcus charges £55 for a medium breed full groom. He sets that amount once, and the payment request fires with £55 every time. There's no decision required in the moment — it's consistent, fast, and looks professional.

Open-amount mode is for variable jobs where the total depends on what was done. A car detailer who adds ceramic coating on top of a standard clean, a handyman who works hourly — these providers know the total at the end of the job, not before. In open-amount mode, the customer sees the total that was agreed verbally and simply pays it. No ambiguity, because the amount was established in conversation before the request arrived.

Both modes produce the same outcome. The payment link lands in the thread, the customer pays, the receipt is automatic. The only difference is where the number comes from.

No App to Download

One of the quieter advantages of this approach is what the customer doesn't have to do. They don't need to download an app. They don't need to create an account on a payment platform. They don't need to leave to a separate website and find their way back.

This matters more than it might seem. Every extra step between "customer decides to pay" and "payment processed" is a moment where that decision can stall. An app download introduces enough friction that a meaningful share of customers will defer it. And deferral is exactly how you end up sending three reminder texts.

A link that opens in the phone's browser, connects to Apple Pay or Google Pay in a single tap, and closes back to the conversation — that's genuinely close to zero friction. That's the difference between collecting on the day and chasing at the end of the month.

The Receipt Handles Itself

Every payment through this workflow generates a receipt automatically. A real one: business name, date, amount, description of the service. It goes straight to the customer's email. Marcus doesn't have to do a thing.

This removes a small but genuinely annoying piece of admin from the end of every job. No copying and pasting into a receipt template. No remembering to send a follow-up email. No customer texting three weeks later asking for proof of payment for their insurance claim.

Plus, Marcus gets a complete payment record without maintaining a spreadsheet. Every transaction is timestamped and linked to the customer conversation. At the end of the month, his paid and unpaid jobs are visible at a glance.

The Compound Effect

The payment-at-the-moment approach has a side effect that most business owners notice after a few weeks: the tail of late payments effectively disappears. Not because customers suddenly become more reliable — but because the friction of paying has been removed at the exact moment they were most inclined to do it.

Marcus sent 47 payment requests in his first month using a workflow. Forty-four cleared on the same day. Two cleared within 48 hours. One client — a regular who'd always been a slow payer — paid within four minutes. "I didn't even get home before I got the notification," he says.

That three-minute window matters. Most people, when they receive a payment link while the job is still fresh and they're already on their phone, will simply tap it. That instinct is all you need to capture.

Where This Fits in the Payments Picture

Payment requests are the foundation of a clean payment operation for a small service business. Once this mechanic is in place, you can build on it.

If your business takes appointments, collecting a deposit before the booking is confirmed is the natural next step — it uses the same payment link mechanic but fires before the job rather than after, and it largely eliminates no-shows. If you bill the same clients repeatedly — personal trainers, tutors, coaches — a monthly billing workflow that sends into the existing conversation thread handles the whole cycle without you touching a spreadsheet.

The starting point is the same for all of it: a payment request that goes where the customer already is, at the moment they're most ready to pay.

---

See how Blinko handles payments and workflows for service businesses → · Start your 30-day free trial → — no credit card required.