Amazon has launched .PAY — a new generic top-level domain that sits at the most sensitive intersection in the internet economy: payments, trust, and brand identity. Here is everything businesses, brand owners, and domain professionals need to know about one of the most consequential new extensions to enter the domain name system.

What is .PAY and Who Controls it?

The .PAY top-level domain is a new generic top-level domain (gTLD) operated by Amazon EU S.à r.l. — the Luxembourg-based legal entity through which Amazon manages its European operations and, in this context, its registry operations under ICANN’s New gTLD Program. The Registry Agreement between ICANN and Amazon EU S.à r.l. for the .PAY TLD was signed on 27 August 2015, making .PAY one of the last unlaunched domains from the landmark 2012 ICANN New gTLD application round — a programme that received nearly 2,000 applications for new domain extensions from organisations around the world.

The full text of the ICANN Registry Agreement for .PAY is publicly available on ICANN’s website, as is the registry agreement details page for .PAY on ICANN.org. Under the terms of that agreement, Amazon EU S.à r.l. is designated as the registry operator for the TLD for an initial term of ten years, renewable automatically in ten-year increments.

Amazon Registry Services operates a significant portfolio of new gTLDs secured through the 2012 application round. Previous Amazon-operated launches have included extensions such as .BOT, .DEAL, .FREE, .FAST, .TALK, and .YOU. .PAY represents a departure from Amazon’s earlier, more generic extensions — it is arguably the most commercially and financially sensitive TLD Amazon has yet launched, positioned directly within the global payments ecosystem.

Key Facts at a Glance

TLD.PAY
Registry OperatorAmazon EU S.à r.l.
ICANN Registry Agreement Signed27 August 2015
Sunrise Period13 April 2026 – 13 May 2026
Sunrise TypeStart Date Sunrise (first-come, first-served)
TMCH RequirementYes — .smd file required for Sunrise eligibility
Limited Registration Period (LRP)Post-Sunrise through 1 February 2027
General AvailabilityExpected early 2027 (dates not yet announced)
Included in GlobalBlockNo
IDN SupportYes — 16 languages including Chinese, Japanese, Korean, Arabic scripts
ICANN Agreement Referenceicann.org/en/registry-agreements/details/pay

Why .PAY is Unlike Any Other Amazon gTLD Launch

Every new gTLD launch carries some brand protection implications. But .PAY is different in kind, not just degree. The word “pay” is not a generic descriptor of a hobby, a lifestyle, or a geography — it sits at the absolute core of commercial trust on the internet. Consider what a domain like brand.pay inherently communicates to any consumer who sees it: this is a payment portal for that brand.

This is not a theoretical risk. In the current internet landscape, phishing attacks — fraudulent websites designed to impersonate legitimate brands and capture payment credentials, banking details, or personal data — are one of the most prevalent and damaging forms of cybercrime globally. A domain ending in .PAY, by its very construction, signals financial activity. A bad actor registering yourbank.pay, yourshop.pay, or amazon.pay (to take an obvious example) would have a structurally persuasive tool for phishing attacks that a comparable .COM or .NET domain would lack.

This sensitivity was not lost on Amazon. Unlike most of its previous gTLD launches — which followed a standard Sunrise Period and then opened to general availability — Amazon structured .PAY’s post-Sunrise phase as a Limited Registration Period (LRP) rather than a traditional Landrush, with explicit eligibility and use restrictions that apply to all registrations made after Sunrise. As noted by critics online, the combination of .PAY’s inherent payment connotation and its exclusion from GlobalBlock makes it one of the highest-priority defensive registration opportunities brand owners have faced in recent years.

The .PAY Launch Timeline: Phase by Phase

Phase 1 — Sunrise Period: 13 April – 13 May 2026

The Sunrise Period is the first registration phase for any new gTLD and is reserved exclusively for trademark holders who have previously registered their marks with the ICANN Trademark Clearinghouse (TMCH). The Sunrise Period for .PAY ran from 13 April to 13 May 2026 — a 30-day window. The .PAY Sunrise followed a “Start Date” model, meaning domain names were allocated on a strict first-come, first-served basis from the moment the Sunrise opened. There was no priority queue or random draw — speed of application mattered.

