Accept crypto payments as a construction company: fund the draw before the crew stands down

Why a construction company gets paid on a schedule it doesn't control

Construction is one of the largest sectors in any economy — the US Census Bureau's Construction Spending series tracks it in the trillions of dollars annually — and almost none of that money moves the way the work moves. The work is continuous. The money arrives in lumps, late, and through a rail that closes at 5pm on Friday and doesn't reopen until Monday.

Look at a single mid-size remodel. You sign a contract in March for a kitchen and two bathrooms. There's a deposit at signing, a material buy-out draw when the order goes to the supplier, a draw at demolition and rough-in, another at drywall, another at cabinet set, and a final balance at punch list — with a retainage percentage held back for thirty or sixty days after that. Six or seven separate collection events on one job, each one a gate that has to open before the next crew mobilises.

Now stack four jobs running in parallel, which is what a healthy small builder actually looks like. That's roughly twenty-five collection events a quarter, none of them predictable, all of them dependent on a homeowner or a developer or a lender remembering to move money on a business day. Your project manager isn't managing construction. They're managing a receivables calendar with a hard hat on.

And the sequence is brutally one-directional. You order the materials before you're paid for them. You pay the framing crew Friday for work the client will be invoiced for on the fifteenth. You buy the permit, rent the lift, pay the dumpster haul and cover the first fuel run — and only then do you get to ask for money. A general contractor is, functionally, an unsecured lender who also happens to build things.

What a late draw actually costs — and it isn't the interest

Ask a builder what a three-day payment delay costs and they'll usually try to calculate interest on the float. That's the wrong number, and it's far too small.

The real cost is the crew. Subcontractors are booked in blocks. If the drywall draw hasn't cleared by Thursday, you can't confirm Monday, and by Friday your drywall crew has taken a different job for the next two weeks. You didn't lose three days. You lost fourteen, plus the trades stacked behind them, plus the client's confidence in your schedule. On a job with a liquidated-damages clause or a hard completion date, that gap is the whole profit.

Then the material float. Lumber, tile, fixtures and cabinetry get bought on your supplier account or, very often, on a company card — which means you're financing your client's project at credit-card rates while waiting to be reimbursed by a transfer that clears in three days. Contractors carry this because there's no alternative, not because it's sane.

Then the deposit dispute. This is the one that hurts most and gets discussed least. A client pays a $9,000 deposit by card. You order custom, non-returnable cabinetry. Eleven weeks later the relationship sours over something unrelated and the deposit is disputed. Card scheme dispute rights run for months — the timeframes are set out in the network operating rules, such as the Visa Core Rules — and by the time you're gathering evidence, your money and the cabinets are both gone. You are defending a chargeback with a signed contract and a photo of a torn-out kitchen.

Then the card ceiling. Which is why most builders cap card payments at a few thousand dollars in the first place. Interchange on a $40,000 draw is roughly a subcontractor's entire week. So the big money moves by wire or check, and you're back to banking hours, deposit holds, and calling the client to ask whether they actually sent it.

Then the fraud. Construction draws are close to a perfect target for payment-instruction fraud: high value, scheduled, emailed as a PDF, between a builder and a homeowner who communicate mostly by email and have no shared security procedure. Business email compromise — an intercepted invoice thread with swapped bank details — has for years been among the costliest categories of reported cybercrime tracked by the FBI's Internet Crime Complaint Center, with real-estate and construction transactions repeatedly called out. A homeowner who wires a $60,000 draw to a fraudster is a homeowner who is not going to wire it twice.

And then the owner who isn't in the country. Second homes, vacation properties, investment renovations, family builds financed by a relative abroad — a large slice of residential and light-commercial work is paid for by someone in a different banking system. Every draw becomes an international transfer with correspondent fees, an FX spread, a compliance question and a two-to-five day lag, repeated six times over the life of one job.

Why cards, wires and checks all fail construction specifically

Each rail fails for a different structural reason, and builders are usually told the answer is "tighter contracts". It isn't. It's the instrument.

• Cards break on size and on finality. They're economical at $800 and ruinous at $40,000, and they stay reversible for months — which is the worst possible property for a payment whose consideration is a wall that already exists. You cannot un-pour a slab.
• Bank wires assume both parties keep the same business hours, and they're opaque until they land. They also put the payment instruction in an email, which is exactly where interception happens. And a wire initiated Friday afternoon is a Tuesday problem.
• Checks add a deposit hold on top of everything else, bounce silently days later, and require someone to physically go to a bank in the middle of a workday.
• Cash still runs a meaningful share of small-works and trade billing, and it brings handling risk, no audit trail, and reporting thresholds that differ by country and get stricter as tickets rise.
• Net terms with a developer or GC above you are not a payment method at all. They're a financing product: you build now, you invoice, and you find out in sixty days whether you were also the bank.

