Custom domain
Use a brand-owned domain for hosted The Wallet Crew pages such as enrolment, pass download, and account-linked wallet journeys.
A custom domain aligns hosted The Wallet Crew pages with the brand identity. It also reduces phishing risk and improves trust when customers open enrolment or pass download journeys.
By default, The Wallet Crew serves hosted pages on its own domain, for example https://app.thewalletcrew.io/<tenantId>/<layout>. A custom domain replaces that public entry point with a brand-owned domain such as https://wallet.example.com. The prefix neostore is the platform's former name and is kept in technical identifiers.
Before starting
Choose the public domain that will host the journey. A dedicated subdomain is recommended: it avoids conflicts with the existing website and keeps wallet traffic isolated.
The brand also needs access to its DNS zone, and an admin console account with access to Settings. All DNS changes are made in the DNS zone.
How the setup works
Custom domains are self-service. Open Settings → General → Custom domains. The page has two tabs: Application for the hosted pages described here, and Email sender for the email sender domain (see the hint above).
Hosted pages are served through The Wallet Crew edge network. You add the domain in the admin console, the console shows the two DNS records to publish, then you check the configuration and go live. A successful check never switches customers to the domain by itself: until you click Go live, customers keep using the standard address.
Rules:
A tenant can have one custom domain.
Wildcard domains are rejected.
A root (apex) domain needs CNAME flattening, or an ALIAS or ANAME record, at the DNS provider. A dedicated subdomain avoids this.
Configure the custom domain
Add the domain in the admin console
Open Settings → General → Custom domains → Application and click Add a domain. Enter the chosen domain in Domain, then click Add domain. The console first checks that the domain can be used, then lists the two DNS records to publish.
The exact names and values are tenant-specific. Do not guess them or reuse them from another tenant or environment.
Check the configuration
Once the records are visible in DNS, click Check configuration on the same page. The console reports what is wrong when the check fails, for example a missing CNAME record or a CNAME record set to "DNS only" at the provider.
The Wallet Crew then issues the certificate, usually in under two minutes. The domain is then Ready. Testing too early can produce false negatives while DNS is still propagating.
Test, then go live
When the state is Ready, the domain already answers with a valid certificate, but customers are still sent to the standard address. Open the final URL and validate the full journey:
the page resolves on the custom domain
HTTPS is valid
the intended layout loads correctly
enrolment, sign-in, or pass download flows still work as expected
internal teams use the custom domain in campaigns, QR codes, and support scripts
Then click Go live. From then on, new emails, QR codes and enrolment links use the custom domain.
Then review the systems listed in What else must be updated.
Domain states
The admin console shows one of these states:
Waiting for DNS
The domain is added. Add the two records at your DNS provider. Nothing changes for customers until you go live.
Issuing certificate
The records work. The certificate is being issued, which usually takes under two minutes.
Ready
The domain answers with a valid certificate. Customers are still sent to the standard address until you click Go live.
Live
The domain serves your customers. The certificate renews automatically: leave the DNS records in place.
Not working
The domain could not be validated within 24 hours, or the provider refused it. Check the records, then click Check configuration again.
Removed
The domain is no longer registered with the provider. Remove it and add it again to start over.
Example DNS records
The exact values vary by tenant and environment. The example below is anonymized. The admin console is the source of truth for the records to publish.
CNAME
registration.example.com
value shown in the console, for example app.neostore.cloud
Routes customer traffic to the hosted pages
TXT
asuid.registration.example.com
<value shown in the console>
Domain ownership validation

