.PAY domain
Checking availability…
Yes. A wallet or payment app can use .PAY for a memorable payment-specific entry point. Check candidate labels through domain.pay: https://domain.pay/domains. If you own a matching trademark, consider the priority route; otherwise pre-order for broader access.
No. myschool.pay is an address, not a payment processor; it points customers to whatever gateway you use, such as Stripe or PayPal. myschool.pay handles branding and discovery while the processor handles the money. You can register myschool.pay and keep your current provider via /register.
.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.
A clear, pronounceable name like myschool.pay is easier for users to say and for assistants to capture, though voice ranking still depends on content and structured data. Make sure myschool.pay reads naturally aloud and your pages answer questions concisely. The extension itself isn't a voice-search factor.
Yes. The LRP policy says .PAY LRP names must be used in connection with payment-related services, and failure to demonstrate such use may lead to suspension or cancellation. Check the current path at 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.