How digital credential verification works

Step 1: The request

Imagine a venue needs to confirm that a customer is 18 or older. The business configures the accepted credential and issuer, the required age claim, and what should happen after the result. Cylinder starts a session and creates a presentation request. A QR code can reference that request for a cross-device journey, while a supported link can open it on the same device.

Step 2: The presentation

The wallet shows who is asking and what information has been requested. If the person approves, the wallet prepares a presentation from the matching credential and sends it to the verifier. Selective disclosure is available only when the credential format, wallet, and request support it.

Step 3: The check

The verifier checks the presentation's integrity, the credential signature, and the claims required by the configured flow. It can also evaluate expiry and supported status or revocation information. The business must still decide which issuers it trusts; a valid signature alone does not make every credential suitable.

Step 4: The result

Cylinder verifies the presentation, maps the relevant credential fields to the attributes configured for the flow, and returns the result. That record can include the outcome, time, flow, and reference. The business can then continue its process or send the case to an alternative review path.

When the check cannot complete

The person may decline the request, lack the required credential, use an unsupported wallet, or present an expired credential. These are not all the same as a failed identity claim. A useful workflow distinguishes an unsuccessful verification from an incomplete or unsupported journey and gives the person a clear next step.

What the business receives

Cylinder's attribute mapping turns common credential fields into consistent results. For an age flow, Cylinder can map a date of birth to age_over_18 and return true or false to the business. If the credential already contains an issuer-signed age threshold, Cylinder can request that claim directly. In either case, the workflow uses the mapped result instead of a copy of the full ID.

Where Cylinder fits

Cylinder manages the customer-facing flow around the supported verification service. Your team configures what to request, adds its branding, publishes a hosted link or QR journey, and reviews the configured result in one dashboard. Support, result fields, fallback paths, and retention are confirmed for the specific use case.