Accept crypto payments as a home services company: your cash register is a van in someone else's driveway

Why a home services company collects its money in the worst place a business can collect money

Almost every business gets paid at a place it controls. A restaurant has a till. A clinic has a reception desk. An online store has a checkout page it wrote itself. A home services company has none of that. Its point of sale is a driveway, a boiler room, a crawl space, a roof, a hallway with the water still running — and the person operating it is a technician who was hired to fix things, not to run accounts receivable.

Think about how a single day actually goes in a plumbing, HVAC or electrical company with six vans out.

The first job is a diagnostic call: a flat fee that half the customers expect to be waived if they approve the repair. The second is a $180 fix that ends with the technician standing in a kitchen asking a stranger to hand over a card. The third is a $9,000 system replacement, quoted last week, where a deposit was supposed to arrive before the equipment was ordered — and it did not, so the equipment was ordered anyway because the install crew is booked for Thursday. The fourth is a landlord who lives in another country and whose tenant has no hot water. The fifth is an after-hours emergency at 11:40pm: a price quoted verbally over the noise of a failing pump, agreed to instantly because the alternative is a flooded basement.

Every one of those is a different collection problem, and the company is trying to solve all five with the same two tools: a card reader that may or may not be in the van, and the phrase "we'll send you an invoice".

The card reader is a fleet, not a device. One per van means hardware to buy, batteries that die, connectivity in basements and rural service areas, firmware that updates at the wrong moment, and a device that walks off with a technician who quit. And behind it sits an acquirer relationship with a rate, a settlement delay of a day or three, and a chargeback process the company will lose more often than it wins.

"We'll send you an invoice" is where trades companies go to die. The job is complete, the parts are consumed, the technician's day is paid — and the money is now a receivable. Thirty days becomes forty-five, forty-five becomes a collections call, and the company is financing its customers' comfort out of a line of credit it pays interest on. A completed job that has not been collected is not revenue. It is a loan.

Cash still exists in this vertical and it is not a solution. It is invisible to the office until the van comes back, unattributable to a specific job without a paper ticket, occasionally lost, and it makes reconciliation between the field-service software and the bank a weekly forensic exercise.

