Proof,
not data.
Verify more, store less, demonstrate better
Affinity connects digital credentials to your onboarding and access processes. Verify the proof you receive and retain technical evidence in compatible flows, without replacing your applications.
TRUST LAYERThe platform is integrated through pilots. We validate issuers, credentials, wallets and evidence coverage with you before expanding the flow.
From checking a credential to using it in your process: explore the components, the flow and the current scope.
01 — 07The onboarding everyone recognises
- 01People sign up again with documents, selfies and data they already provided elsewhere
- 02Your organisation accumulates copies, repeats checks and fragments traceability across systems
- 03Compliance must show which policy applied to each decision — and cannot always do so
- 04More friction for the user; more risk and operational load for the team
What changes
- Minimum proof from wallet
- Explicit policy per resource
- Auditable receipt without extra PII
Give your checks a common foundation.
Configure models in Trust Console and connect their reference to the verification flow.
- Start with age, KYC or driving licence templates.
- Manage and publish models in a technical environment; simulation has a basic scope.
- Verify with OIDC4VP and compatible wallets validated for your integration.
Define the policies
Trust Console
Templates and technical publication are available. The full business rule editor is still evolving.
Explore productFrom proof to the next step.
An example connecting wallet, verification and evidence.
Configure the model and its reference for the agreed flow.
The person presents proof. Your application uses the result. A compatible flow retains evidence.
The check ends. The context remains.
Technical evidence to review what happened.
- 01
Review the result and context in available receipts.
- 02
Check integrity through hashes and, when configured, verifiable signatures.
- 03
Export JSON or PDF. Receipts exclude the personal attributes evaluated; source retention is configured separately.
Evidence receipt
ER-DEMO-0084sha256:7e4b…a92fWhen the first flow works, you can go further
Extend your integration once the first use case is validated.
Issuer Studio
After an initial verification, issue reusable credentials for future access without repeating the same KYC.
Explore productAgent Trust
Identity, delegation and authorisation to limit agent actions. Your system enforces the result and local blocking.
Explore productLet’s talk about your first use case.
Define what you need to verify, which systems are involved and how to measure whether the integration solves the problem.
- The process you want to improve
- The credentials and systems involved
- A concrete scope and success criteria