In this article
The domain market is global in a way that most asset classes simply are not. A seller in Melbourne, a buyer in New York, a broker earning commission in London, and a closing attorney whose retainer gets deducted at settlement — these four parties might all be involved in a single name changing hands. Domain sales are inherently international. The asset itself has no physical address. It can be owned, negotiated, transferred, and invoiced from anywhere. That reality is what makes two-currency closings so common — and so easy to underestimate.
This piece is written for the professionals who sit at the center of these transactions: the brokers who structure the deal, the settlement agents who coordinate disbursements, and the closing attorneys who ensure every dollar (or equivalent) goes to the right place. The mechanics below apply to any sale where the buyer's payment currency and one or more payee's receive currency do not match.
Worked example used throughout this article: a $180,000 USD domain sale (approximately AUD 279,000) to an Australian seller.
Why two-currency domain closings happen
The most straightforward version of this problem looks like this: a U.S.-based corporate buyer negotiates a purchase agreement denominated in USD ($200,000 / ~AUD 310,000 at a representative rate). The seller, however, is an individual investor based in Australia. The broker is based in the U.K. and invoices in GBP. The settlement agent sits in the middle.
Alternatively, a buyer may be paying in Australian dollars because that is where their operating entity is incorporated, but the seller has structured the deal to receive in USD because their portfolio accounting runs in USD. The contractual price is AUD ($210,000 AUD / ~USD 135,000), and the broker has agreed to a commission drawn from the sale proceeds, payable in USD.
In either scenario, the settlement agent faces three compounding problems at once:
- Denomination mismatch: The contract price is in one currency, but one or more payees receive in another.
- FX timing risk: The conversion rate at the moment the buyer's funds hit the escrow account is not the same as the rate at negotiation, at contract execution, or at the time the payees actually receive their disbursements.
- Sequencing risk: In traditional wire-based settlement, each disbursement goes out as a separate transaction. Each leg carries its own delay, its own conversion step, and its own moment of potential slippage.
Understanding each of these problems in depth is the only way to structure a closing that doesn't collapse under its own weight.
The anatomy of a standard two-currency domain deal
Consider a specific scenario that illustrates the full stack of complexity.
A U.S. startup agrees to buy a premium .com domain from an Australian domain investor. The purchase agreement is denominated in USD at $180,000 (approximately AUD 279,000). The deal involves the following parties and payment obligations:
- Seller: Australian individual. Wants to receive AUD into an Australian bank account.
- Sell-side broker: U.S.-based. Earns a commission payable in USD, to be deducted at closing.
- Closing attorney: Retainer billed against the deal, payable in USD.
- Buy-side broker: Also U.S.-based, with a co-brokerage agreement with the sell-side broker.
On larger deals there can be more players still. A six-figure sale might involve a broker on one or both sides, a lawyer reviewing the purchase agreement, and on the buyer's end a finance person who has to approve the wire.
The settlement agent's job is to ensure that when the buyer's $180,000 USD wire clears, every payee receives exactly what the purchase agreement says they should — simultaneously, without error, and without FX slippage that forces re-negotiation or a shortfall that someone has to absorb.
That is a harder problem than it looks when you are doing it with sequential wires and a spreadsheet.
Step one: Lock the denomination in the purchase agreement
The first decision — and the one most often left vague — is which currency governs the contract. This is not an academic distinction. It determines who bears FX risk, and for how long.
Option A: USD-denominated contract, AUD-denominated payout to seller. The seller agrees to receive the AUD equivalent of $180,000 USD at the rate prevailing at settlement. The seller bears the risk of USD/AUD movement between contract signature and closing. If the USD weakens materially, the seller receives fewer AUD.
Option B: AUD-denominated contract, USD-denominated payout to broker and attorney. The buyer agrees to send AUD 279,000. The broker and attorney receive whatever USD the proceeds convert to after the AUD lands. The broker and attorney bear FX risk.
Option C: USD-denominated contract with pre-agreed conversion rates. The parties agree in writing to a fixed AUD/USD rate for the seller's disbursement, typically the rate at contract execution. This protects the seller from adverse moves but may create a windfall or shortfall for the settlement agent depending on what the market does between execution and close.
Most experienced closing attorneys and brokers push for Option A with a clearly stated fallback: the seller receives the AUD equivalent at the rate on the date funds clear, and the contract records the USD amount as the governing figure. This approach keeps the USD total fixed and isolates FX exposure to the seller's disbursement leg — which is the leg the seller can hedge independently if the deal is large enough to justify it.
Commission fees are generally deducted from the sales price proceeds at closing. Parties should ensure the contract specifies who pays the commission, the exact percentage, and payment timing to avoid misunderstandings during the transaction.
That principle applies with even more force in a cross-currency deal. The purchase agreement should specify: the total deal price in the governing currency, the exact percentage or fixed amount owed to each payee, and the currency in which each payee will receive their disbursement. Any remaining FX exposure — who absorbs it, and at which exchange rate — should be resolved in the contract, not improvised on closing day.
Step two: Understand what a traditional wire-based close actually looks like
Once the purchase agreement is signed and the domain is in verified escrow, the buyer initiates a wire transfer. International wire transfers through SWIFT generally take 1 to 5 business days, with the exact timeline depending on the destination country, the number of intermediary banks in the chain, and public holidays in both the sending and receiving countries.
That delay is manageable. What is less manageable is what happens next.
Each intermediary bank adds processing time, and cross-border payments that touch multiple currencies often carry additional FX conversion steps that extend settlement further. On the inbound leg — the buyer's wire arriving at the settlement agent's account — the delay is one problem. On the outbound legs — the disbursements to the seller, broker, and attorney — the delays multiply.
Here is what that looks like on the ground in the scenario above:
| When | What happens |
|---|---|
| Day 0 | Buyer initiates a $180,000 USD wire. |
| Day 1–3 | Wire clears into settlement agent's USD account. |
| Day 3 | Settlement agent initiates outbound wires: USD commission to sell-side broker, USD retainer to closing attorney, and a USD-to-AUD conversion wire to the seller's Australian bank. |
| Day 4–6 | Broker receives USD. Attorney receives USD. |
| Day 5–8 | Seller's AUD lands in their Australian account — after the conversion has been applied, at whatever rate the settlement agent's bank offers that day. |
For international transfers, each intermediary bank in the SWIFT chain typically deducts its own processing fee before forwarding the funds, which means the recipient can land short of the full amount. Currency conversion adds another layer: banks apply their own FX rate on top of the mid-market rate, and that markup is rarely disclosed upfront.
The seller, who signed a contract expecting to receive approximately AUD 237,150, may receive AUD 231,000 or AUD 243,000 depending on how the USD/AUD rate moved across those five to eight days. That is not a small variance on a deal of that size. And because each disbursement goes out as a separate wire, there is no single moment where every party simultaneously receives their share. The co-brokerage split between the two brokers adds another wire, another set of banking fees, and another opportunity for shortfall.
The settlement agent's log becomes a multi-day reconciliation exercise rather than a clean close.
Step three: Recognize the FX risk window — and narrow it
The most consequential risk in a two-currency domain close is not the one that gets the most attention. Everyone worries about exchange rates at negotiation. The real exposure sits between the moment the buyer's wire is initiated and the moment every payee's disbursement lands in cleared funds.
A delayed or failed payment can expose the business to further currency movement if a returned payment must be converted and sent again.
For a settlement agent managing a $180,000 USD deal (approximately AUD 279,000) with a USD/AUD exposure window of five to eight business days, a 1% move in the exchange rate is $1,800 USD — roughly AUD 2,790. On a deal where the seller's net proceeds are the measure of a successful close, that variance is material.
Three practices narrow the risk window:
1. Use a pre-agreed spot rate. The settlement agent agrees with all parties in writing that the conversion will be executed at the rate available at a specific time on the day funds clear — often 9:00 AM in the destination time zone on the confirmed receipt day. This does not eliminate FX exposure, but it removes ambiguity about who decides the rate and when.
2. Execute conversion and disbursement on the same day. The settlement agent should not allow USD to sit in the escrow account for days while outbound wires are prepared. Convert and disburse on the day cleared funds are confirmed. Every day of delay is a day of unnecessary FX exposure.
3. Get all outbound wire instructions verified before inbound funds clear. Verify beneficiary details before release. Match the legal name, account information, bank codes, and currency to the payee's verified instructions. Wire rejections due to mismatched details can add two to five days to settlement, during which the FX window stays wide open.
None of these practices eliminates the structural problem: sequential wires take sequential time, and FX moves in the gaps.
Step four: How onchain routing changes the disbursement structure
This is where the architecture of the closing itself becomes relevant — not just the procedures around it.
The problem with sequential wire-based settlement is structural. Each disbursement is its own transaction, initiated separately, subject to its own processing time, its own correspondent chain, and its own moment of FX conversion. The settlement agent acts as the hub, which means every error, delay, or shortfall flows back through that hub before it can be corrected.
Onchain payment routing takes a different architectural approach. Instead of disbursing proceeds through a sequence of outbound wires initiated by the settlement agent, a routing layer distributes the total proceeds to every payee simultaneously in a single transaction, according to preset shares that have been agreed and configured before the funds arrive.
This is exactly what shaka.deal is built to do on Ethereum. The settlement agent — or the broker, or the closing attorney coordinating the close — configures the deal: total amount, each party's share expressed as a percentage or fixed amount, and each party's receiving address. When the buyer sends the agreed amount in USDC (a dollar-pegged stablecoin), the router distributes it to every payee in one transaction, instantly, with settlement finality. There is no hub waiting to initiate sequential wires. There is no second wire that lands two days after the first.
A customer sends USDC directly to a payment address on a blockchain. The transaction confirms in minutes. It is mathematically final. No participant can reverse it, no bank can put a hold on it, no dispute process can claw it back.
That finality matters enormously for professionals managing a closing. In traditional wire settlement, the settlement agent holds proceeds while each outbound wire is confirmed. During that window, the funds are in limbo. With onchain routing, the distribution happens at the moment the inbound payment clears. The seller's share, the broker's commission, the co-broker's split, and the attorney's retainer all move in the same block. The settlement agent does not hold anything — the router handles the split and pays everyone out the moment the deal funds.
Shaka.deal is non-custodial: it routes the total amount and distributes it to every party at preset shares in one transaction. It never holds funds. The deal either routes or it does not — there is no partial state, no pending disbursement queue, no manual release step.
Step five: Handling the two-currency problem specifically with stablecoins
The two-currency problem does not disappear with onchain routing — but it becomes more controllable. Here is how it changes.
The FX conversion moves to the edges, not the middle. In a traditional close, the settlement agent's bank converts USD to AUD as part of the disbursement process. The rate the seller receives is determined by the settlement agent's banking relationship, at the moment the settlement agent initiates that wire. The seller has no visibility into that rate until after the fact.
With onchain routing, the Australian seller has two clean options:
Option A: Receive USDC. The seller opens a USDC-capable wallet, provides their onchain address, and receives the USD-equivalent of their share in USDC at the moment the deal closes. You price in dollars, invoice in dollars, and receive in USDC, which is dollars on a blockchain. The seller then converts USDC to AUD using the offramp or exchange of their choice, at the time of their choosing, at a rate they can compare and control. The FX moment is the seller's to manage, not the settlement agent's.
Option B: Use a convert-on-receive offramp. A "convert-on-payout" model allows funds to remain in USDC until the moment of disbursement. At that point, funds are converted and settled locally, which reduces FX risk and ensures recipients are paid in their preferred currency. Some Australian offramps offer this: the seller registers their AUD bank account with the offramp, provides their USDC address in the deal configuration, and receives AUD automatically when USDC arrives. The conversion happens at the offramp's posted rate on the day of receipt, which the seller can review in advance.
Either option gives the seller more control over their AUD outcome than a wire conversion initiated by someone else's bank at an undisclosed spread.
The USD payees — the broker, co-broker, attorney — receive USDC instantly. They do not need to wait for sequential wires. Their shares distribute at the same moment as the seller's. Because USDC operates on blockchain rails, funding becomes instant and continuous. Businesses can deploy liquidity in real time — 24/7, including weekends and holidays — without waiting for bank cut-offs or settlement windows.
This matters practically. A deal that closes on a Friday afternoon does not mean the broker waits until Monday for their commission. A deal that closes during a U.S. public holiday does not stall because bank wire rooms are closed. The onchain router does not have business hours.
Step six: Working the concrete numbers
Return to the original scenario: $180,000 USD purchase price (approximately AUD 279,000), with the following agreed disbursements:
| Payee | Share | USD | AUD (approx.) |
|---|---|---|---|
| Seller | 85% net | $153,000 | AUD 237,150 |
| Sell-side broker | 10% commission | $18,000 | AUD 27,900 |
| Co-broker | 3% | $5,400 | AUD 8,370 |
| Closing attorney | 2% retainer | $3,600 | AUD 5,580 |
| Total | 100% | $180,000 | AUD 279,000 |
In a traditional wire-based close, the settlement agent receives $180,000 USD, then initiates four separate outbound wires. The attorney receives their retainer on Day 4 to 6. The broker receives their commission. The co-broker, who is in a different time zone, receives their share a day later. The seller's USD is converted to AUD and a wire is initiated on Day 3 — landing in the seller's Australian account on Day 5 to 8, at whatever rate the bank applied.
The seller's $153,000 USD (approximately AUD 237,150 at contract rates) might arrive as AUD 231,000 or AUD 243,000 depending on rate movement across that window. That is a range of several thousand AUD on a single closing, for a sophisticated seller who understood and accepted the deal terms.
With shaka.deal configured for this closing, the deal setup is: total amount $180,000 USDC; addresses and share percentages for each of the four payees. When the buyer sends $180,000 USDC to the deal address, the router distributes each share in the table above, in USDC, to the seller's wallet, the sell-side broker, the co-broker, and the closing attorney — all in the same transaction. No days of delay between disbursements. No sequential wire queue. No FX conversion performed by a bank the seller never chose.
The seller then converts their $153,000 USDC to AUD using their preferred offramp — today, not in five days. The broker and co-broker have their commissions in cleared form immediately. The attorney can confirm receipt before the closing call ends.
Step seven: What settlement agents and brokers need to prepare
Adopting onchain routing for a domain closing is a procedural change, not a philosophical one. The settlement agent's role remains exactly what it is: coordinating the parties, managing the purchase agreement, verifying disbursement instructions, and confirming that the transfer has completed. The difference is in the mechanics of how funds move.
Practically, the steps look like this:
Before the deal is signed:
- Confirm that all payees can receive USDC and have an Ethereum-compatible wallet address. For the Australian seller, confirm whether they want to receive USDC and convert independently, or use an AUD-denominated offramp.
- Confirm that the buyer is able to fund in USDC, or will fund via a USD-to-USDC on-ramp before initiating payment.
- Document each payee's wallet address and share in the purchase agreement. Treat wallet addresses with the same verification rigor as bank wire instructions. Confirm new banking details through a known contact rather than replying to a change request. The same principle applies to wallet addresses — confirm through a live call or authenticated channel, not through an email reply.
At closing:
- Configure the shaka.deal routing: total amount, each payee's address, each payee's share. Review the configuration with every party before the buyer funds.
- Provide the buyer with the deal address.
- Confirm onchain that the distribution has completed before finalizing the domain transfer or releasing the auth code.
After closing:
- Issue a closing statement that reflects the USDC amounts distributed to each payee, the USD value at the time of distribution, and — for the seller — the USDC amount converted to AUD along with the offramp rate applied. This is the onchain equivalent of a wire disbursement log and should be retained for the same period.
Domain name escrow services have handled complicated transactions including multi-party domain name swaps, three or more party-financed transactions, with payments coming in and going out in multiple currencies as well as cryptocurrencies. The professionals doing that work already understand multi-party disbursements. What onchain routing adds is the ability to execute all of those disbursements simultaneously rather than sequentially, with a transparent on-chain record that every party can verify independently.
The closing attorney's perspective: finality versus reversibility
One question that comes up repeatedly among closing attorneys encountering onchain settlement for the first time is about finality. Traditional wire transfers can, in some circumstances, be recalled. Onchain transactions cannot.
This is not a flaw. It is a feature that directly serves the attorneys and settlement agents managing the close.
In a domain transaction, the seller transfers the domain to the buyer — typically by releasing the auth code or initiating a registrar push — based on the expectation that payment has been received. If payment is reversible after the domain has transferred, the seller has lost the asset and may be chasing funds through a banking dispute process. Onchain settlement is mathematically final.
For the closing attorney, that finality means the moment the onchain router confirms distribution, the payment leg of the transaction is complete. There is no "funds pending clearance" limbo during which the domain has transferred but payment is still technically reversible. The closing statement can be issued. The transaction can be marked closed. Everyone can stop watching their wire tracking portals.
Escrow works in five steps: buyer and seller agree on terms, buyer funds the escrow account, seller transfers the domain into the buyer's registrar, escrow verifies the transfer against WHOIS, and escrow releases funds to the seller. That sequential dependency — fund escrow, transfer domain, verify, release — is the structure that keeps both parties safe. What onchain routing does is collapse the release step from a multi-day, sequential disbursement queue into a single, simultaneous, irreversible distribution. The structure remains. The wait does not.
Common failure modes in two-currency closings — and how to avoid them
Failure mode 1: Rate not specified in the contract. The seller agrees to receive AUD but the contract says "$180,000 USD" without specifying the conversion method. At closing, the settlement agent uses their bank's rate, which includes a spread of 1.5% over mid-market. The seller receives materially less AUD than they expected. Dispute follows.
Prevention: The purchase agreement specifies either a fixed rate (agreed at execution), a rate source (e.g., RBA daily rate on the day of cleared funds), or an explicit acknowledgment that the seller will receive USDC and convert independently.
Failure mode 2: Wallet address error. The sell-side broker provides a wallet address by email. A malicious actor intercepts the email and substitutes a different address. The broker's $18,000 USDC routes to the wrong address and cannot be recovered.
Prevention: All wallet addresses must be confirmed via a live video call or authenticated portal — never via an email reply chain. This is address verification hygiene and should be a non-negotiable close requirement.
Failure mode 3: Buyer funds in the wrong asset. The buyer sends ETH instead of USDC, or sends to the wrong network. The deal address receives the wrong token.
Prevention: The closing confirmation document should specify: asset (USDC), network (Ethereum), exact deal address, and exact USD amount. Send the buyer a test transaction confirmation requirement for large deals — a small amount sent first, confirmed by the settlement agent, before the full amount is initiated.
Failure mode 4: Disbursement assumed complete before onchain confirmation. The settlement agent releases the auth code as soon as the buyer sends the transaction, before the onchain distribution confirms.
Bringing it together: the professional's checklist
A two-currency domain closing is manageable when every variable has been resolved before funds move. Here is the condensed checklist:
- Governing currency confirmed in the purchase agreement (USD or AUD)
- Each payee's disbursement currency confirmed and documented
- FX conversion method confirmed for the cross-currency payee (independent USDC conversion vs. offramp)
- All wallet addresses verified through authenticated channel, not email reply
- Deal configured in shaka.deal: total amount, each address, each share percentage
- All parties have reviewed and confirmed the configuration before buyer funds
- Buyer funds USDC to deal address
- Onchain distribution confirmed before domain transfer is initiated
- Closing statement issued with USDC amounts, USD values, and (for AUD payee) offramp rate
The domain market will only continue to get more international. Transactions with payments coming in and going out in multiple currencies, including cryptocurrencies, are already being handled in sophisticated closings. The professionals who build repeatable procedures for two-currency closings today — and adopt routing infrastructure that eliminates the sequential disbursement problem — will be the ones who close faster, with less re-work, and with clients who come back.
The tool for the routing part is shaka.deal. The judgment, the structure, and the professional relationships are still yours.
