.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.
Payment processors are a strong fit for roman-zhyliak.pay, given the .PAY namespace's payment orientation, and the registry's validation usually aligns well with their use. Their own regulatory duties remain separate. domain.pay can help a processor secure roman-zhyliak.pay at https://domain.pay/register.
Yes. .PAY can fit invoice-payment portals because it tells customers the link is about paying. Search options such as brand-specific or invoice-related labels on domain.pay: https://domain.pay/domains. Confirm availability and premium status before adding the URL to invoices.
If roman-zhyliak has many spellings, domain.pay's search lets you test each one to find which .PAY form is available beyond roman-zhyliak.pay. Picking the simplest spelling usually aids recall. Test spellings at https://domain.pay/domains.
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.
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.