Relying Party Onboarding & Launch Process
01 — Initial alignment and requirements
Before any configuration begins, you and Trinsic will align on the key details that drive the implementation path.
- Which providers are being prioritized for launch
- Whether attribute-specific verification is required
- Data minimization or scoped attribute requirements
- Expected transaction volume (initial and steady-state)
- Target timeline and launch milestones
02 — Custom domain configuration (recommended)
For production deployments, configure a custom domain to support consistent branding and improved end-user trust.
- Create the domain in the Domains tab
- Complete DNS validation
- Confirm HTTPS activation
03 — Production verification profile setup
Create a dedicated production verification profile to control branding, provider configuration, and attribute scope for this RP.
- Brand name
- Display color
- Brand logo
- Custom domain association (if applicable)
04 — Provider enablement
Within the production verification profile, select the providers requested for activation. This establishes the operational configuration for the RP's production environment.
05 — Legal and scheme-level activation
Some providers require additional steps beyond technical enablement. This is often the critical path for production launch.
- Scheme-level licensing or contractual requirements
- RP eligibility constraints (industry, geography, or wallet restrictions)
- Any direct registration processes required by the provider
06 — Testing plan
Before enabling production traffic, establish a structured testing plan.
- Environment scope (sandbox vs production)
- Availability of test credentials or testers via the Testing Network
- Validation criteria for success and failure cases
- Fallback flows (e.g. document verification where applicable)
07 — Final adjustments
Based on testing results, make any final updates before go-live.
- Provider configuration changes
- Attribute scoping adjustments
- UX refinements in selection or fallback flows
- Confirmation of production readiness across environments
08 — Production launch
Once testing is complete and activation requirements are satisfied, you're ready to go live.
- Providers enabled in the production verification profile
- DNS and branding confirmed active
- Initial traffic monitored closely
- Volume expectations and reporting cadence aligned
After launch
- Monitor success and drop-off rates
- Expand provider coverage as demand evolves
- Revisit attribute scope and data minimization over time