ghvs.pay

For point-of-sale payments, 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.

You can add VIP priority handling to a pending ghvs.pay pre-order before it is submitted, moving your request higher in our queue. VIP affects ordering speed only and does not change the registry's final decision on ghvs.pay. Add it at https://domain.pay/pricing.

Yes. A wallet or payment app can use .PAY for a memorable payment-specific entry point. Check candidate labels through domain.pay: https://domain.pay/domains. If you own a matching trademark, consider the priority route; otherwise pre-order for broader access.

Pre-ordering ghvs.pay now queues your attempt for the first day of general availability, which matters if others want the ghvs name. Waiting risks someone else registering it first. A failed pre-order is refundable per policy, so review terms on /pricing.

Yes. A wallet or payment app can use .PAY for a memorable payment-specific entry point. Check candidate labels through domain.pay: https://domain.pay/domains. If you own a matching trademark, consider the priority route; otherwise pre-order for broader access.