Menu

VC use case

External agent access to member policies

Delegated and regulated access for agents to a customer’s policies

  • Finance
Issuer authoritative source creates the claim
Holder person or organization presents proof
Verifier service checks status and makes a decision

Overview

Financial institutions can grant regulated agents delegated access to customer policies using Verifiable Credentials, with clear proof of authority and licensing.

The policy system can verify that an agent has current authority from the policy holder and any required regulatory license before exposing policy information or allowing action.

Why it matters

Delegation is heavily regulated and hard to manage at scale. Institutions need to support advisers and agents without relying on static notes, broad manual approvals, or repeated document checks.

Verifiable Credentials create a cleaner model:

  • the policy holder grants authority with explicit scope
  • the institution issues delegation evidence
  • regulators or licensing bodies issue agent credentials where needed
  • the agent presents both forms of proof when accessing a policy
  • the verifier checks issuer trust, scope, status, and expiry before access is granted

Ecosystem roles

  • Issuer: The financial institution and relevant regulator (license or authority claims).
  • Holder: The agent or adviser.
  • Verifier: The institution’s service channels that grant access.
  • Policy holder: The customer who grants authority over a defined policy or action.
  • Trust governance: The rules that define accepted issuers, license types, delegation scope, status checks, expiry, and revocation.

Trust decision

The verifier decision is narrow: can this agent access or act on this member policy for this policy holder right now?

That decision may depend on delegation scope, agent license, policy type, transaction sensitivity, expiry, and revocation status.

Privacy and assurance

The verifier should request only the delegation and licensing evidence needed for the policy action. A read-only policy enquiry, advice update, and transaction instruction may require different scopes.

Assurance depends on checking issuer trust, credential binding, status, expiry, and whether the requested action fits the delegated authority.

Implementation notes

  • Model policy-holder consent and agent licensing as separate credentials where different issuers control them.
  • Include revocation and expiry so delegated authority can be withdrawn quickly.
  • Keep the policy platform responsible for final access enforcement even after credential verification succeeds.
  • Define exception handling for disputed authority, vulnerable customers, urgent access, and manual compliance review.
Objective
Grant an agent controlled access to a member policy.
Description
Issue and verify credentials that allow a financial agent to access a policy offered by a financial institution.
Actors
Policy holder; financial agent; financial institution; regulator or licensing body.
Dependencies
Delegation credential, license credential where required, issuer trust registry, status endpoints, and policy access rules.
Preconditions
The policy holder has granted authority for the agent to access or act on a policy.
Postconditions
The financial agent can access only approved policy information or actions while authority remains current.
The policy holder delegates authority to the financial agent. The regulator and financial institution issue license and delegation credentials to the agent, who stores them in a wallet.
The policy holder requests delegated authority from the financial institution. The institution issues a delegation credential and the regulator issues a license credential to the wallet. The agent stores the credentials and the wallet confirms they are ready.
The financial agent presents credentials to the service channel verifier. The verifier checks issuer, scope, and status with the trust registry and grants access to the policy system.
The financial agent approves presentation in the wallet. The wallet presents delegation and license credentials to the service channel, which checks issuer, scope, and status with the trust registry. After confirmation, the service channel grants access and the policy system returns policy details to the agent.

Talk to UNIFY

Explore how this use case could work in your trust ecosystem.

Share the scenario you are testing and we will help map the issuers, holders, verifiers, and policy decisions involved.
Looks good!
Please enter your name.
Looks good!
Please enter your company.
Looks good!
Please enter your e-mail address so we can contact you.
This form uses Google ReCaptcha to ensure interactions with our site are from legitimate users. Please accept the use of recommended storage before submitting the form. Find out more at the Privacy Centre.
Your message could not be sent. Try again later.