Accept crypto payments as a moving company: your customer is between two banking systems — and your rail assumes they aren't

Why a moving company collects its money on rails its own customers are leaving behind

Walk through a normal month at a mid-sized mover. A video survey turns into a quote; a deposit locks a crew and a truck against a date six weeks out. The balance falls due before loading — or, on an interstate or international job, before delivery. On the day itself there are extras: a flight of stairs nobody mentioned, a shuttle because the van can't reach the door, four hours of packing that became seven. Afterwards, the long tail: a storage unit billed monthly for as long as the customer is "figuring things out," materials sold over the counter, and a corporate relocation account that pays per assignee. On the paying side: packers and day crews on Friday, the subcontracted truck for the overflow job, the destination agent in another country who handled the last mile, and the relocation consultant's commission.

Now look at who's paying. The defining fact about a moving customer — especially the international one — is that they are mid-transition between financial systems. The United Nations counts roughly 281 million people living outside their country of birth, and every one of them hired, or will hire, someone to move their things. The outbound customer is paying you from an account they are about to close, with a card whose issuer is watching for exactly the anomaly a relocation produces. The inbound customer has landed with no local bank, no local card and no local credit history — and your balance is due before the container clears the depot.

You are running a business whose collections peak at the precise moment your customer's banking works worst. That's not bad luck; it's the structure of the vertical.

What the wrong rail costs on moving day

The decline at the curb. The balance is due, the truck is outside, and the card-not-present charge for $6,800 gets refused — because the issuer's fraud model just saw a big charge from a customer who changed country this week, which is textbook suspicious behaviour everywhere except in your industry. Your crew idles by the hour, the truck is booked on another job tomorrow, and a redelivery from the warehouse costs you the margin on the move. A crew-day is perishable capacity: the Tuesday you lose isn't sold on Wednesday.

The $200 claim that becomes a $7,000 dispute. A lamp arrives broken. Under your valuation coverage that's a bounded, documented claim. On a card, the customer holds a bigger lever: dispute the entire move as "services not as described." Card scheme rules give cardholders months to file — the windows are set out in network rules such as the Visa Core Rules — and household-goods moving is a category issuers already see disputes from. You defend a subjective service claim with a signed inventory and photos, from the wrong side of the presumption.

The deposit that comes back after a cancellation. Dates move; deals on houses fall through. Your contract says the deposit compensates the crew slot you held and turned other work away from. The card rail says the customer can ask their bank instead of asking you — and often win.

The storage card that dies silently. A card on file for $180/month fails in month nine because the bank reissued it — to an address your customer left a year ago, in a country they no longer live in. The dunning emails go unanswered, the lien letters go to the same dead address, and a solvable billing problem drifts toward the auction process nobody wants.

The international wire that arrives short. Corporate relocations and overseas customers pay by wire: two to five days, correspondent fees deducted en route, and an amount that lands $60 short of the invoice — so admissions of freight happen anyway, or someone chases the difference across time zones. Meanwhile the container waits on confirmed funds.

The risk pricing you inherit. Large card-not-present charges, deposits, subjective service disputes: acquirers read that profile as elevated risk and answer with a higher rate, tighter terms or a rolling reserve — a slice of your takings held back for months while payroll for the crews is due every Friday.

Why cards, wires and cash all fail a customer in transit

• Cards assume a stable issuer relationship and reward subjective disputes. Your customer's issuer relationship is at its least stable the week they pay you, and a household move is the most subjectively judged service on any card statement.
• Wires assume the payer's bank and yours share a cheap, fast corridor. Relocation corridors are exactly where correspondent chains are long, fees stack and some countries' banks can't send dollars out at all.
• Cash at the curb settles a $7,000 balance with a foreman counting bills on a tailgate — a security problem, an audit problem and an impossibility for the inbound customer who couldn't withdraw that much locally anyway.
• Local instant-payment schemes are excellent for residents. Your inbound customer became a resident this morning; your outbound customer stops being one on Friday.
• Checks and bank transfers from a closing account can bounce or freeze precisely because the account is being wound down.