The common thread: every one of these rails settles on a calendar set by a financial institution, while your costs accrue on a calendar set by a job site. Those two calendars have never been synchronised, and no amount of contract drafting will synchronise them.

How Payzum lets a construction company accept crypto payments

Payzum is a non-custodial crypto payment processor, and in this vertical that single word does most of the work. Payzum never holds your money. There is no Payzum balance, no release schedule, no rolling reserve held back against your job volume, no withdrawal request to file on a Friday. When a client pays a draw, funds move on-chain from their wallet to a wallet your company controls. Settlement is the payment — which matters enormously when the entire problem is the gap between "the client paid" and "I can confirm the crew".

Be precise about what this covers — and what it doesn't

This is a collections and disbursement tool for money your company bills and pays in its own name. In construction the boundary matters more than in most industries, so draw it before your accountant or your attorney does.

In scope: contract deposits, material buy-out draws, scheduled progress draws, change orders and extras, time-and-materials billing, small-works and service-call invoices, emergency call-outs, design and permitting fees, equipment and scaffold hire you rebill, the final balance and retainage release. On the paying side: subcontractors and trade crews, day labour, equipment rental, haulage and skip hire, and suppliers who accept stablecoins.

Not in scope, and we don't pretend otherwise: Payzum is not escrow, not a construction-loan draw administrator, not a title or closing agent, and not a client-money trust account. If your jurisdiction requires deposits above a threshold to sit in a trust or escrow account, or caps what you may take up front on a home-improvement contract, that obligation is unchanged and it is yours. Your contractor licensing and bonding, mechanics-lien and prompt-payment rules, lien waivers, permits and inspections, insurance and warranty obligations, contract terms, refund policy and tax treatment all stay exactly where they are. In Spain, for example, the structural guarantees and insurance regime under the Ley de Ordenación de la Edificación applies regardless of how the client transfers money. The rail changes. The file does not.

The instruments that cover them

• Payment links and buttons — no code. The workhorse for a draw. Your office generates a link for "Draw 3 — rough-in complete, 12 Oak Street", pastes it into the same email as the progress photos, and the client pays from a phone at 9pm on a Sunday. No bank branch, no business hours, no bank details in an email thread for anyone to intercept.
• Invoices with an expiry and overpayment detection. For the scheduled draws and the final balance. Put the job number and the milestone on it as the reference, and set the expiry to the date the next stage is supposed to start rather than an arbitrary net-30. Mismatched amounts get flagged at the moment they land instead of surfacing at month end.
• Hosted checkout as a redirect, modal or inline embed, so a signed digital quote can end in a paid deposit in the same session — instead of "our office will email you our bank details tomorrow", which is where a third of deposits go to die.
• Recurring subscriptions for the work that repeats: a maintenance contract on a commercial property, a monthly grounds or facilities retainer, a snow or landscaping season plan, a developer's ongoing site-services agreement. Unlike card subscriptions, they don't die to a dispute mid-contract.
• POS with a fresh QR per sale. Any phone or tablet becomes a terminal at the client's front door, at the trade counter, or in the site office. Cashier accounts with PIN mean a foreman or a service tech can take payment for a call-out without ever touching your wallet, with per-cashier analytics at the end of the day — the same PIN-cashier setup any multi-crew operation uses.
• Mass payouts. CSV batch payouts in stablecoins on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche — the entire Friday run of subs, crews and equipment hire as one operation instead of thirty separate transfers. It's the same mechanic behind paying contractors in stablecoins.
• REST API and signed webhooks so your project-management or accounting system knows a draw is funded the second it's funded, and the scheduler can release the next stage without anyone refreshing a bank portal.

Volatility is a decision, not a risk you're forced into

The first objection from any builder is the right one: "I bid this job at a fixed price against a supplier quote. I am not accepting something that might be worth 8% less by the time I buy the windows." You don't have to. Payzum accepts crypto and settles in crypto, with optional auto-conversion to a stablecoin such as USDC or USDT. A stablecoin is designed to track the dollar, so a draw received as USDC on Tuesday is the same number of dollars when the cabinet invoice comes due on Friday. For a business whose margin is the spread between a bid and a cost, that property isn't a bonus — it's the precondition for using the rail at all.

What doesn't change

Everything that makes you a builder stays as it is. Your contracts, your licence and bond, your lien procedures, your schedule of values, your inspections, your subcontractor agreements, your insurance and your warranty obligations continue to work exactly the way they do today. Payzum is crypto-only and does not settle to a bank account, so converting stablecoins into local currency to pay a supplier who invoices in fiat remains a separate decision you make with your own exchange or off-ramp, on your own schedule. What changes is how fast the money arrives and who holds it in the meantime. Nothing else.

How it works, step by step

