How a cross-border domain buyer pays the seller
The domain aftermarket is fundamentally international. The name a company in Singapore needs might be held by an investor in Germany. The brand a founder in São Paulo is building could depend on a .com registered to someone in Toronto. When a deal crosses a border, the question of how money actually moves — which rails it travels, who bears the currency risk, where it slows down, and how each party eventually gets paid — becomes the most operationally consequential part of the transaction. This article covers that mechanic in full: the payment sequence, the structural friction points, how a broker or advisor orchestrates settlement when the parties are on opposite sides of the world, and what clean disbursement looks like when the deal finally closes.
Why cross-border domain payment is a different problem
A domestic domain deal is already more complex than it looks. A cross-border one layers on currency denomination, correspondent banking, compliance holds, registrar restrictions, and time-zone gaps — all simultaneously.
In international domain sales, contracts take on additional complexity because of the involvement of parties from different legal jurisdictions. That complexity doesn’t stop at the contract. It runs straight through the payment infrastructure. A common misconception is that an international money transfer moves directly from the buyer’s bank to the seller’s bank in a straight line. In reality, cross-border settlement takes place within a sprawling, highly fragmented network of multiple independent financial institutions.
For the broker or advisor handling the deal, this matters in a very practical way. You’re responsible for ensuring funds arrive intact, in the right amount, to the right parties. Understanding the path money takes — and where it bleeds value — is part of doing your job well.
The currency question comes first
Before a single wire instruction is issued, there is a decision that shapes everything downstream: what currency denominates the deal?
The vast majority of premium domain transactions are quoted and settled in US dollars, regardless of where the buyer or seller is located. The US dollar is widely accepted as an international trading currency, and companies can often secure payment in dollars. If the buyer asks to make payment in a foreign currency, you should consult an international banker before negotiating the sales contract.
Pricing the deal in USD puts the currency conversion obligation on the buyer. That buyer’s bank must acquire dollars, which introduces exchange-rate exposure on their end. A buyer paying from a EUR, GBP, or JPY account will send their local currency to their bank, which converts it and transmits dollars into the payment chain. The seller receives dollars and avoids FX risk entirely — but this doesn’t mean the deal is clean. It means the seller has transferred the FX problem to the buyer rather than eliminating it.
There is a counter-argument for invoicing in the seller’s local currency. One of the risks associated with foreign trade is the uncertainty of future exchange rates. The relative values of the two currencies could change between the time the deal is concluded and the time payment is received. If you are not properly protected, a devaluation or depreciation of the foreign currency could cause you to lose money. On a $250,000 domain sale, a 2% currency move between signing and wire receipt is $5,000 walking out the door. The practical answer for most domain professionals is to denominate in USD, confirm that figure clearly in the agreement, and require the buyer to send USD regardless of their home currency.
How the wire actually travels
Once currency is decided and payment is initiated, the mechanical question is: what route do those funds take?
A fundamental challenge with international payments is that banks in different countries often use systems that don’t naturally connect. Wire transfers bridge those gaps with the SWIFT network, which connects thousands of banks worldwide and ensures standardized communication between them.
What SWIFT actually does is often misunderstood. SWIFT does not move the money itself; it sends secure payment messages between financial institutions. The actual value transfer happens through correspondent relationships — chains of banks that hold accounts with each other and move funds by book entry.
With a domestic wire transfer, money is transferred directly from your bank account to the recipient’s bank account. A SWIFT payment, however, may have to pass through multiple banks — called “intermediaries” or “correspondent banks” — before the money reaches its final destination.
Here is a real-world illustration of what this looks like. Say you want to send a SWIFT payment from Wells Fargo in the US to Westpac in Australia. If Wells Fargo and Westpac do not have a direct relationship, the payment will be routed through an intermediary bank — in this case, HSBC in Hong Kong. The payment will first be transferred from Wells Fargo to HSBC, and then from HSBC to Westpac. And each time the money is transferred, a fee might be levied on the payment.
On a smaller domain sale — say $15,000 — those intermediary deductions matter. SWIFT transfer fees typically range from $25–$50 for sending, $10–$20 for receiving, plus $10–$30 per intermediary bank involved. Currency conversion markups of 1–4% over the mid-market rate add to the total cost.
The practical consequence: cross-border transactions often involve multiple banks and currency conversions, which can lead to additional fees or deductions taken by the banks involved and potential exchange rate markups. This can result in the end recipient not receiving the full amount of funds sent. If the seller is expecting $15,000 and receives $14,730, the deal math changes for everyone — the seller’s net, the broker’s commission calculation, the escrowed release amount. These variances are not theoretical. They happen on every corridor that involves correspondent banking.
Timing is equally unpredictable
International transfers typically require 1–3 business days but can take longer, varying by destination country, local bank holidays, banking relationships, and regulatory requirements. On the longer end, the sending of a SWIFT payment can take up to four working days to be completed, and even longer for the receiving bank to clear the funds into the recipient’s account.
For a deal that has a hard closing date — a corporate rebrand launch, a legal deadline, a parallel trademark filing — this timing uncertainty is real operational risk. The broker who fails to account for it and wires the day before a deadline is the one fielding calls at 7am about a payment that hasn’t cleared.
Initiating transfers during weekends or holidays may result in delays, and currency conversion adds extra processing time. Verification and compliance checks, particularly for larger transactions, contribute to processing delays. On deals in the six-figure range, banks on both ends tend to flag and review. A $300,000 wire from a first-time buyer in South Korea to a seller account in the Netherlands may sit in compliance review for twenty-four hours before it moves. This is normal. It is not a sign something is wrong. But the professional managing the deal needs to build this buffer into the timeline.
The role of the payment structure in cross-border deals
Direct wire from buyer to settlement account
On straightforward deals where the parties know each other, have dealt before, or the buyer is a large company with in-house treasury, funds sometimes move by direct wire to the seller’s designated settlement account. The transfer instrument is a SWIFT message carrying the payment details, and the receiving bank credits the account once it clears.
This works cleanly when the buyer is sophisticated and the verification layer is already built into the relationship. But in most brokered cross-border transactions, neither party wants to go first without protection — the seller won’t transfer the domain without confirmed funds, and the buyer won’t send funds without confirmed they’ll receive the domain. This is where a third-party payment holder enters.
Settlement through a licensed third party
Licensed services handle international domain transactions with multi-currency support. Transactions with buyers outside the United States incur an additional fee to cover intermediary bank fees. International use of such services is highly recommended due to added complexity of cross-border payments and varying legal jurisdictions.
The mechanics work like this: the buyer wires funds to a settlement account held by a licensed third party. The third party verifies receipt and notifies the seller to initiate the domain transfer. The seller transfers the domain to the buyer. The buyer confirms receipt. One of the ways this is done is by checking the WHOIS database of the appropriate registrar to confirm it properly reflects the new buyer’s name as the domain registrant. Once this has been verified, payment is released to the seller.
The full transaction process — buyer payment, seller transfer, buyer verification, payment release — takes 3–7 business days. Total timeline: 3–7 business days. For international transactions, experience suggests assuming the upper end of that range as a baseline. The verification steps that take one business day domestically often take two internationally, simply because of time zones and correspondent bank clearing windows.
The fee allocation question
In a cross-border deal, there are fees on multiple layers: the third-party settlement fee, the sending bank’s wire fee, the intermediary bank deductions, and the receiving bank’s incoming wire fee. The sender can choose who pays the fees using codes: OUR (sender pays all fees), SHA (fees are shared between sender and receiver), and BEN (receiver pays all fees).
For domain deals specifically, this instruction matters to the seller. If the buyer sends a wire marked SHA or BEN, the seller may receive less than the agreed purchase price, and the broker’s commission — if calculated on net proceeds — shrinks accordingly. The cleanest structure for a seller-side broker is to specify OUR in the wire instructions and make that a deal term, or to gross up the wire amount to account for expected deduction. Documenting this in the purchase agreement before closing saves the renegotiation after.
What the broker actually manages in a cross-border deal
The broker’s job in a cross-border transaction is substantially more involved than the domestic equivalent. Many brokers handle international deals regularly. They navigate currency conversions, time zones, language barriers, and international escrow arrangements.
At a practical level, this means:
Identifying the right settlement vehicle. Not every platform accepts wires from every country. Some have restrictions on buyers domiciled in certain jurisdictions. Some have payment method limitations — credit card may not be available for cross-border buyers, or may carry surcharges that affect net proceeds. The broker determines which settlement structure works for the specific buyer-seller corridor before the deal term sheet is signed.
Setting the wire instructions precisely. Each wire may require entering SWIFT/BIC codes, IBAN numbers, routing details, and recipient bank addresses — and re-entering them for repeat payments. One wrong digit can cause a transfer to fail or be delayed, triggering additional fees and recovery time. On a cross-border deal, getting these instructions from the settlement account, verifying them independently, and transmitting them in writing to the buyer’s treasury team is a non-negotiable step.
Managing timeline expectations on both sides. A buyer in Japan who sends a wire on Friday afternoon Tokyo time may not have it clear in a New York-based settlement account until Tuesday. This is not negligence. This is how correspondent banking works across that corridor. The broker who explains this upfront avoids a seller calling on Monday morning asking why nothing has cleared.
Watching for deductions before release. When funds arrive at the settlement account, the broker or advisor confirms the amount received matches the deal amount. If there’s a shortfall due to intermediary deductions, this is the moment to resolve it — either by requesting a top-up wire or by adjusting net proceeds calculations before disbursement.
The currency risk window between signing and settlement
One of the most underappreciated risks in cross-border domain transactions is the gap between when the deal is signed and when funds actually clear. On a fast domestic deal this window might be 48 hours. On a cross-border deal it can stretch to two weeks or more, particularly if the buyer is navigating internal treasury approval processes, internal compliance review for large transactions, or bank-level AML screening.
The relative values of two currencies could change between the time the deal is concluded and the time payment is received. If you are not properly protected, a devaluation or depreciation of the foreign currency could cause you to lose money.
The practical solution for deals denominated in USD is straightforward: require payment in USD. The buyer absorbs the conversion cost and rate risk on their end. But for deals where the seller has agreed to accept payment in a foreign currency — or where the settlement account receives in local currency and pays out in a different one — there is genuine exposure. The most direct method of hedging foreign exchange risk is a forward contract, which enables the seller to sell a set amount of foreign currency at a pre-agreed exchange rate with a delivery date from 3 days to 1 year into the future. On significant transactions this is worth discussing with the seller before closing.
Credit card payment from a foreign buyer
Some domain deals — particularly those in the $5,000 to $50,000 range — involve foreign buyers who prefer to pay by credit card. The card network enables them to pay in their home currency while the settlement account receives in another. This is convenient for the buyer. It is not without consequence.
Credit card payments on cross-border domain deals carry two structural problems. First, the processing fee for a credit card payment is higher than for a wire — credit cards add 2–3% processing fees on top of standard settlement fees. On a $30,000 sale, that’s $600–$900 in additional cost that needs to be allocated between buyer and seller.
Second, and more seriously, credit cards introduce chargeback risk. A buyer who wires funds cannot reverse that wire. A buyer who pays by credit card can dispute the transaction. Unlike PayPal or direct credit card payments, settlement through proper domain escrow prevents buyer chargebacks after receiving the domain. In a cross-border context, the chargeback risk is heightened: the buyer is in a different jurisdiction, currency conversion creates transaction amount ambiguity, and the cardholder’s bank may default to the buyer’s account in any dispute with a foreign seller. The professional advice for high-value international domain deals is to require wire transfer — not as a formality, but because it eliminates the reversal risk entirely. Wire transfers are traceable and generally irreversible, making them an ideal choice for high-stakes transactions.
Installment deals across borders
A growing segment of premium domain sales — particularly those above $100,000 where the buyer is a startup or a business unit that needs to stage the payment — are structured as installments. The domain may be held by the settlement service during the payment period, with ownership transferring only when the final payment clears. In a Domain Name Holding Service transaction, the buyer makes a down payment and the seller transfers the domain to the holding service. The domain is held during a predetermined period while payments are made through that service during the term. At the end of the term when all payments are completed, the domain is transferred to the buyer.
For cross-border installment deals, each monthly payment is a cross-border wire. Each one carries its own potential for intermediary deductions and timing variation. The broker managing this structure needs to establish wire instructions clearly at the outset and ensure the buyer’s treasury is set up for recurring international payments — not one-time wire processing. A buyer whose accounts payable department has to create a new wire vendor for each installment will create delays. Getting this infrastructure in place before the first payment is due is the broker’s job.
If payments to the seller are made monthly and each involves a transaction fee, these can add up. On a twelve-installment deal at $10,000 per payment, incoming wire fees on the seller’s end and intermediary deductions can collectively consume a material percentage of a later payment. Structuring the deal amount to arrive net of these costs — or confirming OUR instruction with the buyer — prevents a shortfall on the final installment from creating a closing dispute.
The ccTLD complication
Most of the mechanics above apply cleanly to generic TLD transactions — .com, .net, .org, .io, and similar extensions that transfer through standard registrar push or transfer protocols. Country-code TLDs (.uk, .de, .fr, .jp, .au, and others) carry additional complications in a cross-border transaction.
Some ccTLD registries require the registrant to have a local presence in the relevant country. A Korean company acquiring a .de domain may need a German administrative contact. An American buyer acquiring a .co.uk may need a UK-registered entity or address. These requirements do not affect the payment itself, but they affect whether the domain can actually be transferred to the buyer after payment clears. The broker or advisor confirming deal terms on a ccTLD cross-border acquisition must verify registry eligibility before the buyer initiates any payment.
Lease-to-own and certain installment structures are available for most domains, but there are exceptions including most country code top-level domains. If a ccTLD isn’t eligible for standard installment structures, the deal may need to be structured as a direct purchase with a full wire, which changes the buyer’s cash flow requirements and, potentially, their willingness to proceed at a given price.
Disbursement: how the money lands after it clears
A brokered cross-border deal rarely has a single payee. The seller receives their net. The broker receives their commission. Sometimes a co-broker or referral partner is owed a split. Sometimes legal fees are deducted at settlement.
In sell-side representation, the seller pays from their proceeds. Some high-value deals involve split commission structures where both parties contribute. On cross-border deals, this disbursement step introduces its own friction: the settlement account must pay out to multiple wallets or bank accounts, potentially in different countries. Each payee may require a separate wire. Each wire is a separate SWIFT message, a separate fee, a separate clearing window.
Traditionally, this means the closing attorney or escrow agent disburses sequentially: one wire to the seller, a separate wire to the broker, a separate wire to any co-broker. Each wire is processed independently, clears independently, and may arrive on different days. A seller in Hong Kong may receive their net two days after a broker in London receives their commission, because they happen to be on different banking corridors.
This is where the mechanics of how money lands — not just when it moves — become a real professional concern. When a deal closes, the professional who structured it should be confident that funds reach every designated recipient in the agreed amount, in one clean sequence, without chasing individual wire confirmations across time zones.
Shaka is built for exactly this moment. The broker sets the payment link before closing — seller wallet, broker wallet, any split to a co-broker — and defines the percentages. When the buyer funds the deal, the payment routes directly to every wallet simultaneously, in one transaction. The broker doesn’t wait to see if the secondary disbursement wire cleared. Every party is paid at the same instant the deal closes.
Verifying the domain transfer against payment release
One of the clearest failure modes in cross-border domain deals is a timing mismatch between payment and transfer. A seller who releases the domain before payment confirmation is relying on trust. A buyer who sends payment before the domain is locked for transfer is equally exposed.
One of the most important aspects of international domain sales is the contractual agreement between buyer and seller. Like any business transaction, the sale of a domain name must be governed by a contract that clearly outlines the terms of the sale, the payment process, and the transfer of ownership. In cross-border deals this means specifying in writing: what triggers the seller’s obligation to initiate the domain transfer, what confirms receipt of that transfer, and what triggers payment release. A deal sheet that uses language like “upon payment” without defining what constitutes confirmed payment — cleared funds vs. wire initiated vs. notification received — creates ambiguity that becomes a dispute in the 5% of cases where something goes wrong.
The cleanest structure: buyer funds to settlement account, settlement account confirms receipt of cleared funds, seller initiates domain transfer, WHOIS confirmation triggers payment release. Every step documented, every confirmation in writing. For a broker managing the deal, this is not bureaucracy — it is the only professional way to handle someone else’s money across a border.
The practical checklist before you wire anything
Before a cross-border domain payment moves, the professional managing the deal should have confirmed: the deal currency and the wire instruction — specifically whether it’s OUR, SHA, or BEN; the full SWIFT/BIC code, IBAN or account number, and bank address for the receiving account; the expected clearing window for that specific corridor; whether the settlement account has any incoming wire restrictions or minimum transfer requirements; whether the domain’s TLD has any registry eligibility requirement that the buyer must satisfy before transfer; and what documentation the buyer’s bank will require to approve a large wire to a foreign payee — some corporate treasury departments need a copy of the purchase agreement.
Because parties in different countries may use different currencies, the contract should specify the currency in which the payment will be made and the exchange rate that will apply if necessary. This can help avoid disputes over fluctuating currency values and ensure that both the buyer and seller understand the financial terms of the deal.
Getting these terms confirmed in writing before the wire is initiated — not during — is what separates a professional close from an improvised one.
What clean settlement actually looks like
A well-structured cross-border domain deal closes as follows. The purchase agreement specifies USD, wire transfer, OUR instruction, with a defined clearing window. The buyer initiates the wire with correct SWIFT/BIC details to the settlement account. The broker monitors confirmation from the settlement account that cleared funds have arrived — not just that the wire has been initiated. Upon confirmed receipt, the seller transfers the domain. WHOIS confirmation triggers fund release. Every party designated in the disbursement schedule receives their amount.
The seller is in Tokyo. The broker is in New York. The co-broker is in London. None of that geography should determine who gets paid first, or whether anyone has to wait for a secondary disbursement wire to clear. The money should land for everyone at the same moment the deal is done.
That outcome — funds arriving cleanly, splits disbursed instantly, no chasing confirmations across time zones — is the standard worth building toward. Cross-border domain transactions have genuine structural complexity in how money travels. But the complexity lives in the path, not in the destination. The professional who understands the path can engineer a closing where the destination is clean for everyone.