To register during Sunrise, applicants were required to:

  1. Have their trademark previously registered with the ICANN Trademark Clearinghouse
  2. Obtain the resulting .smd file (Signed Mark Data) from the TMCH — a digitally signed certificate that proves trademark eligibility
  3. Submit the registration through an accredited registrar along with the .smd file to verify eligibility
  4. Register a domain name that exactly matches the trademark text as recorded in the TMCH

Sunrise registration policies for .PAY did not include restrictions on the types of entities that could register, nor did they impose requirements on what use must be made of the registered domain name — meaning trademark holders could register defensively without any obligation to actively use the domain. This is an important distinction from the more restrictive rules that apply in the subsequent Limited Registration Period.

Phase 2 — Limited Registration Period (LRP): Post-Sunrise through 1 February 2027

Rather than following Sunrise with a traditional Landrush — where any registrant can register on a first-come, first-served basis at elevated prices — Amazon chose a Limited Registration Period (LRP) for .PAY. This is a more controlled approach that reflects the sensitivity of the extension. The LRP runs from the close of Sunrise through 1 February 2027.

The LRP imposes two significant and explicit restrictions that do not apply to Sunrise registrations:

  • Eligibility Restriction: Only registrants that “conduct payment transactions online using an approved Payment Service Provider or Third-Party Payment Processor” are eligible to register during the LRP. This is a meaningful bar — registrants must be active participants in the online payments ecosystem, not general internet users or domain investors seeking generic registrations.
  • Use Restriction: Registrants agree to use their .PAY domain name “in connection with payment-related services, including but not limited to processing payments, facilitating e-commerce transactions, or providing payment gateway services.” Dormant or parked registrations would be in breach of this use requirement.

Verification of these restrictions will not be conducted on an a priori basis — there is no upfront eligibility check before registration is granted. Instead, Amazon has indicated it will conduct spot checks and attend to reports of non-compliance. As noted by several IP Lawyers, this approach has a practical advantage from a brand protection enforcement perspective: demonstrating non-compliance with a registry policy is generally simpler than meeting the evidentiary standard required for a UDRP complaint or DNS abuse report.

Phase 3 — General Availability: Expected Early 2027

No specific dates have been announced for when .PAY will enter General Availability — the phase at which any eligible registrant can register a domain name on an open, first-come, first-served basis. Based on the LRP end date of 1 February 2027, General Availability is expected to commence in early 2027. It has also not yet been communicated whether the eligibility and use restrictions in place during the LRP will carry over into General Availability — a question of significant importance for brand owners who did not register during Sunrise or the LRP.

The GlobalBlock Gap: Why .PAY Demands Individual Attention

For brand owners who subscribe to GlobalBlock — an industry service that allows a brand name to be blocked from registration across participating gTLD registries simultaneously — the .PAY launch creates an immediate gap. As with several other recent Amazon gTLD launches, .PAY is not included in GlobalBlock.

This means that GlobalBlock subscribers cannot rely on their existing subscription to protect their brand name under .PAY. Defensive registrations must be pursued individually and directly — either during Sunrise (for trademark holders with TMCH registrations) or during the LRP (for qualifying payment industry participants). Brand owners who failed to register during Sunrise and do not meet the LRP eligibility criteria face a gap in their defensive domain portfolio that cannot be papered over by a blanket blocking service.

  1. The inherent risk of a bad actor holding a brand.pay domain, even briefly — the payment connotation makes such a registration inherently deceptive and dangerous
  2. The exclusion from GlobalBlock, requiring brand-by-brand defensive registration decisions
  3. The possibility that registrations made after Sunrise are subject to the LRP’s use requirement — meaning a domain registered purely defensively (without active payment-related use) could be in breach of registry policy and potentially subject to compliance action, removing the option to leave the domain dormant indefinitely

The ICANN Registry Agreement: What Amazon Committed To

The legal foundation of .PAY’s operation is the Registry Agreement between ICANN and Amazon EU S.à r.l., signed on 27 August 2015 and publicly available on ICANN’s document repository. This agreement is a standard new gTLD Registry Agreement — the same template used across the majority of the 2012 application round — with Amazon-specific provisions in the Exhibit A Approved Services section.

