# How to pay a broker a commission out of a domain sale A practical guide to structuring and disbursing broker commissions in domain sales, from fee models and closing mechanics to how onchain payment routing eliminates post-close settlement lag. --- A domain sale sounds simple on paper. Buyer sends money, seller hands over the name, broker gets a cut. In practice, the payment mechanics are the part of the deal that most frequently breaks down. The commission gets paid late, gets paid to the wrong account, or gets held up while two parties exchange wires days after the domain has already changed hands. This guide is for the brokers, closing attorneys, and settlement professionals who manage these transactions. It walks through every stage of the commission structure — how percentages are set, how disbursement is typically handled, where the friction lives, and how onchain payment routing through a tool like shaka.deal changes the settlement experience without changing anyone's role. ## Why commission structure must be agreed before any handshake deal is final Domain broker commissions typically run anywhere from 10% to 20% of the sale price, although the actual total should be worked out at the time of engagement. The broker should be paid upon the completion of the deal. That last point — paid upon completion — sounds obvious, but it is where most disputes begin. "Completion" is ambiguous until you define it in writing. Does it mean when the domain transfer is initiated? When it clears? When the buyer confirms receipt at the new registrar? When the wire lands? Defining completion precisely is the first act of good commission documentation. Most experienced brokers put this in an engagement letter or brokerage agreement before any buyer outreach begins. The agreement specifies the percentage, the event that triggers payment, and the payment method expected by the broker. If those three items are not in writing before the deal is negotiated, disagreements at closing become almost inevitable. **The three standard fee structures in domain brokerage** Brokers typically work with one of three primary pricing models, each with distinct advantages depending on the situation and budget. | Model | What you pay | When it applies | | --- | --- | --- | | Commission-only | A percentage of the final sale price, typically 10–20%; nothing upfront | The most common approach: the broker only earns when successfully closing the deal | | Upfront fee plus commission | A service fee (often $75–$500) in addition to a commission on the sale | The fee covers initial research, valuation, and outreach efforts regardless of outcome | | Retainer plus commission | A substantial retainer (often 1% or more of the domain's estimated value) plus a commission | Premium acquisitions, primarily six-figure and seven-figure deals where extensive negotiation and stealth acquisition tactics are necessary | Many brokers require a retainer before considering a project, with various commission models in use across the industry. For very large transactions, a tiered structure is also common. Tiered commission structures sometimes apply — perhaps 12% on the first $100,000 (AUD ~$155,000), 10% on the next $400,000, and 8% on amounts above $500,000. The logic is straightforward: a percentage-based fee that makes sense on a $50,000 (AUD ~$77,500) transaction can feel disproportionate on a $2 million one. Tiered structures let the commission scale with the work, not just the price. Some brokers will put a cap on the total commission potential, but most offer a set commission percentage for facilitating the deal. Caps are worth raising in negotiations for seven-figure names. A seller dealing with a $3 million (AUD ~$4.65 million) domain will negotiate differently than a seller moving a $30,000 name, and the commission cap conversation is entirely reasonable on that scale. ## The closing process and where the commission sits inside it Understanding where the commission lives in the payment waterfall requires understanding how domain sale closings work. Escrow is a facility provided by an independent third-party company which becomes significant in the event of a domain name purchase transaction. In domain name escrow, once a company has made an offer and the seller has agreed to the price and terms, the agreed cost is placed into a domain name escrow account while both parties fulfill their contractual obligations. This gives security to the buyer that the domain name will become theirs, and it offers security to the seller that the domain name transaction will go ahead. The classic sequence looks like this: 1. Buyer and seller agree on price, with broker facilitating. 2. Buyer deposits funds with the settlement agent or escrow service. 3. Seller initiates the domain transfer to the buyer's registrar. 4. Buyer confirms receipt of the domain. 5. After the escrow company inspects, checks, and verifies that the domain name has changed ownership, the seller receives the money and the transaction is complete. 6. The broker's commission is paid — either out of the proceeds before they reach the seller, or separately by the seller post-close. Step 6 is where most practical problems occur. The domain transfer is the event that unlocks escrow. But the commission disbursement is a separate downstream action. In the traditional wire-based closing, the settlement agent releases funds to the seller in one wire, and the seller then initiates a second wire to the broker. Those two wires are separated in time — sometimes by hours, sometimes by days, and occasionally by a dispute about the correct bank details. **Who actually cuts the check — and when** Brokers typically handle the entire transaction process, including domain valuation, locating owners, initiating confidential outreach, negotiating price and terms, coordinating escrow payments, and managing the technical domain transfer. Given that scope of work, the broker has every reasonable expectation of prompt payment the moment the deal closes. What they often get instead is a promise — "I'll wire you once the funds clear." In the most professionally managed transactions, the commission is built into the settlement statement itself, so that the escrow or settlement agent disburses to both the seller and the broker simultaneously. This is the cleanest structure. The seller never touches the commission money; it routes directly to the broker at the moment of close. In less structured deals — and many private domain sales between individuals, or off-marketplace transactions, are less structured — the commission flows as an afterthought. The seller gets one wire, then manually initiates a second. This creates the conditions for delays, errors in banking details, and, at worst, disputes about whether the agreed percentage applies to the gross price or the net price after escrow fees. ## The co-brokerage scenario: when there are two brokers to pay The single-broker scenario is the easy one. The harder closing is when a buyer's broker and a seller's broker are both involved. This happens frequently on premium domains: the seller engaged a broker to represent their interests, and the buyer also hired a separate broker to locate and negotiate on their behalf. Now there are four parties — buyer, seller, seller's broker, buyer's broker — and only one incoming payment. The co-brokerage arrangement defines the terms under which two or more brokers collaborate to represent a client or facilitate a transaction. Typically, this clause outlines how commissions or fees will be shared between the brokers, the responsibilities each broker holds, and the process for communicating with the client or other parties. By clearly allocating duties and compensation, the clause helps prevent disputes between brokers and ensures that all parties understand their roles. In practice, co-brokerage commission splits in the domain world often mirror the structure seen in other asset classes. The gross commission is established first (say, 15% of sale price), and then the two brokers agree on how to divide it — 50/50, 60/40, or some other negotiated ratio. The key point is that the total amount coming out of the sale proceeds is fixed. The internal broker split is an internal matter. Consider a concrete example. A domain sells for $200,000 (AUD ~$310,000). The seller's broker is entitled to 10% of the sale price, and the buyer's broker has a separate arrangement with the buyer, adding another 5%. In a clean closing structure, the escrow or settlement agent disburses all three amounts simultaneously from the single incoming payment of $210,000 (AUD ~$325,500): | Payee | Basis | Amount | In AUD | | --- | --- | --- | --- | | Seller | Sale price less the seller's broker commission | $180,000 | ~$279,000 | | Seller's broker | 10% of the sale price | $20,000 | ~$31,000 | | Buyer's broker | Separate 5% arrangement with the buyer | $10,000 | ~$15,500 | In a messy closing, the escrow releases $180,000 to the seller (net of seller's broker commission only), and the buyer separately resolves their broker obligation. This leaves the buyer's broker in an unsecured position — relying on the buyer's good faith after the buyer has already received the domain. ## The payment timing problem: why "paid at close" is harder than it sounds In traditional financial markets, there's a delay between when a trade is agreed upon and when it's officially settled. This gap, often lasting two business days, creates a significant problem: counterparty risk. The buyer could send payment but not receive the asset, or the seller could deliver the asset but not receive payment. In domain transactions, the same timing gap is present but takes a different shape. The domain transfer itself can be near-instant in modern registrar systems. The payment, however, is constrained by banking rails. ACH is the US system for low-cost bank-to-bank transfers, processing payments in batches, meaning settlement typically takes a full business day or longer. International wires can take two to three business days. If the seller is in one country and the broker is in another, the commission wire may not arrive until well after the domain has already resolved to the buyer's nameservers. For the broker, this creates a real operational problem. They have fulfilled their entire obligation — found the buyer, negotiated the price, coordinated the close. The deal is done. But the commission is floating somewhere in the banking system, ETA uncertain. For larger brokerages that close multiple deals per month, this timing uncertainty compounds into a genuine cash flow management problem. If five deals close in a given week and the commissions from all five are sitting in various stages of wire processing, the brokerage is operating on a lag that can stretch to tens or hundreds of thousands of dollars in outstanding receivables at any given moment. The secondary problem is verification. A wire transfer confirmation is not the same as cleared funds. A seller can send a wire on day one; the broker sees a confirmation email on day two; the funds may not be usable until day three or four. During that window, the broker cannot know with certainty whether the commission has been paid in the correct amount, to the correct account, and without conditions. ## Structuring the disbursement instruction correctly Whether the deal involves one broker or two, the most important document in the commission payment process is the disbursement instruction. This is the document — or, in a well-run close, the field within the escrow platform — that tells the settlement agent exactly where each dollar goes when funds are released. A well-structured disbursement instruction for a domain sale includes: - **Sale price**: The gross amount the buyer is paying. - **Escrow fee allocation**: Which party bears the escrow service charge, and how much it is. - **Seller's broker commission**: Dollar amount (not just percentage), account number, routing number, and SWIFT code if international. - **Buyer's broker commission** (if applicable): Same fields. - **Net to seller**: The residual after all fees and commissions are extracted. - **Transfer confirmation trigger**: The event that authorises the agent to release funds. Typically this is the WHOIS record updating to show the buyer as registrant. When the domain's ownership details show the buyer as the registrant, the escrow agent is notified. This confirms the transaction has been successfully completed from a technical standpoint. Upon confirmation, the escrow agent releases the funds to the seller. In a multi-party disbursement, that release should go simultaneously to all entitled parties — seller, seller's broker, buyer's broker — not sequentially. Sequential disbursement reintroduces the timing gap and the counterparty exposure that the escrow process was designed to eliminate. ## Practical scenarios: what can go wrong and how to prevent it **Scenario 1: The seller pays the broker after the fact** A common private-sale structure: buyer pays into escrow, domain transfers, escrow releases net proceeds to seller, seller then wires the commission to broker. This is the most fragile structure. The broker has no contractual claim on the escrow release — the escrow agent follows instructions, and if the instructions don't name the broker as a payee, the broker is unsecured. If the seller has a cash flow problem, disputes the commission calculation, or simply delays, the broker has no recourse except to pursue the seller directly. **Prevention**: Insist, in the engagement letter, that the broker's commission is included in the escrow disbursement instruction as a named payee. The broker's details should be in the instruction before funds are deposited, not after the close. **Scenario 2: Banking detail errors on international wires** The broker is in the UK. The seller's escrow account is in the US. The commission wire goes out in USD. A single digit error in the IBAN, or a missing intermediate bank code, causes the wire to reject — silently, in many cases — or to sit in a correspondent bank queue for days. The seller assumes it was delivered. The broker keeps checking. Nobody spots the problem for a week. **Prevention**: Confirm banking details in writing at the time the disbursement instruction is drafted, not at the moment of closing. Run a small test wire if the counterparty is new. Establish who is responsible for confirming delivery and within what timeframe. **Scenario 3: Co-brokerage percentage dispute at close** The seller's broker believed the co-brokerage arrangement was 60/40 in their favour. The buyer's broker has an email that says 50/50. The escrow agent cannot resolve the dispute and delays disbursement to both brokers while the parties argue. The seller is caught in the middle, unable to receive their own proceeds because the commission line items are unresolved. **Prevention**: The co-brokerage split must be documented as a separate, signed agreement between the two brokers before the deal closes. It should express the split in dollar terms — not just percentages — based on the known sale price. Attach it to the disbursement instruction. **Scenario 4: Tiered commission recalculation after price adjustment** The deal was originally negotiated at $250,000 (AUD ~$387,500). Late in the close, the buyer negotiates a $20,000 discount due to a trademark encumbrance discovered during due diligence. The final sale price is $230,000 (AUD ~$356,500). The broker's commission was calculated on $250,000 and the disbursement instruction hasn't been updated. The closing agent releases the original commission figure, leaving the seller short by the overpaid difference. **Prevention**: Any price amendment requires a revised disbursement instruction. Treat the instruction as a living document until the day of close, and require countersignatures on any amendment. ## How onchain payment routing changes the settlement experience All of the friction described above — the sequential wires, the timing gaps, the reconciliation uncertainty — is a product of the underlying payment infrastructure. Traditional bank rails were not designed for multi-party simultaneous disbursement. They were designed for bilateral transfers. When a deal has three or four payees, the settlement agent has to run three or four separate transactions and reconcile them manually. Smart contracts execute steps like manual revenue splits, escrow services, reimbursements, and multi-party settlements automatically as part of the payment itself. This is an automation layer embedded in the transaction flow — instead of manual splits and reimbursements, business rules execute as part of the payment. This is precisely the problem that shaka.deal was built to solve for professionals closing domain transactions. Shaka.deal is an onchain payment router on Ethereum. The closing agent, the broker, or the seller configures a deal with the agreed split: what percentage (or fixed amount) goes to the seller, what percentage goes to the seller's broker, what percentage goes to the buyer's broker. The shares are set in advance, before the payment arrives. When the buyer sends a single payment to the deal address, the router distributes the full amount simultaneously to every named party in one transaction. No sequential wires. No manual reconciliation. No waiting for the seller to forward the broker's share. The key architectural point is that shaka.deal is non-custodial. It routes the incoming payment; it never holds funds. The money passes through the routing contract and arrives at each party's wallet in the same block. There is no pool, no float, no float risk, no delay between "funds received" and "funds distributed." Atomic settlement is a transaction mechanism where the transfer of an asset and its payment occur simultaneously — onchain, this eliminates counterparty risk and enables real-time markets. For a domain broker, this translates directly: the moment the buyer's payment clears the routing contract, the broker's commission is in the broker's wallet. Not queued. Not processing. Settled. Onchain settlement can be near-instant and always available, eliminating cut-off risks and weekend delays. Business rules can be expressed directly in onchain payment logic. Shared ledgers produce consistent, timestamped records across parties, minimising payment disputes and audits. That last point — the audit trail — matters enormously to closing professionals. Every distribution event is recorded on-chain with a timestamp, an amount, and a recipient address. There is no ambiguity about whether the commission was paid, in what amount, and at exactly what moment. For brokers who deal with accountants, tax advisers, or clients requiring transaction documentation, the on-chain record is a clean, immutable receipt. ## Integrating onchain routing into an existing closing workflow Adopting shaka.deal does not require replacing any existing closing process. The escrow agent, the broker, and the attorney continue to do exactly what they do today. The disbursement instruction is still prepared. The trigger event — WHOIS update confirming the buyer as registrant — is still the moment that authorises release. What changes is the mechanism for the release itself. Instead of the settlement agent initiating three separate wires from a bank account, the payment is structured at the shaka.deal deal address level. The buyer (or the escrow service, if using a hybrid structure) sends one payment. The routing contract handles the rest. The closing agent can verify each distribution on the public block explorer in real time, rather than waiting for wire confirmations from two or three different banks. For international co-brokerage deals, this is particularly powerful. Sending a USD commission to a broker in Australia, a net amount to a seller in Germany, and a referral fee to a US-based facilitator would normally involve three separate international wires, three sets of SWIFT codes, three correspondent banks, and three uncertain timelines. With onchain routing, all three receive their share in the same transaction, regardless of geography. Settlement is final the moment the transaction confirms. When it comes to onchain clearing and settlement, there are no "off hours" — it is "always on" by default. A domain deal that closes at 11 PM on a Friday — not uncommon when buyer and seller are in different time zones — settles instantly rather than waiting for banks to open on Monday. ## What brokers should confirm before recommending this structure to a client The onchain routing model works best when a few conditions are in place: **Stablecoin payment**: The buyer needs to pay in a stablecoin (USDC, for example) for the amounts to be predictable at disbursement. Volatile crypto assets would introduce FX risk between the buyer's payment and the broker's receipt. Most professional domain transactions using shaka.deal use stablecoin as the payment token. **Wallet addresses confirmed in advance**: Each party — seller, seller's broker, buyer's broker — must provide a verified Ethereum wallet address before the deal is configured. This is analogous to providing wire details before close. Confirm addresses off-chain through a secondary channel before they go into the routing configuration. **Transaction finality understood**: Onchain transactions on Ethereum settle with finality. Once a payment routes through shaka.deal, the distribution is permanent and cannot be reversed. This is a feature, not a risk — it means the broker's commission cannot be clawed back, recalled, or reversed by the payer after the fact. But it also means that the amounts and the wallet addresses must be correct before the payment is sent. There is no recall mechanism. This is why confirming disbursement splits and wallet addresses before the buyer sends funds is non-negotiable. **Parties are comfortable with on-chain settlement**: Many domain sellers and buyers are already operating in the digital asset space and have no hesitation with stablecoin transactions. Some traditional businesses are newer to it. The broker often plays the role of educator here — explaining that stablecoins on Ethereum are purpose-built for exactly this kind of B2B settlement, and that the settlement record they produce is cleaner and more auditable than a batch of wire confirmations. ## The role of the broker does not change — the settlement lag does The value a domain broker delivers is entirely in the work that happens before closing: sourcing, valuation, confidential outreach, negotiation, and structuring the deal. Brokers bring market expertise and industry connections that individual buyers typically lack, which often results in lower purchase prices or higher sale values than going it alone. None of that changes when the payment mechanism at closing is onchain. What changes is the experience of getting paid. The broker who closes a deal on Tuesday should not still be tracking a wire on Friday. The co-broker on the buyer's side should not be relying on the seller's goodwill to forward their share. The closing attorney who drafted the disbursement instruction should not be fielding calls from three parties asking whether their wire arrived. Onchain payment routing via shaka.deal is not a replacement for any of those professionals. It is the mechanism that lets their agreed-upon disbursement instruction execute instantly and completely, the moment the deal conditions are met. One incoming payment. Preset shares. Simultaneous payout. Final settlement. That is how broker commissions on domain sales should work — and increasingly, for professionals who've experienced it, it is how they insist they do.