.PAY domain
Already registered
Looks like a generic phrase, not a clear single trademark fit. 'Fourleaf' could map to multiple brands or concepts, so the registrant is unclear and the 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.
domain.pay states that if a registration attempt is unsuccessful, you receive 100% credit toward another domain or may request an 80% cash refund. Review the live refund wording before ordering: https://domain.pay/pricing. Premium, reserved, blocked or already-registered names can still prevent success.
A fourleaf.pay registration can be delayed if the .PAY registry requests additional validation or if the name is contested at general availability. domain.pay keeps you informed of any pending steps. To minimize delays, prepare accurate details when you start at https://domain.pay/register.
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.
If a trademark holder claims fourleaf.pay during the priority window, your general pre-order cannot succeed, and domain.pay refunds the failed attempt per its policy. You are not charged for a name you could not obtain. Refund terms are on /pricing.
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.
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.