Taking Payments Away From the Counter | HL Hunt
Taking Payments Away From the Counter
A trades business in a customer's driveway, a stall at a weekend market, a pop-up in a borrowed space, a delivery at the door. Every assumption a fixed counter makes — reliable connectivity, power, a second person nearby, a customer who knows your business name — is absent. Most of what goes wrong is predictable and cheap to prevent, and one setting deserves far more thought than it usually gets: offline mode is not a convenience feature. It's your terminal deciding to extend credit on your behalf, to a customer whose card nobody has checked.
What you'll learn
What's different away from a counter
| Fixed counter | Away from it | |
|---|---|---|
| Connectivity | Wired, with backup | Mobile, variable |
| Power | Mains | Battery |
| Oversight | Others present | Frequently none |
| If it fails | Another terminal | Lost sale |
| Customer recognition | Signage, a location | A name they may not catch |
| Receipt | Printed | Digital, if they give details |
Row four is why this matters commercially. A failure at a counter is an inconvenience; a failure in a driveway or at a market stall is frequently a sale that doesn't happen, because the customer has no second option and neither do you.
Row three is why it matters operationally, and it connects to our controls guide: a counter provides oversight for free by having other people nearby. Away from it, that has to be built into the system deliberately.
Connectivity, the main cause
By a wide margin, and mostly predictable.
Where it degrades:
- Indoors, particularly in older or metal-framed buildings.
- Basements and plant rooms, which trades work in constantly.
- Rural sites.
- Crowded events, where the local network saturates — the signal that tested fine at setup fails at the busiest hour.
- Moving vehicles, between cells.
What to do about it:
- Test the signal before the day where the location is known. A venue's connectivity is discoverable in advance.
- Ask the venue about network coverage and whether other traders have had problems — they'll know, and nobody asks.
- Carry a device on a different network to your primary, which addresses most single-network failures.
- Assume saturation at busy events and plan for the peak rather than the setup hour.
- Have a fallback that doesn't need live connectivity, below.
Item four is the one that catches experienced traders. The reader worked perfectly at 8am and fails at 1pm because two thousand people arrived with phones — which is exactly when the sales are.
Offline mode as a credit decision
The setting that deserves a deliberate decision and usually gets a default.
When a reader stores a transaction to submit later, no authorization has happened. Which means when it's finally sent:
- The card may be declined.
- It may be over its limit.
- It may be expired, cancelled, or reported lost.
- And you've already handed over the goods or done the work.
Per our outage analysis, this makes it an extension of credit decided by a device according to a setting nobody reviewed — and per our pricing analysis, an unpriced one, since you're bearing an expected loss with no compensation for it.
Deciding properly:
| Situation | Reasonable approach |
|---|---|
| Small amounts, repeat customers | Offline with a low limit may be sensible |
| Large amounts | Never offline — use an alternative |
| One-off customers, events | Low limit, accepting some loss |
| Anything you can deliver later | Take the payment properly first |
The fourth row is the underused option. Where fulfilment can be separated from payment — a service booked, goods to be delivered — sending a payment link and completing later removes the risk entirely without losing the customer.
The backup that pays for itself
The highest-return arrangement in this guide.
A single failed sale at a market or a job frequently exceeds a year of the cost of a backup. Which makes the arithmetic straightforward for anyone trading away from a counter regularly.
What a backup should be:
- On a different network to your primary device — otherwise a network outage takes both.
- Independently powered, with its own battery.
- Tested periodically, since an untested backup fails when needed.
- Able to take the same methods, so nothing is lost by using it.
- Known to whoever is working, which means training rather than just equipment.
And the non-terminal fallbacks worth having:
- A payment link sent by text or email, which needs only the customer's connectivity rather than yours — and per our bank payments guide, this works where card infrastructure doesn't.
- An invoice for larger work, which converts an immediate problem into a receivable rather than a lost sale.
- Cash, with the handling considerations that brings.
The payment link is the most underused option because it inverts the dependency — you don't need a signal, they do, and if you're both in the same dead spot you can send it for later.
Keyed entry and what it costs
The habit worth breaking, because it's expensive twice.
Per our channel analysis, how the card is read determines both the cost and the liability, and where you're standing is irrelevant.
- Contactless or chip, card present — treated the same as at a counter.
- Manually keyed — treated as higher risk, typically costs more per our downgrade guide, and carries different dispute liability.
So: tap or dip wherever possible, and treat keyed entry as a fallback rather than a habit. Staff who key by default because it feels faster are costing you on every transaction and shifting liability at the same time.
And per our security guide: never write card numbers down to enter later. That's a stored card number on paper, in a vehicle or a bag, and it's the single worst practice in this area.
Card details written down "to process back at the office"
It creates a storage exposure with none of the protections, it's frequently prohibited outright by your agreement, and it turns a small business into a data breach. Use a payment link or an invoice instead — both take seconds and neither leaves anything written down.
Staff working alone
The oversight a counter provides free, rebuilt deliberately.
What's needed:
- Per-user identification, so every transaction is attributable to a person.
- Refund restrictions — approval required, or no refund capability at all on mobile devices. Per our refunds guide, refund capability away from oversight is a significant exposure.
- Transaction limits per user.
- Visibility that doesn't depend on them reporting — you should see the day's activity without asking.
- Device accountability — who has which reader.
- Prompt removal of access when someone leaves.
The fourth is the one that does most of the work. Per our controls guide, the enabling condition for internal loss is one person controlling a step end to end — and a field worker taking payments and reporting the total is exactly that, unless the system reports independently.
This isn't about distrust, and it's worth saying to staff in those terms: a person handling money alone with no independent record cannot demonstrate they did nothing wrong if a discrepancy appears. The visibility protects them.
Why these transactions get disputed
More often than counter transactions, for reasons that are fixable.
Per our descriptor guide, disputes come disproportionately from customers not recognizing a charge — and a market stall or a mobile trader is precisely the purchase a customer struggles to place weeks later.
- They may never have known your trading name.
- There's no location on the statement to jog memory.
- The purchase was brief and unmemorable.
- They may have no receipt if they declined one.
What reduces it:
- Use the name customers actually see as the descriptor, checked on a real statement.
- Add something identifying where the format allows — a market name, a locality.
- Offer a digital receipt and encourage it, since a receipt in an inbox is searchable.
- Say your business name aloud at the point of sale, which costs nothing.
- Include contact details so they call you rather than their bank.
- Keep your own records per event, per our dispute guide, since evidence assembled later is weaker.
Item four is free and surprisingly effective — a customer who heard the name once is far more likely to recognize it on a statement than one who never did.
The setup
- Choose hardware with good battery life and carry a power bank.
- Get a second device on a different network.
- Set the offline policy and limit deliberately.
- Configure the descriptor and verify it on a real statement.
- Set per-user access, limits, and refund restrictions.
- Enable payment links as a fallback.
- Test connectivity at known venues beforehand.
- Train staff on tap-first, the fallback sequence, and saying the business name.
- Reconcile per event or per route, per our reconciliation guide, while people remember the day.
- Review offline transaction failures periodically to check your limit is right.
Items two and three carry the most value. The backup prevents lost sales and the offline limit caps what a bad day costs — and item ten is what tells you whether the limit you chose was sensible, which most operations never check.
Acceptance that works where the signal doesn't
HL Hunt Pay supports contactless and chip acceptance on mobile readers with configurable offline limits, payment links as a fallback, per-user access and refund controls, and per-event reconciliation reporting.
Frequently asked questions
It shifts risk to you. No authorization has occurred, so the card may fail when submitted — after you've handed over the goods. Set a deliberate limit.
Connectivity, by a wide margin — and much of it is predictable. Venue signal can be tested beforehand, and crowded events saturate at the busiest hour.
Per-user identification, refund restrictions, transaction limits, and visibility that doesn't depend on them reporting. A counter provides oversight free; mobile doesn't.
It depends on how the card is read, not where you are. Tap and chip are treated as card-present; keyed entry typically costs more and carries different liability.
Key takeaways
- Away from a counter, a payment failure is usually a lost sale rather than an inconvenience.
- Event connectivity fails at the busiest hour, not at setup — plan for the peak.
- Offline mode is an unpriced credit decision made by a device; set the limit yourself and review the failures.
- A backup on a different network typically costs less than one lost sale a year.
- Never write card numbers down to process later — use a payment link or invoice instead.
- Say your business name aloud at the point of sale; it measurably reduces later disputes and costs nothing.
One lost sale costs more than a year of backup
Sign up for HL Hunt Pay for card, contactless, and ACH acceptance across fixed and mobile settings, with the same rates, one set of reporting, and fallback options that work without your signal.
This guide is educational and does not constitute legal or compliance advice. Offline transaction rules and limits, interchange treatment of different entry methods, dispute liability, and requirements governing the handling of card data are set by the card networks, your processor, and applicable standards, and vary by category and over time. Confirm the specifics applying to your account with your provider.