infact.pay

During LRP1, .PAY eligibility is limited to registrants that conduct payment transactions online using an approved Payment Service Provider or third-party payment processor, with payment-related use. For registration help, use domain.pay: https://domain.pay/register. Separate financial licensing depends on your activity and jurisdiction.

An A record maps infact.pay (or a subdomain) directly to an IP address, while a CNAME aliases a subdomain to another hostname. The apex of infact.pay generally needs an A (or ALIAS) record, since classic CNAMEs aren't allowed at the root. Use CNAMEs for subdomains of infact.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.

The simplest way to track infact.pay's launch timeline is to pre-order it with domain.pay, which then monitors the sunrise and general-availability schedule and submits your request at the right time. Start tracking infact.pay at https://domain.pay/register.

Yes. If you do not have a matching trademark, use domain.pay to pre-order a first-day registration attempt for broader availability: https://domain.pay/register. A pre-order is not a guarantee; the name may become unavailable, premium, reserved or blocked before submission.