← All .PAY names

.PAY domain

brows.pay

Checking availability…

Checking this name against the .PAY registry — one moment…

Frequently asked questions about brows.pay

Where can I generate .PAY ideas for crypto payments?

For crypto payments, 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.

Are there refunds if brows.pay is withheld by the registry?

If Amazon Registry Services reserves or withholds brows.pay, your pre-order cannot be fulfilled and the attempt is refundable under our stated policy. Reserved names are outside our control. Read how withheld names are handled for brows.pay at https://domain.pay/pricing.

Could I use .PAY for a wallet or payment app for online checkout?

Yes. A wallet or payment app can use .PAY for a memorable payment-specific entry point. Check candidate labels through domain.pay: https://domain.pay/domains. If you own a matching trademark, consider the priority route; otherwise pre-order for broader access.

Should every page on brows.pay be served over HTTPS?

Yes. Serve all of brows.pay over HTTPS and redirect any HTTP request, since mixed or plain-HTTP pages trigger browser warnings and can hurt trust. Modern SEO and security baselines expect brows.pay to be fully encrypted. Add HSTS once brows.pay is reliably HTTPS-only.

Can I browse alternative .PAY names if my first choice is taken when choosing travel.pay?

Use domain.pay to search the live label and review already-registered .PAY examples: https://domain.pay/domains. If your first choice is already registered or not available, domain.pay can help you browse alternatives or pre-order a different name.

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.