.PAY domain
Already registered
Best guess: Sodexo, the global food-services and employee benefits brand. The label exactly matches the company name, and a .pay registration fits a payments/benefits use case tied to its prepaid and employee benefit services.
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.
A .PAY name registered during an LRP may be transferred only to a new registrant that fulfills the same LRP eligibility criteria. For registration or pre-order assistance, start at domain.pay: https://domain.pay/register. Do not buy or sell LRP names without confirming eligibility.
A generic domain says nothing about what happens there, but sodexo.pay states payment in the suffix itself. Visitors reading sodexo.pay expect to pay sodexo, which sets the right context immediately. That built-in meaning is the core advantage of .PAY.
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.
For any campaign that ends in a purchase or donation, sodexo.pay gives you a campaign URL that already implies the payment step. That clarity can reduce hesitation between the click and the conversion. You can secure the name 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.
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.