Self-sovereign identity is a model where people hold and control their own verifiable credentials and share only what a given interaction needs, with no central identity authority in the middle. The aim is to cut repeat KYC and shrink how much personal data gets exposed every time someone proves who they are.
What is SSI, in plain English?
Self-sovereign identity flips the usual model. Instead of every bank, employer, and app holding its own copy of your identity data, you hold verifiable credentials in your own wallet and present them when needed. A university issues you a degree credential, a government issues an ID credential, and you carry them, deciding case by case what to reveal.
The signature idea is selective disclosure: you share only the attribute an interaction requires. To prove you are over 18, you present a yes-or-no age claim rather than handing over your full birth date, name, and document number. There is no central identity authority that sees every transaction, which is meant to reduce both repeat verification and data exposure.
For fraud and AML teams, SSI does not remove risk, it relocates it. Trust shifts from a central verifier you control to the credential issuers, the revocation system that says whether a credential is still valid, and the binding that proves the person presenting a credential is really its subject. Those three become the things you have to check.
Centralized identity versus SSI
What changes | Centralized identity | Self-sovereign identity |
Who holds the data | Each provider stores its own copy. | The person holds it in a wallet. |
What you disclose | Often the full record. | Only the attribute needed. |
Repeat KYC | Redone at every provider. | Reuse a verified credential. |
Where trust sits | The central verifier. | Issuer, revocation, holder binding. |
Main fraud worry | Breach of the central store. | Stolen or misbound credentials. |
Who is involved?
Who | Their role |
Issuer | Vouches for an attribute and signs a credential, such as a government or a bank. |
Holder | The person who keeps credentials in a wallet and chooses what to present. |
Verifier (relying party) | The business that checks a presented credential and decides whether to trust it. |
Revocation system | The mechanism that says whether a credential is still valid or has been withdrawn. |
What it looks like in practice
In practice
A fintech lets new customers onboard with a reusable identity credential issued by a bank that already ran full KYC. An applicant presents the credential and a selective age-and-name claim. The fintech verifies the issuer signature and checks the revocation registry, confirming the credential is genuine and still valid.
But the team does not stop there. It runs a holder-binding step, a live liveness and face check, to confirm the person presenting the credential is its actual subject and not someone who bought or stole the wallet. Only when issuer, status, and binding all line up does it accept the credential in place of a fresh KYC pass.
Why it matters to operators
SSI is attractive because it promises less friction and less data to breach: customers reuse a verified credential instead of redoing KYC, and you hold fewer copies of sensitive records. For onboarding and cost, that is a real win.
The trap is treating a valid-looking credential as proof of a genuine person. A credential can be legitimately issued yet presented by the wrong human, or issued by a party whose standards you do not know. So verify issuer reputation, always check revocation status, and require a holder-binding check. Possessing a credential is not the same as being its subject, and that gap is exactly where fraud lives.
What to watch for
- Unknown issuers. A credential is only as trustworthy as the party that signed it; vet issuer reputation and standards.
- Skipped revocation checks. A valid signature does not mean the credential is still active; always check status.
- No holder binding. Accepting a credential without proving the presenter is its subject invites stolen-wallet fraud.
- Wallet compromise. A takeover of the holder's wallet hands an attacker every credential inside it.
- Over-trusting reuse. Reusable credentials cut friction but inherit any weakness in the original verification.
Quick questions
Does SSI remove the need for KYC?
No, it can let you reuse a credential from an earlier KYC rather than repeat the whole process, but you still have to trust the issuer, confirm the credential is valid, and bind it to the live person. It moves the work, it does not delete it.
What is selective disclosure?
It is sharing only the specific attribute an interaction needs, like a yes-or-no age claim, instead of your full identity record. It reduces the personal data a verifier collects and stores.
What is holder binding and why does it matter?
Holder binding is proving the person presenting a credential is really its subject, usually with a liveness or biometric check. Without it, a stolen or purchased credential can be replayed by an impostor, so it is the control that stops possession from masquerading as identity.
Where does trust live in SSI?
In three places: the issuer that signed the credential, the revocation system that says whether it is still valid, and the binding that ties it to the live holder. A weakness in any one undermines the whole check.
How is SSI different from a digital identity wallet?
A digital identity wallet is the app that stores and presents credentials; SSI is the broader model of user-held, decentralized identity that such wallets implement. The wallet is the tool, SSI is the architecture.
Go deeper
- NIST Digital Identity Guidelines (SP 800-63) ↗ — The US standard for identity proofing and authentication assurance levels.
- FATF ↗ — The global standard-setter for AML, counter-terrorist-financing, and counter-proliferation. Recommendations, guidance, and jurisdiction lists.