Integrations

VCT Registry is referenced by every issuer and resolved by every verifier and wallet. It's deliberately thin — one job, one endpoint.

Where it fits

Credential Issuer

Credential templates reference VCT URLs. The VCT metadata carries schema + display info that wallets use when rendering credentials from that issuer.

Broker

On receiving a presentation, Broker resolves the VCT to validate claim shapes and render decision metadata to audit logs.

eIDAS Verifier

Same pattern as Broker — VCT resolution for validation + audit. Qualified VCTs may chain to member-state trust lists.

Cloud Wallet + Native Wallet SDK

Wallets resolve VCTs to render localised display text, icons, and claim ordering. Users see meaningful labels, not raw JSON.

Trust Registry (complementary)

Trust Registry answers "who can issue?" — VCT Registry answers "what are they issuing?". Cross-linking in the admin UI lets operators navigate from an issuer entry to the VCTs they're authorised for.