Provider Testing

Once your integration is complete and providers have been enabled, the next step is testing. Because every digital ID scheme works differently, how you test depends on the provider. This guide covers the three main approaches.

01 — Use test credentials

The fastest path: if a provider offers official test credentials, start here. Supports repeatable, automated QA flows without needing real IDs.

02 — Test with internal employees

Many providers don't offer test data. In these cases, testing requires a real credential from someone in the correct geography. Use this when you have internal access to the required wallet or ID.

• A team member in Sweden testing BankID
• An employee in Louisiana testing LA Wallet

03 — Use Trinsic's Testing Network

No test credentials and no internal tester? Use Trinsic's Testing Program to request a tester in the right region. Trinsic will coordinate the test and can provide a recording if helpful.

To submit a request, provide:

1. A session URL that is long-lived (at least two days)
2. The provider you want tested
3. Any instructions for the flow (success and failure scenarios)

What to validate

Regardless of testing method, confirm the following before going live:

• A successful verification completes as expected
• Failure and "not found" cases behave correctly
• Sessions time out or cancel cleanly
• Redirects return the user to your application
• Fallback flows (e.g. document verification) work if applicable

Before production launch

• Which environment you're testing in (sandbox vs production)
• Whether test credentials or testers are available
• Clear success and failure criteria
• A confirmed fallback option for unsupported users

Not sure which testing approach applies to a specific provider? Reach out at [email protected] — we're happy to guide you through it.