Key provisions of the Registry Agreement relevant to registrants and brand owners include:

  • Term: Ten years from the Effective Date, renewable automatically in successive ten-year periods unless terminated for cause
  • Registry Fees to ICANN: A fixed quarterly fee of USD $6,250 plus a per-transaction fee of USD $0.25 per registration (applicable once the Transaction Threshold of 50,000 annual transactions is exceeded)
  • Pricing Rules: Amazon must provide 30 days’ notice of price increases for new registrations and 180 days’ notice for renewal price increases — protecting registrants from sudden pricing changes
  • Rights Protection Mechanisms: Amazon is required to implement standard ICANN Rights Protection Mechanisms (RPMs) including the Trademark Clearinghouse Sunrise and Claims procedures, with pass-through fees of up to USD $0.25 per Sunrise and Claims registration
  • Reserved Names: Amazon must comply with ICANN’s Specification 5 on reserved names, including reservations for geographic, governmental, and technical purposes
  • IDN Support: The agreement explicitly approves IDN registrations in 16 languages including Chinese, Danish, Finnish, German, Hungarian, Icelandic, Japanese, Korean, Latvian, Lithuanian, Norwegian, Polish, Portuguese, Russian, Spanish, and Swedish — making .PAY a genuinely multilingual extension
  • Compliance Audits: ICANN may conduct up to two compliance audits per calendar year at its own expense (with costs shifting to Amazon under certain circumstances involving affiliated registrar relationships)
  • Emergency Operations: Amazon must maintain a Continued Operations Instrument (a financial guarantee) to ensure the registry can continue operating even in the event of Amazon’s business disruption — protecting registered domain holders

Amazon’s gTLD Empire: Context for .PAY

Amazon’s involvement in the new gTLD programme is one of the less-discussed dimensions of the company’s extraordinary breadth. Amazon applied for a large number of new gTLDs in the 2012 application round — part of a broader strategy among large technology companies to secure control over domain extensions that could eventually become part of their product and brand ecosystems.

Amazon operates gTLDs across several categories:

  • Brand extensions — .AMAZON, .AWS, .ALEXA (Amazon’s own brand namespace)
  • Commerce extensions — .BUY, .DEAL, .DISCOUNT, .COUPON, .SALE, .SHOPPING, .STORE
  • Technology extensions — .BOT, .CLOUD, .GAME, .SEARCH
  • Communications extensions — .TALK, .CALL, .CHAT, .CONTACT, .EMAIL
  • Financial extensions — .PAY, .CASH, .GIVE
  • Lifestyle extensions — .FREE, .FAST, .FRESH, .FUN, .NOW, .YOU

Many of Amazon’s gTLDs operate as closed registries — extensions reserved exclusively for Amazon’s internal use and not open for public registration. Others, like .PAY, are launched as open or semi-open registries where third parties can register domain names, subject to the applicable launch and registration policies. The decision to open .PAY to external registrations — rather than operate it as a closed registry for Amazon Pay exclusively — is a significant strategic choice that reflects Amazon’s broader registry operator role and its obligations under the ICANN Registry Agreement.

What .PAY Means for the Payments Industry

The payments industry globally is undergoing its most rapid transformation in decades. Digital wallets, buy-now-pay-later services, real-time payment rails, open banking APIs, cryptocurrency payment gateways, and embedded finance are reshaping how consumers and businesses transact. In this context, the launch of .PAY creates a new and highly relevant namespace for:

  • Payment processors and gateways — Stripe, PayPal, Adyen, Razorpay, PayU, and similar companies for whom a .PAY domain is a natural brand extension
  • Banks and financial institutions — for dedicated payment portals, transaction-facing products, and digital banking services
  • E-commerce platforms — checkout and payment subdomains that would benefit from the trust signal of a .PAY address
  • Fintech startups — for whom a premium .PAY domain communicates legitimacy and sector focus from day one
  • Cryptocurrency and DeFi platforms — payment-related services in the digital asset space where establishing trust is particularly important
  • Corporate treasury and B2B payments — enterprise payment portals that benefit from the authority of a dedicated payment namespace

