How to receive payment for a domain without a marketplace

Selling a domain privately — without listing it on Sedo, Afternic, Dan, or any other platform — is one of the cleanest ways to move a name and keep the full sale price intact. The mechanics of doing it right, however, are less obvious than the decision itself. When there is no marketplace standing between buyer and seller, there is also no built-in payment rail, no automated transfer trigger, and no one to blame but yourself if the deal falls apart on the money side. This article is for domain sellers, brokers, and advisors managing private transactions: it covers exactly how to collect payment, how to sequence the deal so both parties are protected, what can go wrong at each stage, and how to structure the money’s landing when multiple parties are entitled to a share.

Why private sales happen — and what they cost you if you wing it

Most high-value domain transactions happen off-platform. A buyer reaches out directly through a WHOIS contact, a landing page inquiry form, a LinkedIn message, or a cold approach brokered by an intermediary. The seller has a price in mind, the buyer has a budget, and neither party wants to hand five to twenty percent of the transaction to a marketplace that contributed nothing to sourcing the deal.

That reasoning is sound. On a $50,000 domain, a platform commission at fifteen percent represents $7,500 walking out the door. On a seven-figure name, the arithmetic becomes almost offensive. Going direct is not a workaround — it is a legitimate choice that sophisticated parties make deliberately.

The risk is not in the decision. The risk is in the execution. A private domain sale has no built-in rails. Payment and transfer must be coordinated manually, and without a clear sequence, the deal exposes both sides to real loss: the seller transfers the domain before payment clears, or the buyer wires money before the name is in their registrar. The mechanics of avoiding that exposure are what separate professionals from amateurs.

The core mechanics: what actually has to happen

Selling a domain privately requires solving three distinct problems in the right order: agreeing on price and terms, moving money, and transferring the domain. These sound obvious. The failure mode is treating them as simultaneous rather than sequential, or assuming that one side’s good faith is a substitute for a clean process.

The transfer problem

Domains are transferred via authorization codes (auth codes or EPP codes) issued by the current registrar. The buyer takes that code to their registrar of choice and initiates a transfer, which typically completes within five to seven days at most generic TLDs under ICANN rules — though premium registrars and ccTLDs can vary. Some sellers move the domain directly into the buyer’s account at the same registrar (a push), which is faster when both parties use the same platform.

The problem is that once you release the auth code, you have lost operational control of the name. If payment has not cleared, you are now in a dispute rather than a deal. The auth code is the handoff point, and it should never precede confirmed, cleared funds.

The payment problem

Private domain deals settle through a short list of payment methods, each with its own risk profile and timeline. Knowing which method fits which deal size is not optional knowledge — it is how you avoid a situation where you are chasing funds for weeks after a name has already transferred.

Wire transfer is the workhorse of domain deals above $10,000. SWIFT wires from U.S. accounts are relatively fast — same-day to one business day domestically, two to five days internationally. The mechanics are clean: buyer initiates, seller’s account receives, and once the funds show as collected (not just posted), the deal can proceed. The risk here is that wires can be recalled in fraud cases, which means “received” is not the same as “final” in the first 24 to 72 hours. For large deals, some sellers wait a full business day after receipt before releasing the auth code. That is not paranoia — it is standard practice.

ACH is common for smaller deals, typically under $10,000, and carries a longer reversal window. ACH transactions in the U.S. can be returned for several business days after they appear to clear. Using ACH for a significant domain sale without understanding that window is how sellers get burned.

Checks — certified, cashier’s, or bank checks — appear clean but carry real fraud risk. Counterfeit cashier’s checks are a well-documented vector in private asset sales. Banks may make funds available before they confirm the check’s legitimacy with the issuing bank, and by the time the check is flagged, the domain has transferred. Do not treat a cashier’s check as cleared funds. Call the issuing bank to verify before acting on it.

Cryptocurrency is increasingly used in domain deals, particularly for transactions involving buyers or sellers outside the U.S., for speed, and for deals where both parties want finality without a banking intermediary. A settled on-chain transaction is final in a way that no wire or check can match. There is no chargeback, no recall window, no ACH return. Once the transaction is confirmed to a sufficient block depth depending on the chain used, the funds are there. For sellers who are comfortable holding or converting crypto, this is a genuinely attractive option for the right buyer.

PayPal and other consumer payment platforms should not be used for domain sales above a few hundred dollars. Chargebacks are a documented abuse vector in domain deals — the buyer initiates a chargeback after transfer, citing “item not received” or a dispute, and the seller is left with neither the domain nor the money while the platform arbitrates. Avoid this entirely for any meaningful transaction.

Structuring the private deal without a marketplace

