WalletOn

Who it’s for

Regulated institutions preparing for wallet‑based identity and emerging eID ecosystems, and looking to modernize onboarding without losing compliance control.

When you need it

• You want to reduce friction from repeated document capture
• You want cryptographic and privacy‑friendly proofs (share only what’s needed)
• You want a future‑ready approach to digital identity with compliant evidence
• You need a reliable fallback when wallet proof is unavailable

What it prevents

• Repeated ID capture for returning customers when a wallet proof can be accepted
• Over‑collection of personal data (collecting full document scans when only a few attributes are needed)
• Drop‑offs and operational effort caused by manual document capture and re‑keying
• Unclear audit trails about what was presented, who issued it, and why it was accepted or rejected
• “All‑or‑nothing” onboarding flows that fail when wallet proofing is unavailable

What you get

• Wallet proofing flows designed for onboarding (web & mobile)
• Selective disclosure (request only required attributes)
• Verification of credential validity and issuer trust (framework‑dependent)
• Policy‑based fallback to document capture via identOn

Key capabilities

• Verifiable credential verification
• Selective disclosure requests
• Credential status and revocation checks
• Evidence pack and decision traceability
• Web & mobile wallet journeys
• Fallback to identOn document capture when required

Trust & Compliance

• Clear policy rules for when wallet proofs are accepted vs step‑up required
• Audit‑ready records of what was presented and how it was validated
• Supports privacy principles through data minimization

Typical use cases

• Wallet‑based onboarding when customers have a supported credential
• Returning customers: avoiding repeated document capture
• Attribute proofs (e.g., residency / age) with minimal data sharing
• Cross‑border journeys where wallet proofs reduce friction
• Step‑up/fallback flows when wallet evidence is insufficient