Chasing invoices is unpaid work. Taking a card at booking removes most of it permanently.
TL;DR Deposit at booking, card vaulted with your processor, balance charged on completion with notice. Never store card details yourself. State the terms up front and the objections mostly disappear.
Why unpaid invoices happen
Rarely bad faith. Usually friction and time.
- The job is done, so the urgency is gone.
- Paying requires an action they have to remember.
- The invoice arrived by email and got buried.
- Nothing bad happens if they wait.
Card on file removes all four. The payment happens without them doing anything.
Deposit structure by job type
| Job | Deposit | Reason |
|---|---|---|
| Diagnostic or call-out | Full fee upfront | Small, and it eliminates no-shows |
| Standard repair | 0 to 25% | Card on file often enough |
| Job with ordered materials | Cost of materials, minimum | You are exposed if they cancel |
| Large project | 25 to 40%, then milestones | Cash flow protection |
| Emergency call-out | Card on file always | Highest cancellation risk |
The rule. Never be more financially exposed than the customer. If you have paid for materials and they have paid nothing, the risk is entirely yours.
Vaulting, done legally
Never store card numbers yourself. Not in a spreadsheet, not on a form in a folder, not in your CRM notes.
Use tokenised storage through your payment processor. Stripe, Square, and every field service platform with payments built in do this. You store a token, they store the card, and you are outside most of PCI scope.
Requirements
- Explicit written consent to store and charge the card. A checkbox at booking with clear terms, or a signed authorisation form.
- State exactly what you will charge and when. “Balance charged on completion” or “no-show fee of $X if cancelled with less than 24 hours notice.”
- Send a receipt for every charge, automatically.
- Let them remove the card on request without friction.
Get advice on your local rules. Consumer protection and card storage requirements vary by state and country. This is not legal advice.
The script that removes the objection
Say it as normal practice, not as a negotiation.
We hold the appointment with a card on file. Nothing is charged today. The balance goes through when the work is signed off, and you get a receipt straight away. If you need to cancel, just give us 24 hours.
Why it works. It states what happens, when, and what they control. Framed as standard, most people simply agree.
When somebody refuses. Some will, and it is information. Offer an alternative: pay the deposit by bank transfer, or pay in full on the day before work starts. If they refuse everything, that is a strong signal about how the invoice would have gone.
Automating milestone billing
For longer projects, charge in stages rather than one large invoice at the end.
A standard structure
- Deposit at signing. 25 to 30%.
- Materials milestone. Charged when materials are ordered.
- Progress milestone. At a defined, visible stage.
- Completion. Balance, on sign-off.
Make each trigger objective and stated in the contract. “On delivery of materials to site” is verifiable. “When we are about halfway” is an argument waiting to happen.
Notify before charging. A text 24 hours ahead. “Charging the materials milestone of $X tomorrow as scheduled.” That single message prevents almost every chargeback.
Chargebacks, and how to avoid them
A chargeback costs you the money plus a fee, and too many will threaten your merchant account.
Prevention
- Recognisable descriptor. Your business name as it appears on the card statement should match what they know you as.
- Notify before every charge.
- Receipt immediately after.
- A signed authorisation on file that you can produce.
- Photos of completed work, dated.
- Respond to disputes fast, with the documentation.
The descriptor issue causes more chargebacks than fraud. If your legal entity name differs from your trading name, customers do not recognise it and dispute in good faith.
Onboarding rules that make it stick
Put the payment terms in front of the customer three times before the first charge.
- At quoting. In the written quote, in plain language.
- At booking. In the confirmation message.
- Before the charge. The notification text.
Repetition removes surprise, and surprise is what produces disputes.
What changes when you do this
- Days sales outstanding collapses. Most of the chasing disappears.
- No-shows drop, because there is now something at stake.
- You stop being a lender. Materials are no longer financed out of your pocket.
- Admin time falls. No statements, no reminder calls, no awkward texts.
And a small number of customers will leave. Overwhelmingly the ones who were going to pay late anyway.
Add a card-on-file requirement to your next ten bookings and see how many object. Most owners are surprised how few, and how much time it gives back.
Not a tech-savvy pro? That is what we are here for. [CALL NOW]