.PAY domain
Checking availability…
If your brand accepts payments, registering the exact .PAY label can be a practical defensive step. Use domain.pay to check and start the priority or pre-order path: https://domain.pay/register. Also keep trademark monitoring and security controls in place.
Identity or registrant verification can be part of acquiring foundation-system.pay where the .PAY registry's validation calls for it. Requirements may vary by intended use and over time. domain.pay relays any verification steps so you can respond quickly; start at https://domain.pay/register.
The .PAY LRP policy does not make owning a domain a financial license. LRP1 eligibility is tied to conducting online payment transactions through an approved Payment Service Provider or third-party payment processor and payment-related use. Use domain.pay for the domain path: https://domain.pay/register; ask counsel about licensing.
Yes, foundation-system.pay resolves through the standard DNS just like any .com or .org address. You can point foundation-system.pay at a website, a payment processor, or a redirect, and browsers treat it normally. The only difference is the payments-focused .PAY suffix.
Start at domain.pay, search the label, then choose the right path: trademark fast-track if you qualify, or pre-order for a first-day attempt when broader access opens. Use this page: https://domain.pay/register. Registration is subject to registry rules and availability.
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.