Skip to content
LakeOps

Cards on file and deposits: getting paid without chasing

Deposits narrowly, cards on file broadly. Why a deposit belongs on first-year customers and big one-offs, why a card on file quietly ends the chase for the standing list — and why the consent wording is the whole game.

· 6 min read

Should you take deposits? Should you keep cards on file? For a seasonal customer list, the short answers are: deposits narrowly, cards on file broadly. A deposit earns its keep on first-year customers and big one-off work, where you have no history and real exposure. A card on file earns its keep on the standing list — the customers you serve twice a year, every year — because for them it quietly ends the chasing altogether.

Both answers come from the same fact about this trade: your customers aren’t strangers. Most of the list has paid you reliably for years, and a payment setup designed for strangers — deposits from everyone, terms, follow-up calls — taxes your best customers to protect you from a risk they don’t pose.

Deposits: a commitment test, not a cash-flow plan

Where a deposit belongs: the new customer with no history, the large custom job, the work that requires you to buy materials or book a crane. There it does two jobs — it filters out the tire-kickers before you’ve scheduled a boat, and it shares the risk on work you can’t easily resell if they vanish.

Where it doesn’t belong is the standing list. Asking a ten-year customer for a deposit on the same install they’ve paid for ten times reads as distrust, and operationally it turns every job into two transactions — two chances for a check to be in the mail, twice the bookkeeping, for money that was never at risk. If you do take one, the record-keeping should be boring: in LakeOps a payment is recorded against the job, so a deposit in April and the balance in June is simply two payment rows against one job, and the balance always shows what’s actually left. Nobody reconciles anything by hand.

Cards on file: what actually changes

A card on file changes the shape of the season’s end. Without one: finish the job, send the email, wait, and eventually spend office time on the slow ones. With one: the crew finishes, the job prices itself, the card is charged for the balance, and the customer gets the same completion email — what was done, the crew’s photos, the amount — plus a receipt when the money lands. Nothing is ever charged before the work is finished. For a customer you visit twice a year, that’s the difference between two collection cycles a year and none.

Consent is the whole game

The customer puts the card there — you can’t, and shouldn’t want to. In LakeOps, a card gets on file one way: the customer, paying online from a completion email, chooses to leave it for next time. There’s no screen where your office types in a card number.

Why the wording matters: “keep my card” means different things to different people, and the version that survives a dispute is the one written down. LakeOps keeps the exact words the customer agreed to, with the date and time — not a checkbox, the full text as it read that day — so “I never agreed to that” has an answer. And removal is self-serve, from the same link they used to save it, no phone call to your office required. A card a customer can’t easily take back is a card they’ll resent leaving, and resentment on the standing list costs more than chasing ever did.

Tell customers about it the honest way: in the renewal letter or the completion email, as a convenience they can take or leave. “Most of our customers leave a card so there’s nothing to remember” — only if that’s true of your list. Never enroll by default, and never make it a condition of service.

When the card declines

Expired, canceled, over the limit — with a list of seasonal customers, a few declines a season is a certainty, not an incident. The charge fails, the job simply stays unpaid, and the customer gets an email so they can pay it themselves. From there it’s ordinary outstanding money on the balances report, aging from the day the work finished, like any other unpaid job. No drama, and no one from your office discovering it in September.

What it costs, and the other door

Payments taken through LakeOps carry a 1% service fee per payment, shown as its own line so you always know what it was, alongside the standard card and bank rates. And you’re welcome to bill your customers yourself instead — take the check at the landing, record it against the job, and there’s no service fee at all. A recorded check is the same first-class payment as a card paid online; everything downstream reads them identically. Plenty of shops run both at once, because their customers do.

February is when to decide

This is a policy, and policies set mid-season become exceptions. Decide it now: deposits for new customers and one-offs above a threshold you pick; cards on file offered to the standing list, on the customer’s initiative, starting with this spring’s completion emails. By fall, the share of the list that opted in is work your office no longer does — and the chase, when it still happens, happens only where it was ever needed.

How a card on file works · How getting paid works in LakeOps

See it with your own shoreline on the screen

Half an hour. A few of your properties loaded, the pins dropped, a season run through it. If it’s not obviously better than what you’re doing now, that’s the answer you’ll get.

Nothing to book and nobody to talk to — you're in within a minute. Or have us walk you through it if you'd rather see it on your own shoreline first.