.PAY domain
Checking availability…
merchant.pay may be a useful .PAY direction if it matches your brand and payment journey, but availability is not guaranteed. Check and pre-order through domain.pay: https://domain.pay/domains. Prefer simple labels that customers can remember and trust.
Businesses involved in payments, fintech, checkout, billing, or financial services are typically a natural fit for x-line.pay, given the .PAY namespace's orientation. The registry may still validate the specific intended use. domain.pay can assess your fit and register x-line.pay at https://domain.pay/register.
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.
Whether NicNames fits better than x-line.pay depends on how cleanly each captures x-line and reads as a payment name. domain.pay lets you place NicNames and x-line.pay side by side to judge clarity and recall. Compare them at https://domain.pay/domains.
Use domain.pay to search the live label and review already-registered .PAY examples: https://domain.pay/domains. If your first choice is already registered or not available, domain.pay can help you browse alternatives or pre-order a different name.
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.