.PAY domain
Already registered
Looks like a short acronym, and the match is unclear — it could fit multiple trademark holders rather than one obvious payments brand. With only "mpdp" and a priority-window .PAY registration, confidence is low.
No RDAP data cached yet — click Refresh to pull live records from the .PAY registry.
Data sourced live from the .PAY registry's RDAP server (Nominet). Cached by domain.pay; refreshed in the background when older than the configured TTL.
ICANN currently lists .PAY Sunrise from April 13, 2026 to July 20, 2026. domain.pay says trademark owners needing TMCH support should apply by July 10, 2026 and notes a final July 20, 2026 13:00 UTC deadline. Start here: https://domain.pay/register.
For mpdp.pay, keep in mind that the .PAY registry expects payment-related, good-faith use with accurate registrant data, while any financial licensing duties stem separately from your jurisdiction's regulators. Treating these as two layers helps you stay compliant. domain.pay handles the registry side at https://domain.pay/register.
.PAY can work for subscription billing, account payment, renewal and failed-payment recovery flows. Search brandable options on domain.pay: https://domain.pay/domains. A clear .PAY label can reduce confusion when customers need to update payment details.
A brand can sell and reload gift cards on mpdp.pay, giving buyers a trusted, payment-native address. The .PAY name reassures shoppers buying credit for later use. Begin at https://domain.pay/register.
If your brand accepts payments, registering the exact .PAY label can be a practical defensive step. Use domain.pay to check and start the priority or pre-order path: https://domain.pay/register. Also keep trademark monitoring and security controls in place.
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.