Five customer archetypes Broker is built to serve. Each is a concrete wallet profile + presentation definition that a neobank, platform, employer, retailer, or municipality has asked for.
1
Remote KYC for a fintech
Customer: A Dutch neobank onboarding retail users.
Asked for
- Replace document-upload KYC with an EU wallet presentation
- Receive identity claims signed by the government, not a KYC vendor
- Complete the flow in under 30 seconds
Presentation
PID credential from an EU member state — given_name, family_name, date_of_birth, nationality. Trust Registry must list the issuer.
Result
Zero document uploads. No KYC-vendor subscription. Onboarding drops from minutes-to-days to seconds.
2
Credential-gated platform access for healthcare
Customer: A prescription-management platform for GPs, pharmacists, and clinical nurses.
Asked for
- Only licensed practitioners can prescribe controlled substances
- Licence credential is issued by the national registration board
- Revoked practitioners must lose access within minutes
Presentation
HealthcarePractitionerLicense — practitioner_type, licence_number, valid_until. Constraint: valid_until > today.
Result
Board revokes a practitioner → next verification rejects → controlled-substance capability gone. Same-day propagation, not end-of-month batch.
3
Employee onboarding at a large employer
Customer: An international consulting firm hiring 500+ junior consultants annually.
Asked for
- Single presentation delivers diploma + tax ID + address in one scan
- New hire doesn't upload a dozen documents to an HR portal
- All credentials are independently verifiable
Presentation
Multi-credential: DiplomaCredential + TaxIDCredential + AddressCredential — each with its own issuer trust chain.
Result
Onboarding paperwork becomes 'open your wallet and tap once.' HR systems reduce document-review staff and manual-entry error.
4
Age verification on a website (age-gate)
Customer: A Dutch online retailer selling age-restricted goods (alcohol, nicotine, gambling).
Asked for
- Don't ask for a full PID presentation — only over-18 proof
- Regulator wants proof we're verifying, not just asking
- Flow must work for under-60-second conversion
Presentation
PID with limit_disclosure: required — only the derived age_over_18 claim. Birth date never leaves the wallet.
Result
Regulatory compliance without privacy-harmful data collection. Birth date never transits retailer infrastructure or logs.
5
Government service — digital permit application with PID
Customer: A Dutch municipality replacing a paper-based permit application.
Asked for
- Citizen proves identity via wallet instead of uploading a passport scan
- No DigiD dependency for services that don't need DigiD LoA High
- Clerk doesn't handle personal data during the application
Presentation
PID credential — given_name, family_name, bsn, date_of_birth.
Result
Citizens don't retype personal data; municipality receives cryptographically-verified data. Form fraud drops materially; processing time drops because verification is built in.
