Safe Domain Transfer and Getting Paid: A Seller's Guide

Understanding safe domain transfer is the foundation of this guide. Below we break it down step by step so you can act with confidence.

You agreed on a price. Now comes the part that actually decides whether the sale is a success or a horror story: moving the domain to the buyer and getting the money into your account without one happening before the other. This is where inexperienced sellers lose domains, lose funds, or both.

The good news is that domain transfers are a solved problem. There is a standard, low-drama way to do this that protects both sides, and once you understand the moving parts, closing a sale becomes routine. This guide walks through escrow, authorization (EPP) codes, the difference between a registrar push and a full transfer, and the specific ways sellers get burned by chargebacks so you can avoid them.

Safe Domain Transfer: The one rule: money and domain move together, safely

The core risk in any domain sale is simple. If you hand over the domain first, the buyer can vanish without paying. If the buyer pays first, they worry you will vanish without transferring. Neither side should have to trust the other blindly, and you should never structure a deal that depends on trust.

The fix is a neutral third party that holds the buyer's payment, confirms you have delivered the domain, and only then releases the funds to you. That is escrow, and for any sale above a token amount it is not optional. The rest of this guide is really about executing that handoff cleanly. If you are earlier in the process, our complete guide to selling a domain name covers everything leading up to this point.

Escrow: Escrow.com and marketplace escrow

You generally have two safe routes for holding funds:

• Dedicated escrow (Escrow.com). The industry standard for private deals. The buyer deposits funds, Escrow.com verifies the money has cleared, you transfer the domain, the buyer confirms receipt (or an inspection window lapses), and funds are released. Escrow.com is licensed and regulated, and its domain-specific service understands auth codes and transfer timelines.
• Marketplace escrow. If you sold through a marketplace, the platform typically runs its own escrow and transfer flow (many marketplaces actually use Escrow.com behind the scenes). The advantage is that the whole handoff is guided inside one dashboard.

Escrow fees are modest relative to the protection: roughly 0.8%-3.25% of the sale depending on amount and payment method, with credit-card funding at the higher end. Agree in advance who pays the fee (a 50/50 split is common). Marketplaces bundle escrow into their commission, so compare total cost using our breakdown of domain marketplace fees.

Never accept a buyer's pressure to skip escrow for a wire, Zelle, PayPal friends-and-family, or crypto sent directly to you. That pressure is itself a red flag.

Auth codes and EPP: what you actually deliver

For most gTLDs (.com, .net, .org and similar), transferring a domain to another registrar requires an authorization code — also called an EPP code, auth-info code, or transfer secret. It is a per-domain password that proves you control the name and authorizes it to move.

Before closing, do three things at your current registrar:

• Unlock the domain. Turn off the registrar/transfer lock (clientTransferProhibited) so a transfer can be initiated.
• Disable WHOIS/privacy if it blocks the code. Some registrars won't reveal the auth code while privacy is on. Toggle it, retrieve the code, and note that the transferring buyer may need it visible briefly.
• Retrieve the current auth code. Codes can expire or be regenerated, so pull a fresh one at the moment of transfer, not weeks earlier.

One critical gate: a domain cannot be transferred to a new registrar within 60 days of its initial registration or a previous registrar transfer (an ICANN rule). If you acquired the name recently, plan for a registrar push instead, or price the timing into your deal.

Push vs. registrar transfer: pick the faster path

There are two mechanical ways to hand a domain to a buyer, and choosing the right one avoids days of waiting.

• Account push (same registrar). If you and the buyer both hold accounts at the same registrar (GoDaddy, Namecheap, Dynadot, etc.), you can push the domain directly to their account internally. This is fast — often minutes — needs no auth code, and sidesteps the 60-day lock. When possible, agree with the buyer to open an account at your registrar for a same-registrar push.
• Registrar-to-registrar transfer (EPP). If the buyer wants the name at their own registrar, they initiate a transfer using the auth code. This can take up to 5 days because of ICANN's transfer-approval window, though it often completes faster.

For an escrow deal, the flow is: buyer funds escrow, escrow confirms cleared funds, you push or release the auth code, transfer completes, buyer confirms, escrow releases your payment. Do not release the auth code or push the domain until escrow confirms the funds have cleared, not merely been submitted.

Avoiding chargebacks and payment reversals

