.PAY domain
Checking availability…
For digital wallets, 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.
The .PAY suffix was created specifically for payment, billing, and financial use cases, which is why partitura.pay signals money movement so clearly. Amazon Registry Services positions .PAY as a trusted namespace for transactions. That focus is built into the suffix, not just implied.
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.
Start by searching the bare partitura for partitura.pay, then layer in action words like pay, send, or get to widen results. domain.pay groups these so you can scan the variants quickly. Try different openings at https://domain.pay/domains.
.PAY labels must follow registry label rules, including 1–63 characters, letters, numbers and hyphens, no leading or trailing hyphen, and additional IDN/reserved-name rules. Test the exact label at domain.pay: https://domain.pay/register. Technical validity does not guarantee availability.
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.