For Indian businesses specifically, the timing of .PAY’s launch is particularly relevant. India’s Unified Payments Interface (UPI) has processed over 100 billion transactions annually and is being expanded internationally. Indian fintech companies — PhonePe, Paytm, Razorpay, BharatPe, and others — are building global payment platforms and may find .PAY domain registrations strategically valuable for their international expansion.

Brand Protection Implications: A Strategic Framework

For brand owners — whether in financial services, e-commerce, or any sector that involves online payments — the launch of .PAY presents a set of strategic decisions that fall into three categories:

1. Assess Your Risk Exposure

Does your brand’s name, when combined with .PAY, create a plausible payment portal? If the answer is yes — and for most consumer-facing brands it will be — then the risk of a third party registering example.pay and operating a phishing or fraud site is real and non-trivial.

2. Understand the Trademark Clearinghouse Requirement

Sunrise registration — the only phase with no use restrictions — required prior registration with the ICANN Trademark Clearinghouse. If your trademark was already registered with the TMCH, you had an opportunity to participate in Sunrise (which closed on 13 May 2026). If you missed Sunrise, the LRP is your next opportunity — subject to the eligibility and use requirements described above. For future gTLD launches, registering with the TMCH is a one-time investment that unlocks Sunrise access for every participating new gTLD for the duration of your TMCH registration — a significant brand protection efficiency.

3. Monitor the General Availability Timeline

If you do not qualify for the LRP (because you do not conduct payment transactions online) or if you were unable to register during Sunrise, monitoring the General Availability launch — expected in early 2027 — is essential. If the LRP’s restrictions do not carry over into General Availability, the .PAY namespace could open to unrestricted registration at that point, creating an immediate first-come, first-served rush for brand-matching domains. Brands should prepare accordingly, including identifying the registrar through which they will act and the specific domain names they intend to register.

What is the Trademark Clearinghouse (TMCH)?

For readers unfamiliar with the TMCH, a brief explanation is warranted given its central role in the .PAY launch and in all new gTLD Sunrise periods.

The ICANN Trademark Clearinghouse is a central database established by ICANN to support the rights of trademark holders during the launch of new gTLDs. It provides two core functions:

  1. Sunrise Eligibility: Trademark holders who register with the TMCH receive a Signed Mark Data (.smd) file — a digitally signed certificate — that they can use to prove eligibility for Sunrise registration across all participating new gTLDs. A single TMCH registration covers Sunrise access for all new gTLDs that implement standard ICANN RPMs.
  2. Trademark Claims Notifications: During the Claims Period (a mandatory post-Sunrise phase), the TMCH notifies trademark holders when someone attempts to register a domain matching their mark, and notifies potential registrants that the string they are attempting to register matches a TMCH-registered trademark. This creates a disclosure mechanism that reduces inadvertent infringement.

TMCH registration is available to holders of nationally or regionally registered trademarks, as well as court-validated marks and marks protected by statute or treaty. Registrations are verified and validated by TMCH agents before marks are entered into the database. The TMCH is operated by Deloitte and KPMG under contract with ICANN.

The Bigger Picture: Amazon’s Role in the New gTLD Ecosystem

The launch of .PAY is a small but meaningful data point in a much larger story: the role of major technology corporations as gTLD registry operators. Amazon, Google (through Google Registry, which operates .APP, .DEV, .PAGE, and others), and other tech giants have used the 2012 gTLD programme to secure control over domain extensions that complement their product portfolios and brand ecosystems.

From a domain investment and brand strategy perspective, this trend has several important implications:

  • Corporate gTLDs are not neutral infrastructure. When Amazon operates .PAY, it is simultaneously the registry operator (setting the rules), a potential registrant (Amazon Pay could operate on .PAY domains), and an indirect commercial beneficiary of the extension’s growth. This vertical integration raises ongoing questions about competitive neutrality that ICANN’s Registry Code of Conduct (Specification 9 of the Registry Agreement) is designed to address — but which remain a subject of industry debate.
  • Amazon’s unlaunched portfolio represents future market events. With a significant number of gTLDs still unlaunched from the 2012 round, Amazon’s registry pipeline continues to generate new launch events. Each new launch follows broadly similar procedures but with extension-specific policies that require independent analysis. Domain professionals should maintain awareness of Amazon’s upcoming launches as part of their market monitoring.
  • The 2026 New gTLD Round will bring more corporate applicants. With the new gTLD application window open as of 30 April 2026, large corporations — including Amazon, Google, and many others — are likely to file additional applications. The .PAY experience provides a useful template for how corporate registry operators may structure sensitive extensions with restricted registration phases rather than open general availability.

