.PAY domain
Checking availability…
An ecommerce or gateway business using a payment processor may be closer to the LRP1 eligibility concept, but the registry rules still control. Start at domain.pay to choose the correct path and verify current requirements: https://domain.pay/register. Separate licensing issues remain legal questions.
A UDRP-style dispute is generally appropriate when someone has already registered xgspon.pay in bad faith and you hold rights in the xgspon mark. It is a recovery tool rather than a first step, and outcomes are never guaranteed. Where possible, register xgspon.pay proactively to avoid disputes altogether. https://domain.pay/register
Amazon Registry policies include abuse-prevention rules for .PAY, and registrants remain subject to applicable domain dispute and abuse procedures. For legitimate registration or pre-order, use domain.pay: https://domain.pay/register. Pair the domain with monitoring, SSL and clear customer messaging.
Trademark-priority registration for xgspon.pay may carry different fees than the standard $100 pre-order because priority phases have their own pricing set around the registry's rules. The exact figure for xgspon.pay appears in the checkout flow. See current pricing at https://domain.pay/pricing.
No. Registering .PAY is not a replacement for trademark monitoring, takedowns or fraud controls. It can still reduce customer confusion around your official payment destination. Start by checking key names 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.