Skip to main content

Define and Issue a Wallet Credential

Work with TRIDENT to define a trusted credential, establish your Agency as an authorised issuer, connect approved source data and deliver the credential securely to eligible users.

Government agencies and authorised organisations can work with the TRIDENT team to introduce approved credentials representing identity attributes, rights, status, eligibility, qualifications or permissions.

Each credential type must have a defined purpose, responsible organisation, authorised issuer, source of trusted information, credential structure and lifecycle policy. TRIDENT Shared Services provide the common identity, trust, issuance and audit capabilities needed to operate within the national Wallet ecosystem.

How it works

  1. Define the credential purpose and intended users.
  2. Establish the identity and authority of the organisation responsible for the credential.
  3. Register the organisation as an authorised Credential Issuer within its approved scope.
  4. Define the credential schema, including the key attributes and metadata.
  5. Connect to an authoritative or approved source to validate eligibility and credential data.
  6. Define the issuance and lifecycle policies.
  7. Test the integration and issue the credential to an activated TRIDENT Wallet.

Credential policies

The credential definition may include:

  • eligible holders and issuance conditions;
  • mandatory and optional attributes;
  • data minimisation and disclosure rules;
  • validity and renewal periods;
  • suspension and revocation rules;
  • replacement and re-issuance;
  • approved relying-party use cases;
  • credential and issuer status checking.

TRIDENT Shared Services

Depending on the approved model, TRIDENT may support:

  • issuer onboarding and trusted organisation identity;
  • issuer registration and trusted-entity publication;
  • user authentication and Wallet Trust Validation;
  • authoritative-source integration;
  • credential creation, signing and secure delivery;
  • credential status and revocation;
  • auditability and operational monitoring.

Possible credentials include licences, permits, professional qualifications, education credentials, eligibility evidence and representation rights.

New credential types are introduced progressively and remain subject to Government approval, source-data readiness, policy definition, privacy and security review, and conformance validation. The architecture specifically requires each credential to define its issuer, purpose, schema, rulebook, lifecycle, status model and relying-party use cases before introduction.

View Developer Resources