Get paid when trusted information is reused.
Turn information you’ve already verified into a new revenue stream. With Truvera, you can create verifiable credentials that other organizations pay to verify, without tracking the people or credential behind each verification.
Verified once. Valuable beyond the first use.
Today, verified information is often used by one organization, while others repeat the same checks. With Truvera, that information can be reused and verified by approved partners, creating new revenue opportunities for the original provider.
With TruveraSet the rules. Set the fee. Track verification.
Establish a trusted ecosystem.
An ecosystem administrator approves participating issuers and verifiers and defines which credential schemas they can use.
Create verifiable credentials.
Issuers turn information they have verified into credentials that holders can present to approved partners. Paid credentials are bound to the relevant ecosystem.
Set verification fees.
The ecosystem administrator assigns a price to the relevant credential schema. Participating verifiers can see the fee.
Verify and report usage.
When a credential is presented, Truvera’s ecosystem broker checks that the verifier is authorized before returning the verification result. The administrator can download reports to support invoicing and settlement.
Truvera enables controlled verification and reporting; the ecosystem administrator handles invoicing, payments, and commercial relationships with participants.
Read the monetization documentationTrack the verification. Not the person behind it.
The ecosystem administrator needs enough information to bill participating organizations. It does not need to know which specific holder or credential was checked.
Truvera’s privacy-preserving verification model lets the administrator report which verifier checked a credential schema from which issuer, without identifying the specific holder or credential instance through that reporting process.
Billing report can include
Not disclosed to the issuer or administrator through paid-verification reporting
The specific holder or credential instance verified, or the attributes shown to the verifier.
The model uses privacy-preserving cryptography, including Keyed Verification Anonymous Credentials (KVAC).
Read about the technical approachFor organizations whose verified information others need.
Truvera can fit into existing systems through its supported credential and verification interfaces. The ecosystem administrator can use reporting alongside existing billing processes.
Identity verification providers
Enable participating partners to verify previously checked identity information.
Business verification providers
Make verified business information reusable across platforms and partner networks.
Telecom operators
Support partner verification of trusted information such as account ownership.
Insurance and certification providers
Explore fee-based verification of coverage or qualifications within trusted networks.
Common questions
No. Truvera supports controlled verification and provides billing reports. The ecosystem administrator handles invoicing, settlement, chargebacks, and commercial agreements. Truvera charges a platform commission, subject to its applicable minimum fee.
No. Paid credentials are bound to an ecosystem, and verification is restricted to authorized participants for the relevant credential schema.
Not through the paid-verification reporting flow. They can see issuer, verifier, schema, verification activity, and fees, but not the particular holder or credential instance that was presented. The verifier can still see the attributes disclosed to it.
Could the information you verify create value again?
Explore which partners could reuse it and how a paid verification model could work for your organization.