The common thread: every rail anchors to a national banking relationship, and a mover's customer is — by definition of the service being purchased — between two of them.

How Payzum lets a moving company accept crypto payments

Payzum is a non-custodial crypto payment processor. Payzum never holds your money: there is no Payzum balance, no settlement batch, no rolling reserve priced against your dispute history. When a customer pays, funds move on-chain from their wallet to a wallet your company controls, and settlement is the payment. On-chain payments are also final: once the balance for a delivered move is confirmed, there is no mechanism by which the customer's bank can pull it back — a damage claim stays a damage claim, handled under your valuation coverage, instead of mutating into a full-invoice dispute.

A wallet works the same in the country your customer is leaving and the one they're arriving in. That's the whole point for this vertical: USDC held by a relocating customer is exactly as spendable the day before the flight as the day after it. The rail doesn't care that their banking life is mid-teardown.

The instruments, mapped to a mover's collection points

• Payment links and buttons — no code. The workhorse for the deposit that follows a video survey: quote agreed on the phone, link sent on WhatsApp or email, crew slot confirmed the moment it settles. A link also closes the ad-hoc charges — the shuttle fee, the extra flight of stairs — the same day they're agreed.
• Invoices with an expiry and overpayment detection for the pre-move balance, with the job number as the reference. Set the expiry to the day before load; short or mismatched amounts get flagged as they land, not discovered while the container waits. The same instrument bills corporate relocation accounts per assignee — and unlike the wire, it can't arrive $60 short without you knowing instantly which invoice and by how much.
• Recurring subscriptions for monthly storage — the billing that today dies silently on reissued cards. A stablecoin subscription doesn't depend on a card that expires in a country the customer left; the month it genuinely lapses, you know that day and can act while the customer is still reachable — the same mechanics as subscriptions without chargebacks.
• Hosted checkout — redirect, modal or inline — so an online quote-and-book flow ends in a paid deposit in the same session, without a human in the loop.
• POS with a fresh QR per sale. Any phone is a terminal: boxes and materials at the counter, day-of extras at the door — the same in-person flow as any counter business. Cashier accounts with PIN mean the foreman collects the stair-carry fee at the curb without ever touching the company wallet, with per-cashier analytics at close.
• Mass payouts. CSV batch payouts in stablecoins on Polygon, Arbitrum, Optimism, Base, BNB Chain and Avalanche: the Friday run for packers, day crews and subcontracted trucks, plus the destination agent abroad and the relocation consultant's commission, goes out as one operation instead of a dozen transfers across three rails.
• REST API and signed webhooks so your move-management system or CRM marks the job payable-to-dispatch the second the deposit funds, and releases the delivery when the balance confirms — including the balance paid at 11pm the night before an 8am load.

Volatility is a setting, not a risk

You quote in dollars and pay crews in local currency, so the right first objection is "I'm not holding something that moves 5% between deposit and delivery." 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 deposit collected six weeks before the move is the same number of dollars on moving day.

What's in scope — and what stays yours

In scope: booking deposits, pre-move and pre-delivery balances, day-of extras, packing-material counter sales, monthly storage, corporate relocation invoicing, and the payout run for crews, subcontractors, destination agents and commissions.

Not in scope, and we don't pretend otherwise: Payzum is a payment rail, nothing more. Your estimates and tariffs — including the consumer-protection rules that govern interstate and cross-border moves, and what you may collect at delivery — your valuation coverage and claims process, customs clearance of household goods, storage and lien law, crew employment classification and tax all stay exactly where they are. The rail changes; the bill of lading doesn't.

What doesn't change