The absence of a marketplace does not mean the absence of structure. A private domain sale should have a written agreement — even a simple one — that specifies the domain name exactly, the agreed price, the payment method and timeline, what constitutes cleared funds, and the sequence: payment first, then auth code release. This does not need to be a ten-page contract. It needs to be specific enough that both parties have a shared record of what they agreed to.

The role of a third-party escrow service

When both buyer and seller are unknown to each other and the deal is large enough to justify caution, a licensed third-party escrow service — Escrow.com is the most commonly used in the domain industry — provides a neutral holding layer. The buyer deposits funds with the escrow service, the seller transfers the domain, the buyer confirms receipt, and the escrow service releases funds to the seller. The service charges a fee, typically paid by one or both parties as agreed.

This is not the same as a marketplace. The escrow service does not source the deal, does not take a commission on the sale price, does not hold an inventory of domains, and does not require the name to be listed anywhere. It is a payment coordination service, and it is entirely compatible with a fully private deal that bypasses any listing platform.

For deals in the five-figure range and above between parties who have no prior relationship, using a licensed escrow service is not excessive caution. It is the standard of care.

For deals where the parties know each other, where there is an established relationship, or where the deal structure is simple and both parties are comfortable, some sellers skip the escrow service entirely and sequence the deal manually: wire first, auth code after confirmation. This works, and it is done every day. The key is that the sequence is agreed to in writing before either party acts.

Small deals: direct payment and push

For lower-value domains — names in the low four figures or below — the overhead of a formal escrow service can exceed the practical risk. In these deals, many sellers accept payment via wire or ACH, wait for confirmation, and then push the domain directly to the buyer’s registrar account. The risk is real but proportionate. A $1,500 domain is not worth the same caution as a $150,000 name.

That said, the sequence still applies: payment first, transfer after. The size of the deal changes the tool, not the principle.

Private domain sales frequently involve more than one payee. A broker who sourced the buyer may be entitled to a commission. A co-owner of the domain may hold a percentage of the proceeds. An advisor who structured the deal may have a fee arrangement. In a marketplace transaction, the platform handles none of this — it pays the seller, and the seller is responsible for distributing what is owed to others.

In a private deal, that distribution is entirely the seller’s (or the closing professional’s) problem to solve. The default approach is serial: the full payment arrives in the seller’s account, and then separate payments go out to each party owed a share. This works. It is also slow, creates reconciliation work, requires each recipient to trust that the distribution will happen, and introduces the risk of a dispute if one party feels their share was miscalculated or delayed.

The cleaner approach is to route the payment so that each party’s share lands directly where it belongs, in one motion. When a deal closes and the funds move, a payment router lets the person managing the close define the wallets and the percentages in advance, and each recipient gets paid directly and simultaneously in a single transaction. There is no serial distribution, no reconciliation float, no “I’ll send yours over by end of week.” The funds split at the point of receipt. Shaka is built for exactly this: a closing professional sets up the deal, defines who gets what, and when payment comes in, everyone’s share goes directly to the right place in one transaction. That is the difference between managing a payout and automating it.

What to do when the buyer wants to pay differently than you prefer

Buyers sometimes push back on the seller’s preferred payment method. A buyer may prefer crypto when the seller wants a wire. A buyer may want to pay in installments when the seller wants the full amount upfront. These negotiations are common, and knowing how to handle them without losing the deal is part of the professional’s job.

Installment deals are real and done frequently on higher-value names. The typical structure is a meaningful deposit — often twenty to thirty percent — at signing, with the balance due within a defined period, sometimes tied to milestones or simply a fixed date. The domain typically does not transfer until full payment is received. Some deals use a lease-to-own structure where the buyer gets use of the domain (pointing permissions, DNS control) while payments are outstanding, but ownership does not transfer until the final payment clears. This requires more documentation and ongoing management, but it expands the buyer pool for expensive names.

If you are doing an installment deal, the agreement must be in writing, must specify what happens on default (the domain reverts, deposits are retained or forfeited depending on what was negotiated), and must be clear about what “use” the buyer gets during the payment period versus what they own. These are not difficult terms to draft, but leaving them ambiguous is how installment deals become expensive disputes.

Crypto offers from buyers deserve evaluation rather than reflexive rejection. If you have a buyer who wants to pay in stablecoin — USDC, USDT, or similar — the mechanics are actually favorable for the seller. The transaction is fast, it is final once confirmed, and there is no recall window. The buyer sends to your wallet address, you confirm on-chain, you release the auth code. For a seller who is comfortable with digital assets or who has professional infrastructure to receive them, crypto-denominated private deals are genuinely clean.

The caveat is volatility if the offer is in a non-stable asset. A buyer offering ETH or BTC is offering you an amount that will be different by the time you decide whether to accept. Price in a stable denomination — USD — and specify that the crypto equivalent will be calculated at the exchange rate at time of payment, or at a rate you agree on at signing. Do not accept the exposure.

