How domain escrow works

Why does a domain sale need escrow at all?

Because nothing technical forces a seller to hand a domain over. There is no smart contract at the registry. What makes the trade safe is sequencing: the buyer’s money is held by a neutral party until the buyer demonstrably controls the domain, and the seller is paid only then. If the seller never delivers, the buyer is refunded and the seller has gained nothing. That is the entire product of an escrow service.

What does the sequence look like?

1. The offer is accepted and the amount is fixed.
2. The buyer pays into the escrow hold, not to the seller.
3. The seller has a set number of business days to deliver: push the domain at the same registrar, or supply the authorization code so the buyer’s registrar can pull it across.
4. The buyer confirms receipt, or the escrow service verifies it from the registration record after a further few days.
5. Funds are released to the seller, sometimes after a short hold.
6. The dispute window closes.

Industry-typical values are a delivery window of about five business days, a verification window of about three, and a hold of one to two weeks when the buyer paid by card. That hold exists because a card payment can be charged back; there is none at all for a bank transfer.

How is delivery actually proved?

Through RDAP, the public registration record (WHOIS is the older form of the same thing). When the registrar and registrant of record show the buyer, the domain has been delivered. Escrow services poll that record, and if the buyer goes silent while the record clearly shows the transfer, delivery is auto-confirmed after a timeout. Neither side gets to decide it by assertion.

What goes wrong?

• The seller ghosts. The money never left the hold, so the buyer is refunded in full. The platform absorbs or passes on the payment processor’s non-refundable fee, which is why large deals are steered to bank transfer.
• A wrong or expired authorization code. A retry loop, not fraud.
• The buyer claims non-receipt after receiving. The registration record decides, which is exactly why platforms insist on registrar-level proof.
• A chargeback after the seller was paid. The reason hold periods exist at all, and the reason sellers get identity-checked on larger deals.
• A stolen domain is sold. The real owner’s registrar reverses the transfer weeks later and the buyer loses the domain. Account age, domain age, registration history and longer holds on high-value names are the usual defences.
• The domain is inside a transfer lock. It simply cannot move yet. See the 60-day lock. Push at the same registrar, or agree a date.

Where does nics.dev fit?

Deliberately outside the money. A nics.dev page produces an offer; the offer becomes a thread you own; you can accept, counter or decline on it. When you accept, the thread hands off to a third-party escrow service and records the reference, and shows a transfer checklist for that extension so both sides can see what is left to do. nics.dev never holds funds, which is why there is no commission mechanism to argue about.

Questions

Does nics.dev hold my money?

No, and it never will under the current design. nics.dev introduces buyer and seller, keeps the thread and records what was agreed. Payment goes through a third-party escrow service, directly between the two of you.

What stops a seller taking the money and keeping the domain?

The sequence. The buyer pays into a hold rather than to the seller, the seller has a fixed window to deliver, and the funds are released only once the registration record shows the buyer in control. If nothing is delivered, the buyer is refunded.

How is delivery proved?

Through RDAP or WHOIS, the public registration record showing the buyer as registrar and holder of record. Escrow services poll it rather than relying on either party's account of events.

Is escrow worth it on a small sale?

That is a judgement call about the fee against the size of the deal and how well you know the other party. Between strangers, on any amount either side would be upset to lose, it usually is.