Connect Systems to Verified Identity Data
Enable authorised agency and organisation systems to receive approved identity-related information from TRIDENT and EBC through protected, purpose-bound APIs.
Government agencies and authorised organisations can use TRIDENT for system-to-system identity verification when the citizen does not need to participate directly in each interaction.
This model supports automated processes while avoiding unrestricted access to the EBC National Identity Register or other authoritative sources. TRIDENT governs the requesting system, approved purpose, permitted scopes and applicable policy controls.
How it works
- The agency or relying-party system is registered and authorised.
- The system requests access from TRIDENT using its institutional credentials.
- TRIDENT authenticates the client and applies the approved scopes and policies.
- The system calls a protected EBC API or TRIDENT VDG service.
- The API validates the authorisation and returns the approved response.
- The interaction is recorded for traceability and auditability.
Possible responses
Depending on the approved use case, the service may receive:
- a selected verified attribute;
- a match result;
- identity or document status;
- an eligibility result;
- a minimised attribute set;
- a yes/no response.
Where prior citizen authorisation is required, TRIDENT can also validate the applicable consent or authorisation record before allowing access.
Typical uses
- Automated identity verification.
- Backend eligibility checks.
- Government-to-Government identity validation.
- Document or registration status checks.
- Recurring verification under approved rules.
- Background processing for authorised services.
Technical access is limited to registered clients, protected endpoints, approved scopes and defined purposes. It does not provide general access to authoritative databases.