A chargeback is the seller-specific nightmare: the buyer pays, receives the domain, then reverses the charge with their card issuer or files a PayPal dispute — leaving you without the domain and without the money. Digital assets like domains are especially vulnerable because non-delivery claims are hard to disprove outside a proper record.

Protect yourself:

• Use escrow that assumes chargeback risk. Escrow.com's wire and verified-funds options settle in a way that is not reversible like a raw card charge. This is the single biggest reason to route payment through escrow rather than accepting a card yourself.
• Prefer wire or verified bank funding for large sales. Cards and PayPal balances are reversible for months; a cleared wire is not.
• Keep a paper trail. Save the agreement, the escrow transaction record, and confirmation that the transfer completed. A clear record defeats most disputes.
• Let funds clear fully before you deliver. Never transfer on a pending or in-review status.

Getting the price and terms straight before this stage matters too — our guide on pricing a domain to sell helps you set a number both sides can commit to, so payment and escrow-fee terms are settled before you shake hands.

A clean closing checklist

Run every sale through the same sequence and closings stop being stressful:

• Agree the terms in writing: price, escrow provider, who pays the escrow fee, and the transfer method (push vs. transfer).
• Open escrow and send the buyer the transaction link; wait for funds to clear.
• Prepare the domain: unlock it, confirm it is outside the 60-day window, and retrieve a fresh auth code.
• Deliver: push to the buyer's same-registrar account, or release the auth code for a registrar transfer.
• Confirm and release: buyer accepts, escrow releases payment, and you keep every record.

If a buyer resists escrow, wants to pay off-platform, or invents urgency, slow down. A legitimate end-user buyer is comfortable with escrow because it protects them too.

The hard part isn't the transfer — it's finding the buyer

Notice that everything above assumes you already have a serious, paying buyer. That is the real bottleneck in domain sales. Listing a name and waiting rarely produces one, which is why listing a domain usually isn't enough and why sellers who close consistently do targeted buyer outreach.

That is the part Dominant Brand's done-for-you outreach service handles. We match your domain to real end-user buyers from our own network and send compliant, personalised pitches on your behalf, so that by the time you reach the escrow-and-transfer steps in this guide, there is an actual buyer on the other end. You keep control of pricing and approval; we do the finding and reaching. When a deal lands, you follow the safe-transfer flow above and get paid.

Frequently asked questions

Should I use escrow even for a small sale?

For anything above roughly $100-$200, yes. Escrow's fee (often under 3%) is trivial next to the risk of losing both the domain and the payment. For very small sales, a marketplace's built-in escrow flow is the simplest safe option. The only time direct payment is reasonable is a same-registrar push where you release the domain only after a truly cleared, non-reversible payment — and even then escrow is safer.

What is an EPP or auth code and where do I find it?

The EPP (authorization) code is a per-domain password that authorizes a registrar-to-registrar transfer. You retrieve it in your current registrar's control panel, usually under the domain's transfer or security settings. You may need to unlock the domain and temporarily disable WHOIS privacy first. Always pull a fresh code at transfer time, since codes can expire or be regenerated.

Why can't I transfer a domain I just bought?

ICANN rules impose a 60-day lock after a domain's initial registration or after a previous registrar transfer. During that window you cannot move the name to a different registrar. You can still sell it — use a same-registrar account push, which is not subject to the 60-day transfer lock, or agree with the buyer to wait out the window.

Push vs. transfer — which is faster?

A same-registrar account push is far faster (often minutes) and needs no auth code, so use it whenever the buyer is willing to hold an account at your registrar. A registrar-to-registrar transfer uses the auth code and can take up to five days because of ICANN's approval window, though it often completes sooner.

How do I protect myself from a chargeback after I transfer the domain?

Route payment through escrow (Escrow.com or marketplace escrow) rather than accepting a card or PayPal directly, prefer wire or verified-funds settlement for large deals, never deliver until funds have fully cleared, and keep a complete record of the agreement and the transfer. Reversible payment methods sent directly to you are the main chargeback exposure; escrow removes it.

A buyer wants to skip escrow and pay by wire directly — is that safe?

Treat it as a warning sign. A legitimate buyer benefits from escrow too, so resistance to it, off-platform payment requests, or manufactured urgency are classic scam patterns. Insist on escrow, and route the payment through a neutral holder before you release the domain.