Onchain TLDs and retailers: what to check

Retail brands carry a structural characteristic that most sectors do not: the name on the storefront is also the name on the payment flow, the name shoppers type into loyalty apps, the name that appears on returns portals, and the name that third-party sellers invoke to describe what they sell. That density of touchpoints matters when the organization’s name also exists as an onchain top-level domain (TLD), an extension such as .yourbrand that is recorded on a blockchain and held as a token in a wallet. The surface for confusion is then wider than it first appears.

This guide is written for the head of legal or the head of fraud at a retailer. It explains why the retail context widens the general onchain TLD question, maps where in the organization the exposure lands, and gives a checklist that can be delegated the same day. The general mechanics of onchain naming are kept to a short passage, because the value here is the sector analysis.

By the end you should be able to brief your brand protection team on what to check, allocate ownership across functions, and make an informed decision about whether to acquire the TLD, monitor it, or both.

Why retail is different from a generic brand

Most analyses of onchain TLDs from a brand’s point of view focus on reputation: a name issued under a TLD that reads like a well-known brand is used to lend credibility to a message the brand never sent. That exposure exists in retail too, but it sits inside a much larger operational envelope.

A professional services firm, a manufacturer or a media company meets its end audience at a low frequency and through a limited number of named channels. A retailer meets shoppers at the point of transaction, repeatedly, across every channel at once: the website, the app, the physical store, the returns flow, third-party marketplaces, affiliate networks, loyalty programs and seasonal campaign microsites. Each of those channels is a place where a name is displayed to a shopper, and where a name the retailer did not issue could be displayed instead.

Retail also operates in a context where shoppers are already in a payment mindset. The gap between seeing a name and paying is often a single screen. That compression makes any name confusion at checkout more consequential than the same confusion at the awareness stage of a business-to-business purchase. A shopper who is already committed to buying and sees pay.yourbrand in a wallet or a payment link is thinking about completing the transaction, not about where the name comes from.

Two further factors compound this. First, retailers frequently operate several named entities: the parent company, regional banners, private labels and franchise partners, each of which is a name that may exist as a TLD. Second, retail names tend to be short, descriptive and easy to recall, which are the same properties that make a TLD attractive to someone who did not create the brand.

The honest limit belongs here as well. Most shoppers never see an onchain name, because most retail payments run on cards and on the ordinary web, where the DNS and the existing controls do their work well. The exposure described in this guide concerns the shoppers, suppliers and partners who use wallets and onchain payment links. For a retailer that group may be small. It is still the group for which the name on screen is the only signal available.

Brand and legal teams working in retail therefore have reason to treat the onchain TLD question as an operational one as much as an intellectual property one, with direct lines into fraud, payments, customer experience and compliance.

The onchain TLD in brief

An onchain TLD is an extension recorded on a blockchain instead of being delegated by ICANN. On Freename, the registry this guide refers to, the TLD is a token that sits in a wallet, and whoever controls that wallet controls the TLD. A retailer’s legal or fraud team can check the registry record on a block explorer, as can anyone else, because the record is public. Names under the TLD come from one source only, its holder, so store.yourbrand, pay.yourbrand and returns.yourbrand can be created by whoever holds .yourbrand and by nobody else.

These names are resolved outside the ICANN DNS root, so a standard browser does not open them unaided. Support exists in Bitcoin.com Wallet, in MetaMask by way of Freename’s resolver, and in desktop browsers that run the Freename Web3 extension. That coverage is partial and it changes, so no scenario in this guide assumes that every shopper can resolve a name. Which capabilities work, and on what sources, is set out on the page on what is live.

The UDRP, the dispute procedure for conventional domain names, binds registrants through the contracts of the ICANN system. An onchain registry is not part of that system, so the procedure does not reach it. Your counsel decides how to characterize that gap and what remedies remain, which vary by country. This guide describes the situation, not the legal strategy.

Checkout and refunds: where the name reaches the shopper

