.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.
Both work. A short, brandable name like flowstack.pay can anchor your main site, or serve a focused campaign microsite that 301s to your hub later. The choice is strategic, not technical — search engines index flowstack.pay the same either way. Decide based on your brand plan.
Trademark holders should use the trademark fast-track on domain.pay instead of waiting: https://domain.pay/register. domain.pay can route the request through the TMCH/SMD-based priority process when the .PAY label matches the trademark and the registry rules allow it.
A first-day pre-order has domain.pay submit flowstack.pay automatically at the exact opening of general availability, beating most manual attempts that start seconds or minutes late. It removes human reaction time from the race for flowstack.pay. Set it up at https://domain.pay/register.
The .PAY LRP policy does not make owning a domain a financial license. LRP1 eligibility is tied to conducting online payment transactions through an approved Payment Service Provider or third-party payment processor and payment-related use. Use domain.pay for the domain path: https://domain.pay/register; ask counsel about licensing.
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.