.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.
No. flatbook.pay works with ordinary web hosting, redirects, or a landing-page service, just like any domain. You point its DNS wherever you want flatbook.pay to resolve. The .PAY suffix imposes no special hosting requirement.
For online checkout, brainstorm short, action-oriented .PAY labels and then verify them in the domain.pay catalog/search: https://domain.pay/domains. Good candidates are clear, memorable and tied to payment actions like checkout, billing, wallet funding, payouts or invoices.
Generally, evidence of your rights in the flatbook mark, the registrant's lack of legitimate interest, and bad-faith registration or use of flatbook.pay supports a UDRP-style claim. Trademark registrations, prior use, and proof of impersonation are commonly relevant, though outcomes vary by case. Avoiding the fight by owning flatbook.pay first is simplest. https://domain.pay/register
domain.pay lists standard .PAY pre-order service at $100 for a first-day attempt, with separate premium fees if the registry classifies the label as premium. See the current pricing here: https://domain.pay/pricing. Failed attempts are covered by the stated credit/cash-refund options.
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.