The payment flow is the surface with the highest consequence in retail. A name that appears at checkout carries implied authorization: the shopper assumes they are paying the retailer. When that name belongs to someone else, the assumption is wrong and the consequence is financial and immediate.

Onchain payment tools make this concrete. A payment link can pay out to a name in place of a long wallet address. With a payment router such as shaka, the parties agree and sign the split onchain before any funds move, and the router passes funds through without holding them. For a retailer, the practical point is that any name issued under .yourbrand could be presented as a payment destination, and a shopper who sees pay.yourbrand in a wallet interface may not distinguish it from the retailer’s own infrastructure.

At the till and after the sale

Retail has payment moments that other sectors lack. A code scanned at the till, a link on a digital receipt, a top-up of a gift card balance, a deposit on a large item, a click-and-collect confirmation: each is a moment where the shopper expects a payment prompt and expects the retailer’s name on it. None of these moments involves an onchain name unless the retailer chooses to use one. The exposure is that the shopper cannot know that, and has no list of the payment names the retailer does and does not use.

The refunds channel carries a parallel exposure, with one difference: the shopper is expecting to receive money, not to send it. A message that offers a refund and asks for details, sent under a name that reads like the retailer’s own TLD, borrows legitimacy from the name itself in a way that an unrelated address does not. Returns are also a moment of mild frustration, which makes a message that promises a faster refund welcome. Customer experience teams who own the returns portal should be part of any TLD review for that reason.

How the name is displayed in a wallet

When a shopper uses a wallet that supports Freename resolution, names are displayed as readable identifiers in place of long strings of characters. A name like refund.yourbrand would be displayed exactly as written, and a shopper unfamiliar with onchain naming would have no indication of who issued it. The page on payments to a name explains how a name is used as a payment destination.

The same display works in the retailer’s favor once the TLD is in its hands. A readable name that only the retailer can issue is a stronger signal than a string of characters nobody can check by eye. The exposure and the benefit are the same mechanism seen from two sides, which is why the checkout team should hear about both.

Marketplaces and third-party sellers

Retail is one of the few sectors where the brand name is actively used by parties who have no formal relationship with the brand owner. Third-party sellers on marketplace platforms use the retailer’s name in product titles, seller descriptions and product tags as a matter of course. Most of that use is legitimate and falls within platform rules. Those rules were written for product pages and conventional web addresses, and they may say nothing about onchain names.

A seller cannot create a name under .yourbrand alone, because issuance belongs to the holder of the TLD. If the TLD is held by a party other than the retailer, though, that party decides who receives names under it. A seller who obtains one can use it to appear authorized: in a seller profile, in a payment link, or in a message sent to a marketplace buyer. On the conventional web, a shopper has some familiar signals to go by, such as the address bar and the browser’s security indicator. An onchain name shown in a wallet or a message comes with no equivalent signal that an ordinary shopper would recognize.

There is a monitoring gap as well. The retailer’s fraud and brand protection teams watch for counterfeit products, unauthorized use of trademarks in titles and imitation storefronts. The tools they use are built around DNS domains and web content. An onchain name used in a marketplace message or a payment link is unlikely to appear in them. This is one of the reasons a dedicated namespace watch is worth considering for a retailer.

When the retailer runs the marketplace

Many retailers also host third-party sellers on their own sites. That reverses the position. The retailer then writes the seller rules, and can decide what its sellers may and may not present as a payment destination or as a sign of authorized status. A short clause on onchain names in the seller terms is a matter for your counsel, and it is far easier to add before a case arises than after one.

The same applies to affiliates and to franchise partners. Each of them uses the retailer’s name under a contract, and each contract either says something about names issued under a TLD that matches the brand or is silent. Silence is the usual state, simply because the question is new.

Private labels and banner names across countries

