β»οΈCredential Payments
Understand how $CHEQ is used for payments for verifiable credentials
Last updated
Understand how $CHEQ is used for payments for verifiable credentials
Last updated
One of the most repeated bits of feedback that we've had, throughout our survey results and community engagement, is that: more easy explanation and examples on how cheqd can be used in practice would better help people understand the project.
These subpages will try and lay out simple use cases where cheqd will be able to create new commercial models.
There has been a consistent cold start problem for digital credential ecosystems where organisations do not see a clear commercial model or revenue opportunity to justify the switch up costs to credential-based technologies. This is because the perceived value in Verifiable Credentials is the costs saved when there is a significant amount in circulation (the chickenπ), but this cannot occur without organisations issuing credentials in the first place (the eggπ₯).
Unfortunately, the benefits of credentials, prior to the point of mass adoption, provide no compelling reason for businesses to change their current data collection and retention practices until this is the case.
Since launching cheqd, our hypothesis has been that Credential Payments will be the catalyst for credential adoption, by incentivising issuers to release data back to the holder, and allowing them to set a price for trusted data checks. This thinking has since been validated by data collected by cheqdβs partners and potential customers, where 70% of respondents believed that payment rails would help drive adoption with their customers.
We now believe that credential ecosystems are technically mature enough to scale, especially with new regulations like eIDAS 2.0 accelerating their adoption and providing a template for interoperability. Yet, there is a barrier between the theoretical and philosophical benefits of Verifiable Credentials, and the commercial and business benefits of Verifiable Credentials. A payments or incentive layer is still required to provide a compelling reason for enterprise organisations to make the switch.
To achieve this shift, weβve built Credential Payments into our cheqd Studio product to allow organisations to build trusted data markets easily, with simple REST APIs. This abstracts the complexity and responsibility of handling interactions with the ledger and provides a clear integration pathway for developers that are not familiar with decentralised identity standards or blockchain.
Verifier Pays Issuer
This is cheqd's unique superpower for monetising credential issuance, creating new commercial models for companies engaging in credential ecosystems.
Holder pays Issuer
A more simple payment flow, enabling Holders to pay Issuers directly for "purchasing" credentials from them.