Test vs. Live Environments
This page explains the two environments which Trinsic makes available; what you can and can’t do in each; and how to move from testing to production.
Overview
Trinsic offers two different environments: Test and Live.
Each environment is isolated from the other: Verification Profiles, Sessions, and API Keys are all tied to a specific environment, and cannot be transferred between environments.
Within the Trinsic Dashboard, you may switch between environments at any time by using the environment switcher in the bottom left. A colored bar at the top of the Dashboard serves as a visual indicator of the environment you are using at any time.
Test Environment
The Test Environment is intended for non-production use cases; use it during product evaluation, development, and for automated test suites.
Within the Test Environment, there are two kinds of Providers available:
- Trinsic "Mock" Providers
- These are Trinsic-hosted Providers which mimic the behavior of real Providers. They are the easiest way to explore the platform's functionality and test your integration during development.
- We recommend writing automated test suites against these Providers.
- Test-enabled Identity Providers
- These are real Providers which offer the ability to perform test verifications with test credentials.
- Not all Providers offer a test environment; these are not available in the Test Environment.
- For information on how to test with specific providers like BankID Sweden, SPID, Bangladesh NID, LA Wallet or any other test-enabled provider, visit the documentation page for the respective provider.
Verifications performed in the Test Environment will fail if a real credential is used. Test verifications do not incur a per-transaction cost.
Live Environment
The Live Environment allows you to perform production verifications with real user data. Test credentials will not work; a real user with a real credential or account with a Provider is the only way to perform a verification in the Live Environment.
Because a real credential must be used, testing your integration in the Live Environment can be difficult. Oftentimes, teams will find testers in their organization who live in relevant geographies, or tap into Trinsic’s network of testers. If you need help finding testers, please reach out to your Trinsic contact.
Verifications performed in the Live Environment incur a per-transaction cost.
Why aren’t some providers enabled?
In the Test Environment
In the Test Environment, you are able to perform test verifications with any Provider which makes available a test mode. However, certain Providers have no mechanism by which they can be tested without a real credential, and can only be used in live mode. These Providers are not shown in Trinsic's test environment.
In the Live Environment
Based on your order form with Trinsic, you may only have access to certain Providers in the Live Environment. Additionally, some Providers require additional steps in order to be enabled for production usage. These steps may include:
- A simple approval from the Trinsic team
- A use-case approval by the provider
- A separate contract between the end customer and the Provider
Comparison of environments
Capability | Test Environment | Live Environment |
---|---|---|
Providers shown | Trinsic-hosted "mock" Providers Providers which expose a test environment | Live Providers enabled for your organization |
Data used | Fake/test data only | Real end-user data |
Verification results | Not valid for production decisions | Production‑grade verifications |
Billing and Cost | Transactions not billed | All transactions billed per your plan |
Use cases | Integration; staging; automated testing; demos | Launch; pilots with real users; production. |
Updated about 2 hours ago