.PAY domain
Checking availability…
.PAY is sensitive because it signals money movement, so lookalike domains can confuse customers. Check your exact brand and obvious variants at domain.pay: https://domain.pay/register. Registration is one brand-protection layer, not a full anti-phishing program.
A bank is typically a strong candidate to register regularizar-cpf.pay, since regulated financial institutions align naturally with the .PAY namespace's payment focus. The registry may still validate the intended use. domain.pay can help a bank secure regularizar-cpf.pay at https://domain.pay/register.
For BNPL checkout, 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.
A pre-order queues a first-day attempt for regularizar-cpf.pay but does not guarantee acquisition, since contested names may have multiple applicants. If the attempt fails, the pre-order is refundable per policy. domain.pay explains how attempts work at https://domain.pay/pricing.
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.
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.