Large retailers rarely operate under a single name. A parent entity might own several trading names: the primary retail banner, one or more private-label food or clothing brands, a financial services arm with its own name, a loyalty program with its own brand, and regional variants in different countries. Each of those names is a possible TLD.

The exposure multiplies in two directions. First, any of those names may already exist as an onchain TLD. Second, the names interact. A TLD that matches a private label is associated with the retailer without carrying the retailer’s primary name, which complicates the response: the trademark may sit in a different entity, the label may be sold in some countries only, and the team that manages the label may never have been part of a domain review.

Cross-border operations add a further layer. A retailer trading under different banners in different countries has several names in several languages, and trademark rights that differ from one country to the next. A banner that is a household name in one market can be an ordinary word in another. A review therefore needs to cover each banner name and each significant private label, not only the primary brand. The Namespace Exposure Score, a free tool on this site, scores how exposed a brand is onchain, and it can be run once for each name.

Private labels raise a specific point about third-party use. Whoever holds the TLD that matches a private label could issue names under it to parties who present themselves as the manufacturer or the exclusive distributor of those products. Shoppers who know the label but not who owns it have little basis to question the apparent affiliation. Suppliers are exposed in the same way: a private label is made by contract manufacturers, and a payment request under a name that reads like the label reaches people who are used to invoicing it.

Acquired banners deserve a line of their own. A retailer that has grown by acquisition often keeps the names it bought, sometimes for years, sometimes only until a rebrand. A name that is about to be retired still has shoppers who trust it, and a name that is about to be extended to new countries has a wider audience ahead of it. Both changes are reasons to check the matching TLD before the change is public.

Seasonal peaks as the period of highest exposure

Retail exposure is not spread evenly across the year. The promotional calendar concentrates shopper attention and transaction volume in major sale periods, gift-giving seasons, back-to-school weeks and product launches. It concentrates the opportunity for misuse of a name in the same weeks.

During a peak, shoppers handle more messages, more offers and more payment requests than in a quiet period, and the scrutiny applied to any single name or link falls accordingly. A shopper who would pause over an unfamiliar name in a quiet week may not pause during a sale that ends at midnight.

The retailer’s own behavior changes too. Peaks bring campaign microsites, one-off promotional names, gift card pushes, temporary staff in stores and contact centers, and longer return windows that extend the refund season well past the sale. Each of these adds names and messages that shoppers have not seen before, which makes an unfamiliar name look normal. Temporary staff are the least likely to know which payment names the retailer uses, and the most likely to be asked by a shopper.

The organizational implication is that any monitoring, acquisition or internal guidance should be settled before a peak begins. A peak is a poor moment to learn that .yourbrand is in other hands and that names exist under it. It is an equally poor moment to open a negotiation, since a buyer who needs an answer by a fixed date negotiates from a weaker position.

The checklist below makes seasonal preparation a task of its own. The fraud team and the brand protection team can both add the status of the TLD to their pre-peak review, next to the domain and trademark monitoring that is already in place.

Exposure by function inside the organization

Different functions own different surfaces, and the exposure does not land evenly. The table below gives the main exposure for each function and says whether it is mostly reputational, financial, operational or legal.

The table is not exhaustive. A retailer with a financial services arm has an additional surface in the credit and payment products it offers under its own name. A retailer with a franchise model has a further surface in the franchise network, where a franchisee may accept a name under a TLD that neither the franchisee nor the retailer controls.

Reading the table by column is also useful. The financial rows belong to functions that already run controls and can add one more. The reputational rows belong to functions that usually have no control in place for this at all, and they are the ones most likely to hear about a case from a shopper first.

A checklist of nine checks and their owners

The checks are ordered so that the first three can start the same day with no outside help. Each one names the function that owns it.

