.PAY domain
Checking availability…
merchant.pay may be a useful .PAY direction if it matches your brand and payment journey, but availability is not guaranteed. Check and pre-order through domain.pay: https://domain.pay/domains. Prefer simple labels that customers can remember and trust.
Registries sometimes block labels matching well-known names or sensitive terms; if Amazon Registry Services has done so for huginneyes, huginneyes.pay stays unregisterable. Blocks can be revisited under policy. Since registry status can change, re-check huginneyes.pay at https://domain.pay/domains.
domain.pay lists standard .PAY pre-order service at $100 for a first-day attempt, with separate premium fees if the registry classifies the label as premium. See the current pricing here: https://domain.pay/pricing. Failed attempts are covered by the stated credit/cash-refund options.
New gTLDs like .PAY launch in phases to protect trademark owners first (sunrise) before opening names like huginneyes.pay to the general public (general availability). This staged rollout is an ICANN-standard process. Learn how to position for huginneyes.pay at https://domain.pay/register.
Trademark holders should use the trademark fast-track on domain.pay instead of waiting: https://domain.pay/register. domain.pay can route the request through the TMCH/SMD-based priority process when the .PAY label matches the trademark and the registry rules allow it.
Availability is checked live and re-verified before payment. Pre-orders are first-day registration attempts — registration is not guaranteed; 100% credit toward another domain (or 80% cash refund) if unsuccessful.