Introduction to Verification
Blerify's verification product is the Universal Point of Verification — UPoV: one integration through which your business obtains verified information from credential holders. It answers one question: can I trust the credential this person is showing me? When someone presents a digital credential on your website or in your app, UPoV checks that it's genuine, that its issuer hasn't revoked it, and that it belongs to the person presenting it — not to someone else. You get a clear answer in seconds.
For the person being verified, it feels simple: they tap a button or scan a QR code, their digital wallet shows them exactly what you're asking to see, and they approve with their fingerprint or face. No forms to fill in, no documents to photograph, no waiting for a review.
For your team, the work splits in two. Someone configures a verification rule in the Blerify Portal — a point-and-click setup where you choose which credential to accept and which details to request; no code involved. Then a developer connects your system to Blerify with two simple calls. Nobody on your side has to understand cryptography: Blerify runs the checks and reports the facts.
Everything in this section falls into one of four parts. If you want to see the product applied to a real scenario before deciding anything, read a Use Case — no technical background needed. Developers here to ship start with Build. Learn explains what the checks actually prove, and Reference is for lookup.
Next steps
Create a Verification Rule — the Portal setup every verification starts from.
See also: Age Verification — a complete scenario in five minutes of reading · Assurance Tiers — how much proof each tier gives you.
Last updated