1. Registry check across all trading namesCheck every banner name, private label and loyalty program name to see which exist as onchain TLDs. A block explorer is enough for this check, since the registry record is public. Owner: brand protection or legal.
2. Exposure score for each nameRun the Namespace Exposure Score for each name and rank the results, so that the review starts with the most exposed names. Owner: brand protection.
3. Inventory of names already issuedFor each TLD found, note which names exist under it, for example pay.yourbrand, store.yourbrand or returns.yourbrand. A TLD with names issued deserves attention before one with none. Owner: fraud and security.
4. Payment-channel reviewConfirm whether any onchain name matching the retailer's names appears in the payment environments its shoppers and suppliers use, such as wallets that resolve Freename names and payment links. Owner: fraud and security, with e-commerce.
5. Marketplace and seller reviewCheck whether third-party sellers refer to an onchain name in their profiles, offers or messages, and whether the seller, affiliate and franchise terms say anything about such names. Owner: e-commerce, with legal.
6. Customer service lineGive the contact center and store staff one sentence on which payment and refund names the retailer uses and which it does not, so that a shopper who asks gets the same answer everywhere. Owner: customer experience.
7. Pre-peak calendar alignmentPlace the review on the promotional calendar so that any monitoring, acquisition or guidance is settled well before the first major peak. Owner: brand protection, with marketing for the calendar.
8. Confidentiality scopeBefore briefing anyone beyond the core team, confirm who needs to know which names are under review, and have outside advisers sign an NDA before they receive the list. Owner: legal.
9. Options memo to senior leadershipPrepare a short memo with the options (acquire, monitor, or both), what each involves, and a recommendation with its reasons. Owner: general counsel or head of brand protection.

Options and who should own the file

Once the scoping checks are done, the organization typically faces one of three situations: the TLD does not exist yet, the TLD exists and no names have been issued under it, or the TLD exists and names are already issued.

A TLD that does not exist yet is the simplest case. The retailer can register it with the registry and hold it. It then controls issuance: no name can be created under .yourbrand without its authorization, and it can issue names for its own operations. A Freename TLD carries no annual renewal fee, which removes the recurring task that conventional domain portfolios require.

A TLD that exists with no names under it calls for a decision between monitoring and acquisition. The holder may have chosen the word for reasons unrelated to the retailer, particularly when the banner name is an ordinary word. Nothing in the registry record tells you the holder’s intentions, and it is unwise to assume them. If the retailer decides to acquire, a discreet approach is usually preferable to a public one, for the reason given in the callout above. Brand namespace recovery is the service of the desk for this case: the acquisition of the onchain TLD that matches a brand, carried out under mandate.

A TLD that exists with names already issued deserves the earliest attention. Those names may be in use in payment flows, marketplace messages or promotions. Acquiring the TLD gives control over what is issued from then on. What becomes of names issued before the transfer is a separate question. Names the seller itself holds under the TLD can be transferred with it if the parties agree, names sold to third parties remain with them, and the split should be settled before closing. Legal’s involvement is essential here. What the retailer then does with the TLD is the subject of post-transfer activation.

Monitoring alone is a legitimate choice in each case, and for a small banner or a label near the end of its life it may be the right one. It costs little and it leaves issuance in the holder’s hands. The memo should say so plainly, so that the choice to monitor is a decision and not a default.

Ownership of the file should be assigned before the review begins. A workable arrangement is for the general counsel or head of legal to hold the file, with brand protection as the operational lead and fraud and security briefed on the payment implications. The file should not sit with marketing alone, because confidentiality and the legal questions call for a function with the authority to sign an NDA and to instruct counsel.

What holding the TLD would let the retailer do

Defense is the most discussed reason for a retailer to acquire .yourbrand, but it is not the only one. Holding the TLD opens uses that are closed while the name is unregistered or in other hands.

Controlled name issuance. The retailer can issue names under its own TLD for operational purposes: pay.yourbrand as a payment identity for supplier transactions, store.yourbrand for a particular location, returns.yourbrand as a named endpoint for the refunds flow. Since issuance belongs to the holder, a shopper or supplier can be told one simple rule: a name under .yourbrand comes from the retailer.

