A crypto transfer that hasn't cleared is not a payment. It's a promise with a price tag that changes while you wait.

Here's the operational rule: don't mark an invoice paid until the funds are irreversibly settled in an asset you can spend. Until then, you've accepted a receivable — one that can lose value, reverse, or vanish before it becomes money you can use. If a client says "I sent it," that's a status update, not a settlement.

The three risks you're actually taking on

Volatility is the obvious one. If you agree to $12,000 worth of a coin and it drops 9% before you convert to fiat, you just gave a discount you never negotiated. On a thin-margin job, that swing is your profit. You did the work; the market took the pay.

Settlement lag is the quieter problem. Network confirmations, exchange holds, and off-ramp delays mean the "instant" transfer can take hours or days to become spendable dollars. During that window, you carry the exposure. If it crashes mid-transit, you eat it.

And the chargeback story is backwards from what clients tell you. Crypto is often sold as "no chargebacks," which sounds great — until you realize it also means no dispute leverage for you. If the client sends the wrong amount, sends to a wrong address, or claims fraud through their exchange, you have no protocol that guarantees you get made whole. Irreversibility protects whoever holds the coins, and that's not always you.

The problem was never getting paid in crypto. It was calling it 'paid' before it cleared, then finding out the number moved.— GC who took a partial crypto deposit on a remodel

The structural fix: milestone escrow

The reason a wallet transfer feels risky is that it collapses two separate events — funding and release — into one moment you don't control. Escrow splits them back apart, and that's the whole fix.

Here's how it works structurally. The client funds the full milestone amount into escrow before you start the phase. The amount is locked to the agreed value — denominated in the currency you actually price in — so a market swing during the job doesn't rewrite your contract. You do the work. When the milestone is verified, the funds release. You never front labor and materials against money that only exists as a pending transaction.

That sequence kills all three risks at once. Volatility is neutralized because the value is fixed at funding, not at some fuzzy conversion moment later. Settlement lag stops mattering because the money was already confirmed and held before you lifted a tool. And the dispute problem inverts in your favor — instead of chasing a client who already has the deliverable, you hold verified funds and release on completion.

What this changes about how you quote

Once payment is structured this way, the crypto-versus-fiat question stops being scary. You're no longer betting on a coin or hoping a transfer finalizes. You're working against money that's confirmed, locked to your agreed number, and staged to release as you hit checkpoints.

Break the job into milestones — deposit, rough-in, completion, whatever fits the scope. Each one funds before it starts and releases when it's done. The client gets proof their money is committed. You get proof you'll be paid for work you're about to perform. Nobody is trusting a screenshot.

That's the difference between accepting a modern payment method and taking on a modern liability. The method isn't the problem. Getting paid before the value moves out from under you is the point.

If you want to see how milestone-based escrow lines up against the way you already run jobs and bill clients, it's worth walking through the structure before your next deposit.