Verified intent for critical actions.
PassProof binds a verified person to a registered device, confirms intent when a high-risk action occurs, and checks that what executes is exactly what was approved.
01
Certainty, not friction.
A step-up check on every action adds friction and erodes the value of the service.
PassProof keeps routine use seamless and concentrates on the actions that carry real risk — transfers, account changes, privilege grants — confirming that the rightful holder intended them. Your risk policy, not ours, defines what is in scope.
02
Four checks. One decision.
What PassProof delivers. Detailed specifications are shared in technical briefings.
Verified user
Links the account to a person verified through eKYC or your existing onboarding. Identity verification remains with you or your IDV provider.
Trusted device
Registers a device bound to that person — and preserves that trust when devices are added, replaced or lost.
High-risk action confirmation
Separates critical operations — large transfers, privilege changes — from routine use and requires the holder’s explicit approval.
Transaction integrity
Binds the approved details to what actually executes, reducing the risk of alteration after approval.
03
Complements your stack. Replaces nothing.
Identity verification, authentication and transaction authorization answer different questions. No single technology answers all three. PassProof has one defined role: verifying intent for critical actions.
| Existing control | Question it answers | Relationship to PassProof |
|---|---|---|
| Identity verification (eKYC / IDV) | Is this person who they claim to be? | Binds the verified person to a registered device and to the confirmation of critical actions. |
| Passkeys / FIDO2 | Is the sign-in coming from the user’s authenticator? | Sign-in stays with passkeys. PassProof adds intent and transaction confirmation for critical actions, and supports trust continuity across device changes. |
| JPKI (Japan’s My Number Card) | Government-issued certificate for identity and signature | Extends official identity verification into ongoing use and the confirmation of critical actions. |
| Username & password | Knowledge-based authentication | Enables a phased rollout: keep the existing login, add confirmation for critical actions only. |
Identity verification, authentication and transaction authorization are distinct. PassProof does not by itself provide the assurances other controls provide. Roles are defined for each customer’s architecture.
04
Secure by design, not by secrecy.
Security comes from design, implementation and testing — not from keeping a mechanism hidden.
No central store of user secrets
Users’ authentication secrets are not concentrated on the server by design. The server holds the registration data and records required for verification.
Narrow scope
Confirmation is reserved for operations the customer designates as critical. Usability and control, balanced.
Accountable records
Who approved what, from which device. Approval records support review and accountability.
No security technology stops every attack on its own. PassProof is designed to operate alongside the customer’s fraud controls, operations and user education.
Request a technical briefing
Share the operations in scope and your current authentication stack. We will show where PassProof fits and how it is deployed.