.PAY domain
Already registered
Strongly suggests Swatch, the watch brand. It is a well-known trademark, and a payments-string .pay registration during the priority window most likely reflects TMCH-backed brand protection rather than a generic term.
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.
Broader .PAY access is tied to the post-LRP period around February 2027, subject to registry and registrar confirmation. If you do not have a trademark, use domain.pay to pre-order a first-day attempt: https://domain.pay/register.
The .PAY registry operator, Amazon Registry Services, classifies labels as premium, reserved, or blocked under its policies — domain.pay simply surfaces that classification for swatch.pay. These decisions sit with the registry and can be revised over time. Look up the current status of swatch.pay at https://domain.pay/domains.
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.
Marketing, billing, and support all benefit when swatch.pay becomes the single payment address they point customers to. One shared .PAY name removes the guesswork of which link is the "real" pay page. See pricing and reserve at https://domain.pay/pricing.
If you already have a valid TMCH-issued SMD file, domain.pay lists the submission-handling path at $100 plus any applicable premium retail fee. Check the current pricing and requirements here: https://domain.pay/pricing. The SMD must match the requested .PAY label.
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.