Natural consumer finance word for stored value, cards, and app balances.
.PAY domain
coffee-shop.pay
Checking availability…
Frequently asked questions about coffee-shop.pay
Is .PAY useful for an invoice-payment portal for mobile money?
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.
Are marketplaces a fit for coffee-shop.pay?
Marketplaces can use coffee-shop.pay as the trusted settlement and payout surface buyers and sellers return to. A single payment-native address simplifies the "where does my money go" question for both sides. Explore options at https://domain.pay/domains.
Will I need accurate contact details for a .PAY registration for loan repayments?
Yes. Registry policy requires complete, accurate and current registration data. Use domain.pay for the registration path and keep your contact details up to date: https://domain.pay/register. Inaccurate data can create compliance and communication problems.
Is coffee-shop.pay useful even if I already have a payment page?
Yes. You can keep your existing payment page and point coffee-shop.pay at it as a cleaner, more shareable front door for coffee-shop. Customers get a short address while nothing about your processor changes. Add coffee-shop.pay to your stack via /register.
How can a marketplace use a .PAY domain for payroll disbursements?
A marketplace can use .PAY for seller payouts, buyer checkout, escrow, billing or payment support flows. Generate and verify names through domain.pay: https://domain.pay/domains. Choose a label that customers will recognize as official and safe.
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.