Practical Guidance for Different Stakeholders

For Indian Fintech and Payment Companies

India’s fintech sector is one of the world’s most dynamic — home to some of the largest digital payment volumes globally. Companies operating payment gateways, digital wallets, lending platforms, and UPI-based services should evaluate .PAY domain registrations as both defensive brand protection and potentially as a primary or product-specific domain identity. During the LRP, the eligibility requirement (conducting payment transactions online) is almost certainly met by Indian payment companies. Act before 1 February 2027.

For Brand Owners in Any Sector With an E-Commerce Presence

If your brand sells products or services online and processes payments — even through a third-party checkout — a bad actor registering yourbrand.pay is a phishing risk you should not ignore. The Sunrise period has closed, but the LRP remains open through 1 February 2027 for qualifying registrants. Consult with your domain strategy provider or IP counsel about eligibility and registration options.

For Domain Investors

The LRP’s eligibility and use restrictions significantly limit the domain investment opportunity in .PAY during the current phase — dormant or parked registrations would be in breach of the use requirement. However, once General Availability opens (expected early 2027), it remains to be confirmed whether these restrictions will carry over. Domain investors should monitor the General Availability announcement closely and be prepared to act quickly if registrations open on an unrestricted basis. Generic payment vocabulary — words like “fast,” “instant,” “secure,” “global,” and similar — may attract premium values in an unrestricted .PAY General Availability if it occurs.

For IP and Legal Professionals

The .PAY launch demonstrates how new gTLD registry policies — particularly LRP eligibility and use requirements — are creating novel enforcement mechanisms that sit outside the traditional UDRP framework. A registrant who violates LRP use requirements may be subject to registry compliance action that is faster and procedurally simpler than a UDRP complaint. IP practitioners advising clients on domain strategy should be conversant with these registry-level enforcement tools as a complement to UDRP and court-based remedies.

Conclusion: .PAY is a Signal, Not Just a TLD

The launch of .PAY by Amazon Registry Services is more than the addition of another new extension to an already vast domain landscape. It is a signal — about where the domain industry is heading, about the growing commercial sensitivity of certain gTLD namespaces, and about the increasingly sophisticated ways in which registry operators are managing launch phases to balance openness with brand protection.

The decision to structure post-Sunrise access as a Limited Registration Period — with eligibility requirements tied to actual participation in the payments ecosystem and use requirements that mandate active payment-related deployment — is a departure from the generic “open to all, first-come first-served” approach that characterised many early gTLD launches. It reflects a growing maturity in the industry’s approach to sensitive extensions, and it creates a model that other registry operators may follow for future high-sensitivity TLDs.

For domain professionals in India and across Asia, the .PAY launch is a case study in how new gTLDs should be assessed: not merely as registration opportunities, but as brand protection events with phased access controls, eligibility requirements, and compliance frameworks that require careful evaluation rather than a one-size-fits-all approach.

At DOMAINX™, we will continue tracking the .PAY rollout — including the General Availability announcement and any developments regarding the carryover of LRP restrictions — and bringing the Indian domain community the intelligence it needs to stay ahead of every significant development in the global domain namespace.

Sources and References

ICANN Registry Agreement Details — .PAY: icann.org/en/registry-agreements/details/pay

Full .PAY Registry Agreement (ICANN / Amazon EU S.à r.l., 27 August 2015): itp.cdn.icann.org/en/files/registry-agreements/pay/pay-agmt-html-27aug15-en.htm

ICANN New gTLD Programme — .PAY Sunrise and Claims Period Status: newgtlds.icann.org/en/program-status/sunrise-claims-periods/pay

This article is published by DOMAINX™ for informational and educational purposes. The .PAY Sunrise Period closed on 13 May 2026. Brand owners and businesses are advised to consult qualified domain strategy counsel or IP professionals regarding their options during the limited registration period and ahead of General Availability. DOMAINX™ has no commercial relationship with Amazon, ICANN, or any other party mentioned in this article.