Relying Party Onboarding & Launch Process
A playbook for enabling a new relying party in production
1. Initial Alignment and Requirements
When an RP first requests access to a new provider, we (customer + Trinsic) will begin by aligning on key implementation details:
- Which providers are being prioritized for launch
- Whether the RP requires any attribute-specific verification
- Any data minimization or scoped attribute requirements
- Expected transaction volume (initial and steady-state)
- Target timeline and launch milestones
This ensures the correct provider configuration and activation path from the start.
2. Custom Domain Configuration (Recommended)
For production deployments, we recommend configuring a custom domain to support consistent branding and improved end-user trust.
Steps include:
- Creating the domain in the Domains tab
- Completing DNS validation
- Confirming HTTPS activation
Reference: Custom Domain Setup Documentation
3. Production Verification Profile Setup
Next, create a dedicated production verification profile to control branding, provider configuration, and attribute scope for the specific RP.
Required configuration includes:
- Brand name
- Display color
- Brand logo
- Custom domain association (if applicable)
4. Provider Enablement
Within the production verification profile, select the providers requested for activation. This step establishes the operational configuration for the RP’s production environment.
5. Legal and Scheme-Level Activation Requirements
Some providers require additional activation steps beyond technical enablement. We will review:
- Scheme-level licensing or contractual requirements
- RP eligibility constraints (industry, geography, or wallet restrictions)
- Any direct registration processes required by the provider
This step is often the critical path for production launch.
6. Testing Plan
Before enabling production traffic, a structured testing plan should be established, including:
- Environment scope (sandbox vs production)
- Availability of test credentials or testers via our Testing Network
- Validation criteria for success and failure cases
- Fallback flows (e.g., document verification where applicable)
7. Final Adjustments
Based on testing results, final updates may include:
- Provider configuration changes
- Attribute scoping adjustments
- UX refinements in selection or fallback flows
- Confirmation of production readiness across environments
8. Production Launch
Once testing is complete and activation requirements are satisfied:
- Providers are enabled in the production verification profile
- DNS and branding are confirmed active
- Initial traffic is monitored closely
- Volume expectations and reporting cadence are aligned
Post-Launch Considerations
After launch, ongoing best practices include:
- Monitoring success and drop-off rates
- Expanding provider coverage as demand evolves
- Revisiting attribute scope and data minimization over time
Updated 3 days ago