# How to settle a domain lease-to-own arrangement
A practical guide for domain brokers, escrow officers, and closing attorneys on structuring and settling every financial layer of a domain lease-to-own deal.
---
A domain lease-to-own deal is not a single transaction. It is a structured financing arrangement that quietly generates complexity at every stage — at signing, at each installment, at early payoff, at final transfer, and at the moment a broker or attorney expects their fee. Most professionals who handle these deals are fluent in the underlying agreement mechanics. Where things get messy is in the settlement layer: who receives what, in what order, and with what certainty when the final payment finally arrives.
This article walks through the full lifecycle of a lease-to-own (LTO) arrangement from a settlement perspective — the mechanics that closing attorneys, domain brokers, and escrow officers need to understand before structuring the deal, not after it closes.
## What a domain lease-to-own arrangement actually is
A domain name lease-to-own purchase option is a contractual arrangement that lets a buyer acquire the right to use and ultimately purchase a domain by making periodic payments instead of paying the full price upfront. The buyer makes scheduled payments under preset terms; when the payment plan completes — or sometimes if an agreed buyout is exercised early — ownership transfers from the seller to the buyer.
There is an important legal distinction worth noting at the outset. With a pure installment plan, the seller may have limited recourse if the buyer goes bankrupt, because the domain is legally the buyer's property from the moment of transfer. With a lease-to-own, by contrast, title remains with the seller throughout the lease term, and a proper option price must be defined — otherwise the agreement may lack enforceability in a dispute. Getting that distinction right in the agreement is the first responsibility of the closing attorney or broker structuring the deal.
Interest or financing charges are sometimes added, particularly for longer terms, ensuring that the seller receives compensation for tying up the domain rather than selling it outright. It is common to see LTO deals priced slightly higher than lump sum transactions, reflecting both the convenience provided to the buyer and the risk undertaken by the investor.
Domain holding service transactions have a term minimum of six months and a maximum of five years in many structured escrow frameworks, though plans can range from two to one hundred and twenty months depending on the platform or agreement structure used.
## The roles that matter at settlement
Before you can settle the deal correctly, everyone's role needs to be mapped. In a fully brokered LTO, there are typically at least four parties:
1. **The seller** — the domain investor or business that holds legal title throughout the lease term.
2. **The buyer** — the company or individual making installment payments and using the domain during the term.
3. **The escrow or holding service / closing attorney** — the neutral party that holds the domain and facilitates the flow of funds.
4. **The broker (sometimes two)** — the professional who originated, structured, or negotiated the deal.
How funds and the domain move through a holding serviceFrom signed agreement to final transfer
Agreement signedOnce a signed agreement is received from all parties, the buyer is authorized to send the first payment and any portion of the service fee.
Domain moved into holdingWhen that first payment is received, the seller is prompted to transfer the domain into the holding account.
First payment releasedWhen the domain is received and secured, the parties are notified and the first payment is released to the seller.
Scheduled payments passed onThe escrow or holding service then receives the scheduled payments from the buyer and sends them to the seller throughout the term of the transaction.
Final transferWhen all payments are completed, the domain is transferred to an account for the buyer and the last payment is made to the seller.
That description makes it sound clean and sequential. In practice, each installment is its own micro-settlement event, and each one carries the same question: does everyone who is owed a share actually receive it simultaneously and with certainty?
## How the payment waterfall works — and where it usually breaks down
### The installment structure
Some deals simply divide the agreed purchase price by the number of months in the term, creating equal installments. Others include an upfront deposit or down payment to demonstrate buyer commitment and reduce seller risk.
Consider a concrete example. A premium domain is agreed at $120,000 USD (~$185,000 AUD). The deal is structured as follows:
- Down payment: $24,000 USD (~$37,000 AUD) — 20 percent of the total
- Monthly installments: $4,000 USD (~$6,150 AUD) for 24 months
- Broker commission: 10 percent of total consideration, owed to a single sell-side broker
- Escrow/holding service fee: agreed as a flat monthly holding fee, split between the parties
Each month, $4,000 comes in. Out of that, the broker is owed approximately $400 per installment if commission is distributed pro-rata, or the full $12,000 can be structured as due at final close, depending on the commission agreement. The escrow service takes its monthly fee. The seller receives the remainder.
On a platform that processes each of these as a single sequential payout, there are three separate disbursement events per installment. Sellers typically receive their portion of each installment payment monthly, within three to five business days of the platform receiving the payment and verification of funds. In practice this means there is a lag between the buyer's payment and the seller's receipt, and the broker may be on a completely different disbursement schedule.
This is the first pressure point. Multiple parties, multiple shares, multiple timing windows — all triggered by a single incoming payment from the buyer.
### The broker commission problem in LTO deals
The broker's fee in a domain LTO deal is structurally similar to how commercial lease commissions work in property. In buy-side representation, the buyer usually covers the commission; in sell-side representation, the seller pays from their proceeds. Some high-value deals involve split commission structures where both parties contribute.
When the broker commission is paid at close — a common structure in outright domain sales — the timing is straightforward. In an LTO, "close" is ambiguous. Does the broker earn at signing? At the first installment? Pro-rata over the term? At final transfer?
There are some cases where a broker may not receive all of their commission at once. A broker and seller can agree to a structured payment where the broker receives commission payments over a set number of months.
The challenge is that a pro-rata commission arrangement creates ongoing administrative work and introduces real risk. If the buyer defaults in month 14 of a 24-month term, the broker may have already received 14/24 of their fee — but the seller may be trying to claw back payments or pursue default remedies. The question of whether the broker is entitled to retain those installment commissions, or whether they are netted against the seller's recovery, needs to be answered in the agreement before the deal closes, not after default occurs.
The cleaner approach used by many experienced brokers and closing attorneys is to treat the commission as fully earned at signing (when the agreement is executed and the domain is placed in holding), with payment either immediately at signing or deferred to the first installment. This mirrors the commercial real estate convention of paying a portion at lease signing and is far less contentious.
## DNS access, registrar locks, and the transfer mechanics at final settlement
### What the buyer controls during the term
During the lease, the owner keeps legal title at the registrar but updates the domain's DNS records — A, CNAME, MX, or others — so the buyer's website, email, and other systems operate normally. After the first installment, the buyer is typically assisted in updating name servers or DNS, but such access does not grant the buyer any ownership interest in the domain prior to full payment.
The practical implication for the settlement professional is that the buyer is commercially dependent on the domain from day one — their website, email infrastructure, and brand identity may all run through a domain they do not yet own. This dependence is leverage for the seller in a default scenario, but it is also a source of significant business interruption risk for the buyer if there is any dispute about the settlement of the final payment.
### The final transfer at settlement
When the last payment clears, the domain must be transferred from the escrow holding account to the buyer's registrar. This is where knowing the locking mechanics is essential for any closing professional.
Three different mechanisms get called a "lock," and conflating them is the root of the transfer confusion buyers run into.
| Mechanism | Set by | How it is cleared |
| --- | --- | --- |
| Registrar lock | Client-set | You clear it yourself |
| Registry lock | Server-set | Only the registry can remove it |
| 60-day hold | An ICANN eligibility rule based on time | Not a toggleable lock at all |
ICANN mandates a 60-day transfer lock after registration, transfer, or WHOIS changes. No registrar can override it. This matters enormously at final settlement. Some registrars have hold periods so that once a domain is transferred to the escrow agent, it cannot again be transferred to the purchaser for a period of time, such as 60 days, thereby creating an obstacle to the closing of the transaction.
If the holding account transferred the domain to its custody at the start of the deal — and the deal is, say, 24 months long — the 60-day hold is not a practical problem at final close. But if the escrow agent refreshed the domain registration, updated registrant contact information, or there was any intervening transfer during the term, a new 60-day clock may have started. If you change the registrant name or email and then try to initiate a transfer immediately after, you have triggered a 60-day lock that prevents the transfer until that period expires.
Within the same registrar, an account push can bypass the ICANN lock entirely. If the holding account and the buyer's target account happen to be at the same registrar, a push can complete the transfer at final settlement without waiting out any ICANN period. This is worth negotiating into the agreement upfront — specifying which registrar will hold the domain during the term and whether the buyer's receiving account must also be at the same registrar to enable a clean, instant transfer at close.
## Default mechanics and the settlement implications
Clear cure and default mechanics, along with escrow and registrar locks, reduce transfer risk if the buyer defaults. But these clauses are only useful if they are operationally connected to the payment flow.
In some structured LTO frameworks, if a payment is seven days overdue, DNS may be disabled. At fourteen days overdue, the agreement is terminated and the domain returns to the seller. The specific timeframes will vary by agreement, but the principle is the same: default triggers a sequential unwinding — first DNS access is restricted, then the agreement terminates, then the domain is released back to the seller.
If a buyer cancels a contract, they willingly forfeit any payments made up to the cancellation and there will be no refunds available. The domain is returned to the original seller and the buyer receives no ownership of the domain.
The settlement question on default is: what does the broker or closing attorney do with the commission that has already been distributed? If the broker was paid pro-rata on each installment and the deal defaults in month 14 of 24, the seller may expect the broker to return the unearned portion of the commission. This needs to be defined in the commission agreement. Experienced domain attorneys typically recommend a commission structure where the broker's fee is considered fully earned at signing, eliminating any clawback dispute on default — in exchange, the broker accepts that no additional commission accrues on installments they did not help originate.
## The multi-party settlement problem — and why it matters at final close
The most structurally underserved moment in an LTO deal is the final settlement. This is when everything is supposed to resolve at once: the buyer's last payment comes in, the domain transfers, the broker collects any remaining balance of their fee, and the seller receives the last installment. In a deal with two brokers — one representing the seller and one representing the buyer — and a separate escrow officer, that final payment needs to split into as many as four simultaneous streams.
In a traditional bank-wire settlement workflow, this requires either a manual disbursement memo from the escrow officer (who receives the full payment and then manually wires each party), or a series of sequential wire transfers that each carry their own banking delay and confirmation lag. The parties must trust the settlement agent to execute every disbursement correctly, and they have no way to verify in real time that every wire has landed.
This is precisely the operational problem that onchain payment routing solves. The provision in an annotated lease agreement makes clear that the escrow provider is not to hold onto funds until the end of the transaction but rather is supposed to disburse them to the lessor immediately once received. The intent — immediate disbursement upon receipt — is written into the contract. The execution, in a traditional wire-based workflow, rarely matches that intent.
Shaka.deal is built for exactly this moment. It is an onchain payment router on Ethereum that takes a single incoming payment and distributes it simultaneously to every party at preset shares, in one transaction, with finality. A closing attorney or escrow officer can configure the wallet addresses of the seller, the sell-side broker, and any co-broker or service provider before the deal even begins. When the final payment is routed through shaka.deal, every party receives their share in the same block — not sequentially, not subject to a manual disbursement queue. The router is non-custodial: it distributes funds, it never holds them.
This matters not just at final close but at every installment. In a 24-month LTO, there are 24 installment events, each of which creates the same multi-party disbursement problem. If each installment passes through a manual settlement process, the overhead accumulates — and so does the opportunity for timing errors, banking delays, and disputes about who received what and when.
With a preset payment routing configuration on shaka.deal, the disbursement logic is encoded once, before the first installment, and executes identically on every payment thereafter. The seller, the broker, and any other entitled party all receive their share simultaneously, without the closing attorney having to manually re-execute the waterfall each month.
## Structuring the agreement for clean settlement
The settlement professionals who will handle LTO deals most smoothly are those who treat the settlement architecture as a deliverable of the closing process — not an afterthought. Here is what that looks like in practice.
### At signing
- Define the commission structure unambiguously: is it earned at signing, at the first installment, or pro-rata over the term? Document what happens to earned commission on default.
- Specify the payment waterfall: who receives what share of each installment, expressed as a precise percentage or fixed dollar amount.
- Confirm which registrar will hold the domain during the term, and whether the buyer must open an account at that registrar to facilitate a clean final transfer.
- Incorporate the escrow service's agreement by reference, and check for any inconsistencies between the escrow terms and the lease terms. The escrow service provider will generally require that the parties additionally enter into an escrow agreement directly with the escrow service provider, which will also form part of the lease agreement. This agreement should also be reviewed, particularly for any inconsistencies with the domain name lease.
- Agree on who pays the escrow or holding fees. It is up to the parties to negotiate who pays the escrow fees; sometimes they are split.
### During the term
- Track the payment history with a formal ledger, not just email confirmations. The ledger should show each installment, the date received, the amount disbursed to each party, and the outstanding balance.
- Monitor the domain's EPP status codes at regular intervals. Every lock is recorded as an EPP status code on the domain, readable in a WHOIS or RDAP lookup. The codes that matter for transfers are `clientTransferProhibited`, set by your registrar, and `serverTransferProhibited`, set by the registry.
- Do not make registrant contact changes during the term without understanding the transfer implications. Never update registrant contact information immediately before planning a transfer. Always complete transfers first, then update contact information at the new registrar after the transfer completes.
### At final settlement
- Audit the domain's transfer eligibility at least 90 days before the expected final payment date.
- Prepare the disbursement instructions for every entitled party before the final payment is initiated — not after.
- If the deal involves an early payoff, recalculate the waterfall carefully. A buyer can complete payment for any remaining installments at any time in most LTO structures, and the commission earned on an accelerated payoff may differ from what was expected on a full-term deal, depending on how the commission agreement was written.
- Confirm that the transfer will not be blocked by a 60-day hold. If the domain has been in the same holding account since inception and no registrant changes occurred, the path should be clear. If there is any uncertainty, push rather than transfer if the parties' accounts are at the same registrar.
## Scenario: a three-party settlement with a Shaka routing configuration
Consider a fully brokered deal. The seller is a domain portfolio company. The buyer is a Series A startup. The sell-side broker is a boutique domain brokerage firm. The domain's agreed total price is $200,000 USD (~$308,000 AUD). The deal is structured as a 36-month LTO. Broker commission is 12 percent of total consideration, earned at signing and paid pro-rata across the installments. An escrow officer from a domain-specialist law firm is handling the closing and ongoing administration.
Each monthly installment is approximately $5,555 USD (~$8,555 AUD). Out of that:
- The broker is owed approximately $667 USD (~$1,026 AUD) per installment (12 percent).
- The escrow officer's monthly administration fee is agreed at a fixed amount, split between the parties per the agreement.
- The seller receives the remainder of each installment.
In a traditional wire workflow, the escrow officer receives the full installment, deducts the administration fee, sends a wire to the broker, and sends a separate wire to the seller. That is three disbursement events per installment, across 36 months — 108 individual wire operations to correctly administer a single deal. Each wire carries a banking delay. Each introduces a window for human error. None of them give the seller or broker real-time certainty that their share has been disbursed until the wire confirmation arrives.
With shaka.deal configured before the first installment, the broker's wallet address, the seller's wallet address, and any other entitled address are encoded as the preset distribution. Each month, when the installment payment is routed through shaka.deal, every party receives their share in a single onchain transaction. The payment is split, it is instant, and it is final — the same three properties for every one of the 36 installments.
The escrow officer in this scenario is not replaced. They are still the professional responsible for the agreement, the domain holding, the transfer mechanics at close, and the legal oversight of the whole arrangement. What Shaka.deal removes is the manual disbursement overhead — leaving the escrow officer free to focus on the substantive work of the deal rather than administering a waterfall of wire transfers every month for three years.
## The underappreciated value of finality
One dimension of onchain settlement that domain professionals sometimes overlook is the finality of the payment record. In a multi-year LTO, disputes can arise about whether a particular installment was paid, when it was received, and what share each party received. An onchain transaction record is immutable and publicly auditable — every disbursement in the Shaka.deal routing is recorded on Ethereum, with a timestamp and exact amounts, visible to all parties.
This is not a minor convenience. Using an escrow service has the benefit of having all payments facilitated and tracked by an independent third party. An onchain router extends that benefit further: the record is not held by the third party — it is held by the chain, accessible to every party regardless of what happens to any intermediary platform or service.
For the closing attorney who may need to produce payment records in a dispute, or for the broker who wants to demonstrate to their client exactly how each installment was disbursed, an onchain ledger from shaka.deal is a cleaner evidentiary record than a folder of wire confirmations and email threads.
## What this means for professionals who structure LTO deals today
Domain lease-to-own deals are becoming more common as premium domain prices rise and buyers seek structured financing paths. Buyers who cannot commit to paying a large lump sum upfront frequently abandon deals, leaving investors without revenue and buyers without the assets they need. Lease-to-own provides a middle ground that reduces friction, expands the pool of potential buyers, and turns domain names into structured cash flow vehicles.
As LTO volume grows, so does the operational load on the professionals who administer these deals — brokers tracking commission across multi-year terms, escrow officers managing monthly disbursements, and closing attorneys maintaining the administrative thread of an agreement that may run for five years.
The professionals who build the best settlement processes around these deals will be the ones who get referrals from both sides. That means engineering the disbursement waterfall before signing — not improvising it at close — and using tools that match the intent written into the contract: immediate disbursement upon receipt, to every party entitled, in one event.
That is exactly what shaka.deal delivers. One payment in. Preset shares. Simultaneous payout. Final settlement.