Questions About V.A.I.
Answers for platforms considering ChainPass, and for the users who hold a V.A.I. If your question is not here, ask us directly.
Tell us about your platform and we will walk you through requirements.
What Platforms Usually Ask
Nothing. ChainPass is completely free for platforms. There are no onboarding, integration, API, dashboard, custom-development, verification, subscription, or ongoing platform fees. The V.A.I. holder pays.
There is no integration fee and no platform fee and an extensive suite of APIs. Tell us about your platform and we will walk you through requirements.
No. Offer V.A.I. alongside your existing login process or use it as the access method for experiences that require verified users.
Yes. Platforms may use the ChainPass client dashboard instead of building a custom administrative interface. Nothing the client dashboard can do is hidden from the documented API.
Yes. The launch V.A.I. supports the platform requirements ChainPass agrees to administer. If a required capability does not already exist, ChainPass will build it for your platform at no cost.
Yes. Your platform controls its brand, rules, and user experience. ChainPass manages verification, onboarding, platform requirements, and security.
No. Your platform receives the V.A.I. and the confirmations it requires—not the user’s legal name, government ID, identity document, or verified photograph. Details a user gives your platform directly, such as a username or a contact channel, remain your platform’s own records.
What V.A.I. Holders Usually Ask
A unique seven-character alphanumeric identifier, cryptographically bound to the photo verified during your KYC session. It shows you are a real, verified user without carrying your legal name. It identifies a credential; it is not a password.
No. Use the same V.A.I. across every participating platform. If a platform has additional requirements, ChainPass will update your V.A.I. to meet them at no extra cost.
There is one V.A.I. today. Its annual price is set by ChainPass and shown before enrollment begins. The annual term runs from the date the V.A.I. is issued. Platforms are never charged—the V.A.I. holder pays.
No password is required. Email access alone cannot complete ChainPass recovery.
A live face match begins recovery. A registration OTP or one-time recovery password, followed by a recovery question, completes the normal recovery path.
It lets you confirm face-authenticated agreements, declarations, transactions, and authorizations with a live facial scan—without revealing your legal identity to the platform.
VAIRIFY’s One-Time 48-Hour Courtesy
When a user chooses VAIRIFY as their initiating platform, VAIRIFY can pay for that user’s ChainPass V.A.I. for 48 hours. The user owes nothing and has no obligation to pay afterward. The 48 hours begin only when the user explicitly activates the courtesy; opening the explanation page does not start them.
No. It is available once per user, for life. ChainPass facial recognition matches a second attempt to the existing V.A.I. and declines it. The user reactivates the existing V.A.I. instead.
The V.A.I. becomes inactive. The number stays the user’s for life. The annual term runs from the date the V.A.I. was originally issued, whether it is active or not. It does not restart when the courtesy ends, and it does not restart when the user pays.
Pay ChainPass to reactivate the same V.A.I. for the time remaining in its annual term. Payment does not start a new year, and verification is not repeated. For example, a user who pays six months after issuance receives the remaining six months.
A user checking it sees: “V.A.I. issued [date] via VAIRIFY’s one-time 48-hour courtesy. Currently inactive.” That names VAIRIFY as the sponsor and gives the issuance date. It applies only to a V.A.I. issued through the courtesy. For any other inactive V.A.I., the reason stays private. This is the planned design, not a live feature.
What Is Held, and by Whom
The photo verified during the KYC session, used for later face checks; the records of the agreements it administers; recovery questions and one-time codes; and the contact channel given at enrollment. The government ID and identity documents remain with the KYC provider, and ChainPass never learns the user’s legal name.
ChainPass has no endpoint that returns identity documents, and a platform’s API key or session key alone is not access to them. Identity evidence is held by the KYC provider. Any release would be a verified formal request handled through ChainPass. Ask platforms@chainpass.io for the current written procedure.
No. A platform never receives activity from elsewhere in the ecosystem, another platform’s requirements, biometric calculations, or facial-match percentages.
Live face matching is not switched on in production yet. Contact us for the current status; we will not quote a response time until it is measured on the live service.
Tell Us About Your Platform.
There is no integration fee and no platform fee and an extensive suite of APIs. Tell us about your platform and we will walk you through requirements.