Banks and financial institutions
Account-opening and account-holder statements, with an identifiable source and a status recipients can check.
For credential issuers and professional services
Help recipients check who issued a credential, whether it is still valid and what information they need to see. Start with the proof your institution provides.
An accountable issuer
Connect each statement to its source.
A current status
Check validity when the proof is used.
Only necessary information
Design sharing around the recipient’s need.
Different services. A shared verification need.
Institutions issue statements that people reuse elsewhere. Make the source, scope and validity easier for the next recipient to understand.
Account-opening and account-holder statements, with an identifiable source and a status recipients can check.
Income and financial statements that clearly identify the reporting period, issuer and information being shared.
Shareholding, authority and legal-opinion statements with a defined scope, supporting basis and version history.
Energy-rating evidence linked to the assessed property, assessment date, responsible assessor and validity period.
Product and facility assessments that identify the applicable criteria, evidence and responsible issuing body.
Explore qualification, employment and insurance-coverage proofs that recipients can verify without repeated manual enquiries.
These are candidate use cases. Document types, issuer qualifications and recipient requirements are confirmed for each deployment.
A clearer verification result
Signature integrity, issuer identity, validity dates and current status answer different questions. A useful result makes those checks explicit.
An intact signature is not enough to accept a credential. Check its validity period and status, and whether the issuer and statement meet the recipient’s requirements.
Illustrative example
In this scenario, the credential is within its validity period and the latest status check reports it as active.
This demo uses fictional data and simulated checks. It does not verify or change a real credential.
From issuance to ongoing trust
Agree the template, scope, validity period and staff allowed to prepare, review and sign.
Associate the statement with its issuing organization and protect the signed content against undetected changes.
Choose a link, QR code or system integration, with disclosure suited to the recipient and purpose.
Manage expiry, suspension and revocation. Plan renewals and corrections so earlier proofs are not mistaken for current ones.
We will confirm templates, review steps, audit needs, batch issuance and integration options for your organization before rollout.
Privacy with a clear purpose
Keeping information off a public page and limiting what a verifier receives are different needs. Choose the right sharing model for each credential.
Decide what is public and what requires authorized access. A verification link should not become an open customer record.
Plan customer-authorized sharing around a specific recipient and purpose, rather than distributing the whole customer file.
Sharing selected signed fields or proving a condition without revealing the underlying value requires a suitable credential format and verification flow. Discuss availability for your use case.
Before you issue
No. Revocation changes the credential’s status; it cannot remove PDFs or screenshots already held by someone else. Recipients need to check the current status when relying on the proof.
No. A signature helps establish origin and integrity. The issuer remains responsible for its statement, and the recipient must assess applicable rules, issuer qualifications, scope and supporting evidence.
Different professions need different statements, review processes and sharing controls. Contact us to confirm the supported document format and workflow before using it with customers.
Start with one proof
Tell us what you issue, who receives it, how its status changes and which information must stay private. We will help define a suitable starting point.