Taxes, reporting, and the money you actually keep

A domain is an intangible asset. In most jurisdictions, a profit on its sale is a taxable capital gain or ordinary income depending on how the domain was acquired and held. This is not a technicality — on a significant private domain sale, the tax consequence can be substantial, and the fact that no marketplace issued you a 1099 does not change your reporting obligation.

If you are a domain investor selling names regularly, the IRS and most equivalents outside the U.S. will treat those gains as ordinary income from a trade or business. If you are a business selling a domain that was an asset of the business, the gain is treated accordingly. If you acquired a single domain for personal investment and held it for more than a year, long-term capital gains rates apply in the U.S. The specific treatment depends on facts, and the right answer here is to know your situation before a large deal closes — not to figure it out at tax time.

The practical point: when you are collecting the full sale price privately, with no platform netting out a commission, you are also netting the full gross amount. Your tax liability is calculated on that gross — or on the net gain over your basis, if you can document a cost basis, which most sophisticated domain investors and brokers can. Keep clean records of acquisition cost, holding costs, and any improvements or development expenses.

Protecting yourself when the buyer is a company

Corporate buyers introduce a different set of considerations. A company may have a legitimate procurement process that requires a vendor setup, a purchase order, approval from finance or legal, and a payment cycle that does not match your timeline. These are not stall tactics — they are real institutional constraints, and professionals who sell to corporations navigate them regularly.

The practical implication is that a verbal or email agreement with the business development person who approached you about the domain may not bind the company to a timeline or even to the price. Get a signed agreement — or at minimum a signed letter of intent — from someone with actual authority before you take the domain off the market. In a private deal with no platform holding the name in escrow status, there is nothing stopping the buyer from going cold if their internal process stalls.

Also understand that corporate buyers sometimes prefer wire transfers specifically because their accounts payable systems are built around them. If you are structured to receive wires cleanly — a business bank account, a verified beneficiary name that matches your entity, correct routing and SWIFT details — you will have fewer friction points with corporate buyers than if you are trying to direct them to a crypto wallet.

The registrar side of the equation

Even in a fully private deal, the registrar is part of the process. Most registrars require that a domain be unlocked before an auth code can be issued, and some impose a 60-day transfer lock on newly registered or recently transferred domains. If your domain was recently transferred to your account, check the lock status before you promise a buyer a specific closing timeline. Discovering a 45-day lock after a deal is signed is an avoidable problem.

Some registrars also require identity verification before releasing auth codes on high-value domains, or on domains that have not had prior transfer activity. Knowing your registrar’s process — and confirming that your account is in good standing with no holds — is part of deal preparation, not an afterthought.

For premium extensions — .io, .ai, and various ccTLDs — the transfer process sometimes involves the registry directly, not just the registrar. Certain country-code domains have restrictions on who can hold them, require local presence, or have manual approval steps. If you are selling a ccTLD privately, verify the transfer mechanics before you finalize the deal structure.

When a closing professional manages the deal

Not every private domain sale is seller-managed. Brokers and closing advisors frequently manage transactions on behalf of a seller, handling the buyer relationship, the documentation, the payment collection, and the transfer. In those cases, the professional needs their own infrastructure for receiving and disbursing funds — not just relying on the seller to settle up after the fact.

When a broker is handling a deal where the sale proceeds need to split among a seller, a co-broker, and potentially an advisor, the old approach is to collect the full amount and then wire out shares separately. That creates float, creates trust dependencies, and creates reconciliation work every time. The modern approach routes each party’s share directly at the point of settlement. When a deal closes on a platform like Shaka, the closing professional configures the split upfront — seller receives their net, broker receives their commission, any other party gets their share — and the transaction handles the distribution automatically. No one is waiting on anyone else’s wire. Payments are final.

The deal that looks easy until it isn’t

Private domain sales have a deceptive simplicity. Two parties, one asset, agree on a price, move the money, transfer the name. But the deals that go wrong almost always go wrong in the gaps: unclear sequence, ambiguous payment confirmation standard, an auth code sent too early, a check that bounced after the name had already transferred, a distribution that turned into a dispute because one party thought they were owed more than the other remembered.

The professionals who close private deals cleanly are not necessarily more experienced than the ones who get burned — they are more deliberate. They agree on the sequence in writing before anything moves. They define what “cleared funds” means for the payment method in use. They release the auth code only when that standard is met. They handle distributions through a mechanism that does not depend on anyone’s memory or good timing.

A private sale without a marketplace is not harder than a listed sale. In many ways it is simpler, faster, and more profitable. The difference is that every piece of the infrastructure that the platform would have handled — payment collection, sequencing, distribution — is yours to own. Own it deliberately, and the private deal is one of the cleanest transactions in the domain business.

How to receive payment for a domain without a marketplace