Can my merchants reach the platform on my own domain?
Each interface carries two domains, a primary and a secondary, whose labels follow the environment you run: production and sandbox in production, development and staging in development. You point the merchant interface and the admin interface at addresses you own. Your merchants sign in on your address and stay on it through every operation they perform.
In detail
Yes. You point the merchant interface and the admin interface at addresses you own, so your merchants sign in on your domain and stay on it through every operation they perform.
How domains are set up
Each interface carries two domains, a primary and a secondary. Their labels follow the environment you run: production and sandbox in production, development and staging in development. That lets your teams and your merchants test on a sandbox address while live operations run on the production one, both under your brand.
Domains are part of a wider branding layer. Themes, menus and hosted payment pages all follow your identity, and the program list shows whether the merchant domain and the admin domain are configured, as readiness indicators before go-live.
Why it matters
A custom domain is what makes the platform read as yours. Your merchants bookmark your address, receive links to your address and never land on a third-party URL. It also supports your own security practices, such as communicating one official login address to merchants to reduce phishing risk.
In a cascading structure, each program can carry its own domains. A reseller or a client program reaches its merchants on its own address, while the infrastructure underneath stays out of sight at every level.