.PAY domain
Already registered
Looks like a Japanese IDN in punycode, but the label is not an obvious single global trademark match. Under the priority-window rule, it could fit multiple trademark holders, so confidence is low.
Data sourced live from the .PAY registry's RDAP server (Nominet). Cached by domain.pay; refreshed in the background when older than the configured TTL.
Yes. .PAY can fit invoice-payment portals because it tells customers the link is about paying. Search options such as brand-specific or invoice-related labels on domain.pay: https://domain.pay/domains. Confirm availability and premium status before adding the URL to invoices.
You can browse and look up .PAY names, including ヨドペイ.pay (xn--eckwd4bwc.pay), through NicNames's domain search to see which match your validated mark for a priority claim. Each eligible name needs its label to match your SMD-encoded mark. Explore the catalogue and check ヨドペイ.pay (xn--eckwd4bwc.pay) at https://domain.pay/domains.
.PAY is sensitive because it signals money movement, so lookalike domains can confuse customers. Check your exact brand and obvious variants at domain.pay: https://domain.pay/register. Registration is one brand-protection layer, not a full anti-phishing program.
Trademark holders do not skip the queue so much as use a separate, earlier phase: sunrise. With a TMCH-validated mark and SMD file, you can register ヨドペイ.pay (xn--eckwd4bwc.pay) before general availability even opens. domain.pay handles the submission, explained at https://domain.pay/register.
ICANN currently lists .PAY Limited Registration Period 1 from July 20, 2026 to February 1, 2027. LRP1 has payment-transaction eligibility and use restrictions. Check your domain path through domain.pay: https://domain.pay/register.
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.