Payment identity. A name under .yourbrand can serve as a payment destination in onchain payment flows. For the parts of a retail business that may settle onchain, such as supplier payments, marketplace commissions or franchise fees, a readable name that the retailer controls is easier to verify by eye than a wallet address, and it can be published in supplier and partner documentation.

Loyalty and rewards. Names under the retailer’s TLD could be issued to loyalty members as identities they hold in a wallet. This is a possibility and not an established retail practice. It depends on members using wallets that resolve the names, which is far from universal, and a conventional loyalty number remains simpler for most shoppers.

A namespace for AI agents. ERC-8004, titled “Trustless Agents”, is a draft Ethereum standard and may change. It sets out three registries: one for identity, where an agent is represented by an ERC-721 token that points to its agent card, one for reputation and one for validation. Names under a retailer’s own TLD could label the agents it deploys for customer service, procurement or returns. The way naming registries connect to the standard is still evolving, so treat this as a direction to follow, not a plan to budget.

Royalty participation. Freename operates a royalty program under which the holder of a TLD is paid part of each registration fee for names registered under it. Up to half is the share the registry advertises, and the figure that applies to a given banner follows the registry’s current terms and its activation conditions. Participation has a price of its own: a Freename TLD has no annual renewal fee, but the royalty program carries an annual cost that the registry sets. Certain TLDs were registered under earlier terms that include the program for life, and a retailer buying one should confirm with the registry, before closing, whether those terms pass to it. For a retailer that issues names to franchisees, authorized partners or members, the program offsets part of the cost of running the namespace. It is not a reason to acquire a TLD in itself.

None of this is needed at the assessment stage. It becomes relevant once the decision to acquire has been made, and it belongs in the options memo as a short paragraph, not as the argument.

The next step for a retail legal or fraud team

If this review is new to your organization, the most useful first action is the registry check and an exposure score across all your trading names, done by a small team. The tool is free, the registry record is public, and the result tells you whether the question deserves a place on the agenda before the next peak or can wait for the annual brand review. If a name is also a registered trademark, the page on trademark TLDs explains what a trademark TLD is and holds the free Trademark Name Check.

If a TLD matching your primary brand or a significant banner already exists, move to the options memo while the review is still confidential. Assign the owner, set the review against the promotional calendar, and let your counsel weigh the trademark position in each country where the name trades.

Hush Partners is a private desk for onchain TLDs. An organization can mandate it to find the holder of a TLD and make the approach, and closing runs through onchain escrow on an aftermarket. The fee is a fixed amount charged to the client that gives the mandate, and a party that only answers a note pays the price of the TLD and nothing more. A standard mutual NDA covers every exchange, and you can read the mutual NDA before sharing anything. The contact form on the site is the only way to reach the desk.

Questions people ask

If no names are issued under the TLD, is there still an exposure?

A TLD with no names under it is a lower priority, but not a closed question. The holder can issue names at any time, and nothing obliges a holder to give notice. Monitoring is reasonable while an acquisition is being considered. It tells you when something changes and does not prevent the change.

Does a registered trademark give the retailer the matching TLD?

A registered trademark gives documented rights in the name for the goods, services and countries it covers. It does not give automatic control of an onchain TLD that matches the mark, because onchain registries sit outside the ICANN system and its dispute procedure. The registrations remain relevant in any negotiation or dispute, and rules vary by country. Your counsel decides how the trademark position bears on an acquisition or an enforcement step.

Should a franchise network be told about the review?

Not at the scoping stage, where the smallest team is the right team. Once a decision is made, franchisees are among the first who need a clear line, since they use the name every day and are approached by suppliers and service providers under it. A short notice on which names the retailer issues is usually enough.

When is the right time to run this review?

Before a major peak, before a rebrand that changes or extends trading names, and before the public announcement of a new banner or private label. A new name attracts attention from the day it becomes public, and a check done beforehand costs less effort than a response afterwards.