Payzum is crypto-only and does not settle to a bank account. Converting stablecoins into local currency for payroll, fuel and rent remains a separate step you take with your own exchange or off-ramp, on your own schedule. What changes is how fast confirmed money arrives, who holds it in the meantime — nobody but you — and whether the balance that decides if the truck unloads depends on a fraud model's opinion of a customer who just changed country.

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 — nothing to release later, nothing to reserve against your dispute history.
2. Turn your quote sheet into instruments. Payment links for deposits after the survey. Invoices with an expiry set to load day for balances, job number as reference. Subscriptions for storage. POS QRs for the counter and the curb. Hosted checkout on the website's quote flow.
3. Collect the deposit as final money. The customer pays in USDC from any wallet — Solana confirms in well under a second, Base and Polygon in roughly two. Dispatch sees it against the job and confirms the crew and the date.
4. Clear the balance before the truck rolls. The pre-move invoice settles the night before; a signed webhook flips the job to "cleared for delivery" in your move-management system. Day-of extras go on the foreman's QR at the door.
5. Run the payout side from the same place. Friday: one CSV settles packers, day crews, the subcontracted truck, the destination agent and the sales commission in a single stablecoin batch.

Use cases at a moving company

Five situations where the difference shows up inside a single job, not in a year-end review.

• The outbound expat. Booked six weeks out, deposit paid in USDC while their local account is already scheduled for closure. The balance settles from the airport hotel the night before load — no card, no issuer, no fraud model with an opinion about relocations. The general case behind cross-border collections, compressed into one household.
• The inbound family with no local bank. Container at the depot, delivery balance due, and the customer's home-country card fails abroad. Instead of a week of attempted wires, they pay the invoice from a wallet in minutes and the crew delivers the same morning. The alternative wasn't a slower payment — it was storage fees, a redelivery charge and a furious customer sleeping on the floor.
• The claim that stays a claim. A lamp broke. You settle it under valuation coverage for $180, as your contract says. The move itself was paid in stablecoins and is final — so the claim can't escalate into a $7,000 "services not as described" card dispute filed from another continent.
• The storage unit billed for fourteen months. A USDT subscription survives two card-reissue cycles that would have killed a card-on-file. When the customer finally ships the goods onward, the account is current — no lien letters to a dead address, no auction file.
• The corporate relocation program. An employer moves eight assignees this quarter. Each gets an invoice with an expiry and the assignee's file number as reference; finance pays from one wallet; your dashboard reconciles per job. The destination agents who handled the last mile in three countries get settled in the same Friday CSV as your own crews — the payout pattern shared with every business trimming rail costs.

Payzum vs cards, wires and cash on moving day

Common objections, answered

"My customers don't hold crypto."

Most don't, and you don't need them to. This is an additional rail alongside the ones you already run, not a replacement. The customers it converts first are the ones the card rail serves worst: relocating professionals already paid in USDC, expats leaving countries whose banks can't send dollars out, inbound customers with no local account, and corporate programs tired of reconciling short-arriving wires. Offering it costs nothing when nobody uses it — and saves a crew-day every time the alternative was a decline at the curb.

"What I can collect, and when, is regulated on interstate moves."

It stays regulated, and nothing here changes that. Your estimates, tariffs and the rules on what's collectible at delivery govern how much and when — Payzum only changes how an accepted payment form settles. You list stablecoins among your accepted forms of payment in the estimate and the order for service, exactly as you list cards or certified checks today, and your compliance obligations ride along unchanged.

"I quote in dollars. What about volatility?"

Turn on auto-conversion and every payment — deposit, balance, storage month — settles as USDC or USDT, designed to track the dollar. The deposit you collect in March is the same number of dollars on moving day in May. No exposure window, no spreadsheet of rates.

"We already run move-management software."

Keep it. Payzum is drop-in: a REST API with API keys, signed webhooks and an integration playground, plus no-code links and invoices for everything you don't want to build. Your system stays the source of truth for surveys, inventories and dispatch; a webhook tells it the moment each deposit, balance or storage month is funded. Nothing about your estimate flow or your bill of lading has to change.