1. Open the account and connect a wallet you control. Create a Payzum account, complete KYC, and point settlement at your company's own wallet. There is never a Payzum-held balance, which is why there's nothing to be released to you later and nothing for a processor to reserve against your job volume.
2. Turn your schedule of values into links and invoices. Build a payment link for each milestone on the contract — deposit, material buy-out, rough-in, drywall, cabinet set, final — and use invoices for the variable ones, with the job number as the reference and an expiry set to the date the next trade is booked to start.
3. Send the draw request with the progress photos. The client pays from their wallet or exchange on whichever supported network they use — Solana confirms in well under a second, Base and Polygon in roughly two. Funds land in your wallet, the dashboard marks the draw paid, and overpayment detection flags any mismatch instead of leaving it to a reconciliation three weeks later.
4. Let the schedule act on it. A signed webhook marks the milestone funded in your project-management system, so the office can confirm the next crew immediately — including at 8pm on a Sunday, which is exactly when a Monday start gets decided.
5. Take counter and call-out payments on the POS, and pay everyone from the same place. A service tech opens the POS on a phone, enters the amount and shows a fresh QR at the customer's door — the same in-person flow any field business uses. On Friday, upload one CSV to settle every sub, crew and equipment hire in a single batch.

Use cases in construction and remodeling

Five situations where the difference shows up inside one working week, not in a year-end review.

• The Sunday-night draw that saves Monday. Rough-in passes inspection Friday afternoon. Drywall is booked for Monday, and you won't confirm it until the draw is funded. You send a payment link with the inspection photos. The client pays Sunday at 9pm from their phone, it settles in seconds, the webhook marks the milestone funded, and the office confirms the crew before anyone opens a laptop on Monday. The two weeks of schedule slippage that didn't happen is the entire return.
• The change order agreed on site at 11am. The homeowner wants the island moved and an extra circuit run. Your foreman prices it on the spot, the office sends a link from the truck, it's paid before lunch, and the electrician does it the same afternoon instead of on a second mobilisation next month. Small-ticket extras stop being a receivable you write off at the end of the job.
• The non-resident owner building a second home. A client abroad is renovating a coastal property and every draw is an international transfer with fees, an FX spread and a three-day lag. They pay in USDT instead, from wherever they are, on the day. Auto-conversion means you booked a dollar amount — the general case behind cross-border collections and getting paid from abroad without a local bank account. The adjacent case, where a real estate agency collects reservation deposits and management rent, works the same way.
• The Friday subcontractor run. You owe eleven subs, six day-crew members, a scaffold company and a plant-hire firm. Instead of eighteen separate transfers with eighteen fixed fees and a two-day lag each, you upload one CSV and settle the whole list as a batch of stablecoin payouts. The people who show up Monday are the people who got paid Friday.
• The service and small-works desk. Emergency call-outs, boiler swaps, gutter and roof repairs, trade-counter pickups: a tech takes payment at the door on a phone with a fresh QR per job, PIN cashier accounts per technician, per-tech analytics at close — no acquirer, no terminal rental, no batch settlement, and none of the 3% card fees on jobs where the margin is already thin.

Payzum vs cards, wires and checks for construction draws

Common objections, answered

"My clients are homeowners. They don't hold crypto."

Most won't, and you don't need them to. This is an additional rail offered alongside the ones you already run, not a replacement for them. The clients who take it up first are the ones the bank rail serves worst: non-resident owners of second homes, investors and developers who already hold stablecoins, crypto-native buyers, and anyone facing a Monday start that a Friday wire cannot fund. Offering it on the draw request costs you nothing when nobody uses it, and saves a fortnight of schedule the first time someone does.

"What about the deposit rules and escrow in my state or country?"

They apply unchanged, and they're yours to meet. Many jurisdictions cap what a contractor can take as an up-front deposit on a residential improvement contract, and some require client funds above a threshold to be held in trust or escrow. Payzum is not escrow and does not hold client money — funds go directly from the payer to a wallet your company controls, which means your obligations around segregation, deposits and disclosures are exactly the ones you have today with a bank transfer. This is general information, not legal advice: confirm the rules that apply where you build with your own attorney or adviser.

"I need local currency to pay my suppliers."

Then be clear-eyed about scope: Payzum is crypto-only. It does not settle to a bank account and it will not convert your receipts to fiat for you. Turning stablecoins into local currency is a separate step you take with your own exchange or off-ramp, on your own timetable. What changes is that you're holding a dollar-denominated asset you actually control within seconds of the client paying, instead of waiting three days to learn whether a wire landed and how much of it survived the trip. Note too that a growing number of trade suppliers and equipment hire firms will take stablecoins directly.

"What if a client overpays, or pays the wrong draw?"

Invoices carry overpayment detection, so a mismatch surfaces at the moment it happens rather than at reconciliation. Because each draw carries the job number and milestone as its reference, allocation is unambiguous — which is already better than a bank transfer arriving with "PAYMENT" in the memo field and a bookkeeper guessing which of your four active jobs it belongs to.