Setting up a Custom Domain

Introduction

By default, verifications through Trinsic use a Trinsic-owned domain name (verify.trinsic.id), which is shown in a user's browser bar under certain conditions - such as when redirecting to/from a Provider, or when interacting with a Trinsic-hosted interface.

Custom domains allow you to replace Trinsic’s default domain with your own custom domain (e.g. eids.yourcompany.com). This gives your users a fully branded, native experience and enhances brand trust while still leveraging Trinsic’s powerful identity infrastructure. If you are an intermediary, you can register both your own and your customer's domains.

Trinsic presently supports custom domains by applying a CNAME to Trinsic's white-label endpoint, and generating an SSL certificate in the process. Please reach out if you'd like to bring your own certificate or would like to implement a Reverse Proxy setup instead.

Setup

Create the domain in the Trinsic Dashboard

In the Trinsic Dashboard, add your domain - it will be added with a status of Requested. Custom domains are not available in Test mode at this time.

The Trinsic team will be notified of this and will ensure all required details are setup correctly. Once confirmed, your domain will be marked with a status of Connected and our team will communicate to you it's ready to be used.

Adjust your DNS records

The Trinsic team will send you a few DNS records to add to your domain:

A CNAME that points from your desired domain (eg eids.yourcompany.com) to white-label.trinsic.id.
A TXT record to validate domain ownership for our proxy.
A TXT record to validate domain ownership for SSL certificate generation.

Once they are in place, please let us know so we can initiate the verification process.

📘
Domains must be validated within 7 days. After this time, the domain validation will need to be started again from scratch. Please align with your internal team that manages your DNS to ensure this process can be completed within 7 days.

Start using the domain

Configure Verification Profiles

❗️
Custom domains require activation for most providers
Custom domains require unique provider activations. Once a Verification Profile has been configured with a custom domain, it will likely break most active providers on that profile until the Trinsic team has performed the necessary configuration steps with each provider.
We recommend setting up a new profile with the domain, rather than adjusting a profile you're already using for live verifications.

You can now go into the dashboard and apply the domain to the specific profile you'd like to use the domain for.

Frontend SDK

If you are using Trinsic's Web UI SDK to launch verifications via a popup, you may want to specify the initialUrl and initialWindowTitle parameters when calling createPopup() or createPopupAndWaitForResults().

Due to browser restrictions regarding popups, the Web UI SDK opens a popup to a predetermined loading page before you call your backend to create a Session; finally, the SDK redirects the popup to the Session's launch URL. In the time between the popup being opened and being redirected, it displays a loading page which is hosted on Trinsic's domain name. The initialUrl and initialWindowTitle parameters allow you to change this behavior.

const popup = trinsicUi.createPopup({
  initialUrl: `https://${window.location.hostname}/loading`,
  initialWindowTitle: "Your Company Verification",
});

Backend SDK

There are no adjustments required to make custom domains work with Trinsic's backend SDKs.

Test

Once Trinsic confirms your domain and changes the status to Connected, launch a flow using one of Trinsic's built-in test providers. These support custom domains automatically.