Then there is the shape of the money itself, which is unusual. A trades company has three distinct revenue streams that behave nothing alike: small tickets collected in the field (service calls, repairs, call-out fees), large tickets quoted and staged (system replacements, panel upgrades, repipes, with a deposit against equipment ordered specifically for one address), and recurring plans (the maintenance agreement or membership that guarantees two visits a year, priority dispatch and a discount, and that quietly funds the months when nobody's furnace is broken).

Three revenue shapes, three failure modes, one payment stack that was designed for a shop counter.

What the wrong rail costs a plumbing, HVAC or electrical company every month

The emergency call-out that reverses. Night, weekend and holiday work carries a premium for the excellent reason that someone left their family to drive to a stranger's house. It is also the single most disputable transaction in the trades. The customer agreed under pressure, in the dark, without a written estimate they read carefully. On Monday, calm and dry, the premium looks like opportunism. Some of them call you. Some of them call their issuer instead, and card dispute windows — documented in network materials such as the Visa Core Rules — give them months to do it. Your evidence is a photo of a corroded valve and a finger-signature on a cracked tablet screen.

The deposit dispute on non-returnable equipment. A condensing unit, a panel, a specified boiler, custom ductwork: ordered for one address, non-returnable or returnable only with a restocking fee. When the deposit that funded it is charged back weeks later, you are holding equipment that fits exactly one house that no longer wants it.

The parts float, financed at card rates. Material is bought on Tuesday at the supply house, the job is completed on Thursday, the invoice is paid — optimistically — in thirty days. In between, the company card carries it. You paid a processing fee to buy the parts and you will pay another to collect for them.

Membership churn nobody sees. The maintenance plan is the healthiest number on a trades company's balance sheet: predictable revenue, guaranteed visits, first call on the customer when something breaks. It is also billed to a card that expires, gets reissued after a breach at an unrelated retailer, or trips an authentication step-up sent to a phone number that changed. The charge fails silently. Nobody cancelled; the plan simply stopped. You find out in April when the spring tune-up calendar is half empty. This is exactly the failure mode described in crypto subscriptions without chargebacks, and in home services it costs you the customer relationship, not just the monthly fee.

Per-technician blindness. Ask most trades owners what each technician collected yesterday, by job, and you will get a spreadsheet answer tomorrow. When collection is distributed across vans and devices, so is the visibility — and so is the shrinkage.

The dispute ratio that repriced your account. Acquirers do not merely bill each dispute. They watch the ratio, and a company with after-hours premiums, deposits on custom equipment and recurring plans generates more of them than a shop counter does. Drift toward the monitoring thresholds and the answer is a higher rate, a rolling reserve, or a polite suggestion to find another processor. A reserve is particularly painful for a business whose payroll, van leases, insurance and supply-house account are due on fixed dates regardless.

The customer who is not in the country. Non-resident landlords, second-home owners and the property managers who act for them are a large and growing share of this vertical's work. They need the AC fixed in a rental in a coastal city while they are in another hemisphere, and paying you means an international transfer with a fee, a cut-off time and a correspondent bank that may deduct along the way — for a $340 repair.

The Friday run. Subcontracted technicians, apprentices, day crews, the excavator guy, referral commissions to property managers and realtors. Every week, a stack of individual transfers with individual fees and individual cut-off times. And worth naming because it is expensive and rail-agnostic: the FBI's Internet Crime Complaint Center has documented for years that business email compromise — impersonating a payee to redirect a legitimate payment — is among the costliest categories of cyber-enabled crime. A subcontractor emailing "new bank details" the day before payout is the classic vector. Out-of-band verification of payee details is the control that matters, on any rail.

Why card readers, invoicing and cash each fail somewhere in the field

None of these rails is badly built. Each was designed around an assumption that field service violates.

Cards assume a merchant who can prove delivery. The dispute framework exists to protect a cardholder who paid and did not receive, and its evidence model is shipping: tracking, delivery confirmation, signatures. A home services company delivers labour into a building it does not own. Your proof is photographs, timestamps and a work order — real evidence, but weak evidence in a process designed around parcels. You are structurally the weaker party, and you are the weaker party after the copper, the compressor and the technician's ten hours are already spent.

Cards assume a stored credential that stays valid. Recurring billing works beautifully for a stable card in a stable country. It works less well for a membership plan sold to a homeowner whose card is reissued every couple of years and who has no idea the plan is attached to it.

Cards assume a terminal and a network. Basements, mechanical rooms, new-build sites without power, rural service areas at the edge of coverage. Every trades owner has a story about a completed job and a reader that would not connect.

Invoicing assumes the customer's convenience is aligned with yours. It never is. The invoice is sent when your interest in collecting is at its peak and the customer's interest in paying is at its lowest — the water is no longer on the floor.

Bank transfers assume a domestic customer during banking hours. The landlord abroad, the relocating owner, the corporate property manager in another jurisdiction: each one turns a $340 repair into a cross-border payment with a fee structure built for much larger amounts.

And every one of these rails assumes the payer has an account with a local institution. A meaningful share of the tenants, owners and small landlords a trades company serves are structurally foreign to the local banking system — newly arrived, non-resident, or simply holding their money somewhere else.

How Payzum lets a home services company accept crypto payments — at the door, in the office and on the payout run

Payzum is a non-custodial, crypto-only payment processor. Two words carry the weight.

Non-custodial means the money never sits in a Payzum balance. It goes from the payer straight to wallets your company controls. There is no processor float, no settlement delay, no reserve, and nothing for a third party to hold back while your van leases fall due. The settlement is the payment.

Crypto-only means the rail is on-chain and the payment is final once confirmed. Confirmation is fast enough to happen while the technician is still packing up: roughly 0.4 seconds on Solana, around two seconds on Base and Polygon. And because you can auto-convert to USDC or USDT, "crypto" does not have to mean price movement — see USDT vs USDC for payments if you want the difference between the two.

The instruments, mapped to how a trades company actually bills

• POS with a fresh QR per job. The technician opens the app on the phone already in their pocket, enters the amount for that work order, and shows a QR generated for that sale alone. No terminal to buy, no reader to charge, no acquirer, no card-network fees, no chargebacks. This is the same mechanic covered in turning a phone into a crypto POS.
• PIN cashiers, one per technician. Each tech collects under their own PIN, and the office gets analytics per cashier and per terminal. You can finally answer "what did van three collect today" without waiting for a paper ticket. The mechanics are covered in crypto POS with PIN cashiers.
• No-code payment links. The deposit on a system replacement, sent by text or WhatsApp the moment the customer says yes on the phone — before the equipment is ordered, not after. Also how the landlord in another country pays for a repair at a property they have not seen in two years.
• Invoices with an expiry and overpayment detection. For the quoted install, the commercial maintenance contract, the property-management account settled monthly. Reference the job number so reconciliation is mechanical; set the expiry to the date the crew is scheduled, which is the deadline that actually matters.
• Recurring subscriptions. The maintenance plan or membership, billed monthly or annually, with nothing to expire, reissue or authenticate. A plan cancels when the customer cancels it — not when their bank sends them a new card.
• Hosted checkout and a drop-in plugin. Behind the "book a service call" form on your site, so a diagnostic fee is collected at booking instead of hoped for at the door.
• CSV mass payouts and EVM stablecoin payouts. One file settles the whole Friday run — subcontracted techs, apprentices, day crews, referral commissions — on Polygon, Arbitrum, Optimism, Base, BNB Chain or Avalanche, plus BTC/LTC/DOGE batches. The format is walked through in bulk crypto payments by CSV.
• REST API with signed webhooks. Your field-service management software learns the job is paid the instant the payment confirms — so dispatch closes the ticket, the warranty clock starts and the technician's commission is calculated without anyone re-keying anything at 9pm.

What actually happens at the door

The technician finishes, opens the work order on their phone, taps the amount and shows a QR. The homeowner scans it with their wallet and approves. Within a couple of seconds the payment confirms on-chain, the technician sees it confirmed on the same screen, the office sees it attributed to that technician and that job, and the funds are in the company wallet. There is no authorisation that might be captured later, no batch that settles tomorrow, no acquirer in the middle, and no possibility that the payment is pulled back in March.

The difference from a card reader is not speed for its own sake. It is that the technician leaves a completed job with the money already collected, and the owner does not spend the following quarter wondering whether it will stay collected.

Honest scope: finality removes chargebacks — it does not remove a cancellation right

This is the part a home services company must understand before anything else, because this vertical sits exactly where consumer protection is strongest.

Contracts signed at a consumer's home are treated specially in most jurisdictions. In the United States, the Federal Trade Commission's cooling-off rule gives consumers a right to cancel certain sales made at their residence within a short window — the FTC explains the scope and the exceptions in its guidance on the cooling-off rule, and many states add their own home-improvement rules on top. Comparable withdrawal rights exist across the EU and in many Latin American consumer statutes.

On-chain finality does not touch any of that. What it changes is who executes the reversal. On a card rail, a customer can bypass you entirely and instruct their issuer, and you find out when the money is already gone. On this rail, there is no third party that can pull funds from your wallet — so where a cancellation right applies, or where you simply decide the customer is right, the refund is a payment your company initiates, from your wallet, on your books, on your timeline.

That is a genuine improvement in control and a genuine obligation. It means your written estimate, your cancellation notice, your refund policy and your record-keeping matter more, not less. Anyone telling a trades company that crypto payments make the customer's legal rights disappear is selling something we are not.

What else this rail does not do

Payzum is a payment rail. It is not your licence or registration, not your bond or insurance, not your permit, not your warranty administrator, not a mechanics-lien service, not an escrow agent, and not a payroll or worker-classification provider. Deposit caps on home-improvement contracts, prompt-payment and lien rules, permit obligations, sales tax on parts and labour, technician classification and the terms of your service agreement all remain exactly where they were: with you.

There is also no pre-authorisation on this rail. You cannot place a hold on a wallet the way a card reader places a hold on a card. A deposit here is real money received, refundable by you under your own written terms. For most trades companies that is closer to how deposits should have worked anyway, but it is a design difference worth knowing before you rewrite your terms.

Volatility is a setting, not a risk

The objection every trades owner raises first: "I am not taking something that moves 8% before I get to the supply house." You do not have to. Accept whatever the customer holds and auto-convert to a dollar-denominated stablecoin — USDC or USDT — so what lands in the company wallet is a dollar amount for a dollar invoice. The chain is the transport; the stablecoin is the unit.

How it works, step by step

1. Connect your wallets. Create the Payzum account and point it at wallets your company already controls. Many owners run two: one for field collections, one for deposits and larger installs. Turn on auto-convert to USDC or USDT if you invoice in dollars, and enable 2FA.
2. Put a cashier in every van. Create a PIN cashier per technician. Their phone becomes the terminal: amount in, fresh QR out, confirmation on screen. Nothing to buy, nothing to charge overnight, nothing to lose when a tech leaves — you deactivate a PIN, not chase a device.
3. Wire up the three revenue shapes. Payment links for deposits closed over the phone. Invoices with an expiry and the job number as reference for quoted installs and commercial accounts. Recurring subscriptions for maintenance plans and memberships. Hosted checkout behind the online booking form for diagnostic fees.
4. Connect the office software. Point the REST API and signed webhooks at your field-service management system so a confirmed payment closes the work order, starts the warranty clock and feeds technician commission automatically — including at 11pm on a Sunday, when no one is at a desk.
5. Run the payouts from one file. Build the weekly CSV for subcontractors, day crews and referral partners, verify any changed payee details out of band, and settle the batch. Same rail, opposite direction.
6. Reconcile by cashier and by job. Every payment carries its reference and its cashier. The office closes the week against work orders instead of against a bank statement that says nothing about which van did what.

Use cases at a home services company

Concrete situations a plumbing, HVAC or electrical company will recognise from this week.

• The 11:40pm emergency. Burst pipe, after-hours premium, price agreed on the doorstep. The technician collects on a QR before leaving. On Monday the customer may still call to complain about the premium — but the conversation happens with you, under your policy, and not with an issuer three months later.
• The $9,000 system replacement. The customer approves on the phone at 4pm. A payment link goes out by text at 4:01 and the deposit confirms at 4:06 — before the equipment is ordered. The balance goes on an invoice with the job number as reference and an expiry set to install day.
• The landlord in another country. A tenant has no heat. The owner is eight time zones away and their bank is closed. A payment link approved from a phone releases the repair the same evening, at the amount you quoted, without correspondent deductions turning a $340 job into a $312 receipt.
• The membership plan that survives the card reissue. Two hundred households on a maintenance agreement, billed as recurring subscriptions. No expiries, no reissues, no silent failures, and no April surprise when the tune-up calendar should be full.
• The property-management account. Forty units, a monthly statement of call-outs, one invoice with the property reference and an expiry. Paid in one transaction that confirms in seconds instead of a wire that arrives on Wednesday, short.
• The Friday run. Eleven subcontracted technicians across two metros, three day crews, and a referral commission to a property manager. One CSV, one batch, one set of confirmations — instead of fourteen transfers and fourteen fees.
• The commercial service contract. A small chain of restaurants on a quarterly preventive-maintenance agreement, billed as a subscription, with ad-hoc breakdown call-outs collected on the QR at the site by whichever technician attends.

Payzum vs card readers and invoicing for a home services company

Common objections, answered

"My technicians are not going to run a crypto payment on a customer's doorstep."

They already run something harder. A PIN cashier flow is: unlock phone, enter amount, show QR, watch it confirm. It is fewer steps than pairing a card reader, and there is no device to blame when it fails. The training is one job, supervised, and the analytics tell you immediately who is using it and who is not.

"Do enough of my customers even hold crypto?"

Not all of them, and this is not a replacement — it is an additional lane that costs you nothing when it is unused. It is worth having for three specific segments that are already expensive to serve: non-resident owners and landlords, customers who are new to the country and have no local card yet, and the crypto-holding homeowner who currently pays you by bank transfer because you gave them no better option. In several LATAM markets that third group is much larger than owners expect.

"We use field-service software for everything. Is this a rebuild?"

No. Links and invoices are generated from a dashboard with no code at all, and the POS is an app. The integration work — if you want it — is pointing signed webhooks at your system so a confirmed payment closes the work order automatically. Most companies start with the dashboard on day one and automate later.

"What happens when a customer wants a refund?"

You send one, from your wallet, under your written terms. What you no longer face is a third party deciding it for you months later and taking the money before you are consulted. As noted above, this does not affect any statutory cancellation right your customer has — it changes who executes the reversal, not whether the right exists.

"We are a four-van company. Is this too much for us?"

It is arguably more useful at four vans than at forty, because a single reversed emergency call-out and a couple of thirty-day receivables are a bigger share of your month. There is no acquirer application, no hardware order and no terminal fleet to manage — the phones already exist.

"Is it safe to have the money go straight to our own wallet?"

That is the point: there is no Payzum balance holding your money, so there is nothing for a processor to freeze, reserve or delay. The trade is that wallet custody is genuinely yours — which is why 2FA, encrypted secrets, a full audit log and signed webhooks are part of the product, and why we walk through wallet hygiene with every company on the setup call.