How On-Site Payment Capture Works
For a shop coming off paper invoicing, collecting payment before the technician leaves the driveway is usually the single change that pays for the whole platform — and it does so in the first month rather than the first year.
Paper invoicing puts three to six weeks between finishing a job and having the money. On-site capture compresses that to the same day.
The mechanics are easy. The hard part is the conversation, and it is solved by setting the expectation when the appointment is booked rather than at the moment the technician asks.
The cash conversion problem
Follow a paper invoice through a typical week and the delay is not one bottleneck but five, each reasonable on its own.
The working capital effect is worth calculating. A shop invoicing $120,000 a month with a four-week collection cycle has roughly $120,000 permanently outstanding. Compressing that to same-day releases most of it once, as a one-off improvement to your bank balance — and then keeps it there.
What the workflow actually looks like
Six steps, and the whole sequence takes two or three minutes.
- Technician completes the work order in the app — parts, labour, findings, photos
- The system builds the invoice from the price book, so the figure is not improvised
- The customer sees it on the screen, itemised, before anything is charged
- Payment is taken — card, ACH, cheque or cash, all recorded the same way
- Customer signs on the device
- Receipt is emailed automatically and the record syncs to accounting
The third step matters more than it looks. A customer who watches an itemised invoice being assembled from a published price book has a different experience from one handed a total. It also removes most billing disputes before they exist.
The four methods
| Method | Best for | Note |
|---|---|---|
| Physical card reader | Most service calls | Tapped or dipped cards attract the lowest processing rate |
| Phone camera capture | When the reader is in the other van | Usually treated as keyed-in, so a higher rate |
| Payment link | Customer not present, or paying later | Better than posting an invoice; worse than collecting on site |
| ACH bank transfer | Replacements and commercial invoices | Flat fee rather than a percentage — the difference is large on big tickets |
The rate difference between a tapped card and a keyed one is real and it accumulates. And on a five-figure replacement, ACH instead of a card can save several hundred dollars on a single job — the arithmetic is set out in payment processing fees.
The conversation, which is the actual difficulty
Technicians are not reluctant to take payment because the software is hard. They are reluctant because asking a homeowner for money in their own kitchen feels awkward — and if it feels like a request, some customers will defer it.
Set the expectation when the appointment is booked. “Payment is taken on completion, and our technician can take card or bank transfer.”
Now the technician is not asking for anything. They are following a process the customer already agreed to, and the awkwardness disappears entirely.
Reinforce it in the confirmation message and the day-before reminder. Three mentions before anyone arrives is enough that nobody is surprised.
Two more things that help:
Give technicians a script, not an instruction. “I’ll get the invoice up on the screen and we can settle it while I’m packing up” is a sentence someone can say without discomfort. “Collect payment on site” is a policy that leaves them to improvise.
Never make the technician negotiate. If a customer genuinely cannot pay, the technician sends it to the office and leaves. Asking a technician to handle a payment dispute in a driveway is how the whole practice gets quietly abandoned.
Deposits on replacements
Different problem, same mechanism. A $12,000 system replacement usually involves a deposit at signing and the balance on completion.
What the system should handle: taking a percentage deposit against a signed proposal, recording it against the job, and showing the correct remaining balance at completion without anyone doing arithmetic.
Worth checking in any trial, because it is a workflow some platforms handle awkwardly — and a deposit recorded as a separate unlinked payment is a reconciliation problem every time.
Saved cards for agreements
For recurring maintenance billing, the card has to be stored — and one detail decides whether that works over time.
Ask whether the platform supports automatic card updating. Cards expire and get reissued after fraud. Without automatic updating, your recurring billing accumulates a silent failure rate that looks like customers cancelling and is actually plumbing.
This is a common and avoidable way to lose maintenance agreements, and it connects directly to the renewal leakage described in service agreement management.
Financing at the point of sale
For replacements, offering monthly figures alongside the total changes what feels affordable. Integrated financing means a customer can be approved on the technician’s device rather than being told to arrange something and call back.
Two honest cautions. Always show the total as well as the monthly figure — a monthly cost presented alone reads as concealment, and customers notice. And financing terms, fees and approval criteria are set by the lender rather than by you, so what a customer is agreeing to should be visible to them before they sign.
What breaks it
No signal. The app has to queue the payment and process it when connectivity returns, or take an offline authorisation. Test this specifically — the offline behaviour of payment capture is not the same as the offline behaviour of the rest of the app.
Dead battery. A phone that dies at 3pm cannot take payment for the rest of the day. Chargers in every van.
Technician avoidance. If some technicians collect and others do not, the practice erodes. It has to be a requirement with a stated exception process, not an encouragement.
The office undermining it. If a customer can phone the office and say “just send me an invoice”, and the office agrees, everyone learns the policy is optional. Have an answer ready that is not a refusal: the payment link, sent while they are on the phone.
Frequently asked questions
How much faster do you get paid with on-site capture?
How do I stop the payment conversation being awkward?
What if a customer refuses to pay on site?
Is it cheaper to tap a card than to type the number in?
Should I take ACH instead of cards?
What happens to saved cards for maintenance agreements when they expire?
What to do next
- Calculate your current collection cycle. Average days between job completion and payment received. That number is your case for change.
- Add the payment expectation to your booking script and your confirmation messages, before changing anything technical.
- Write the technician script and the exception process, so nobody has to improvise.
- Test payment capture with no signal, and put chargers in every van.
- Payment processing fees — what each method actually costs
- Moving from paper to software — why this is phase one of a rollout
- How accounting integration works — getting payments into the books correctly
The collection timeframes and figures here are illustrative examples used to explain a principle, not measured benchmarks. Payment methods, offline behaviour, deposit handling and financing partners vary between platforms and by jurisdiction. Financing terms are set by the lender, not the contractor. Confirm capabilities during a trial and read financing terms before presenting them to customers.