Learning Docs
Product DocsTechnical DocsLearning & GovernanceUseful Links
  • Learn about cheqd
  • Getting Started
    • ♟️What is cheqd?
    • ✋What is Creds?
  • Decentralised Identity
    • 🟢Start here
    • What are DIDs?
      • What is a DID?
      • What is a DID method?
      • What is a Verifiable Data Registry?
    • What are Verifiable Credentials?
      • What is a Verifiable Credential?
      • Types of Verifiable Credential
        • JSON (JWT)
        • JSON-LD
        • AnonCreds (ZKCreds)
        • SD-JWT
      • What is a Verifiable Presentation?
    • What are DID-Linked Resources?
  • $CHEQ
    • 🟢Start here
    • 📈Tokenomics
      • Tokenomics: Part 1
      • Tokenomics: Part 2
      • Tokenomics: Part 3
      • Tokenomics: Part 4
      • Circulating Supply Explained
      • Network Parameters
    • ✍️Identity writes
    • ♻️Credential Payments
      • Verifier pays Issuer
      • Holder pays Issuer
  • Governance
    • 🟢Start here
      • Introduction to Governance
      • Introduction to Entropy
      • Governance Principles
        • Foundational Principles
        • General Principles
    • 📚Learn
      • 🍎Core concepts
        • Staking
        • Slashing
        • Validating
        • Voting
        • Community Pool
      • ✏️Terminology
      • 📖Glossary
    • 🍍How to Participate
      • How to stake
      • How to vote
      • Making Network Changes
        • Minor Network Changes
        • Major Network Changes
    • ⚡Advanced
      • What is a Liquidity Pool?
        • How do liquidity pools work?
        • How to take part in a Liquidity Pool
      • CHEQ-ERC20 wrapped token
        • Why did we decide on a bridge to Ethereum?
        • What is the Gravity Bridge?
        • Why did we decide to use the Gravity Bridge?
        • What other bridging options did we explore?
        • How to send tokens to Ethereum with Gravity Bridge
        • How to add CHEQ tokens to UniSwap Liquidity Pools
        • How to send CHEQ tokens from Ethereum to cheqd
  • ⚖️ Legal
    • License
    • Code of Conduct
    • Security Policy
    • Legal Disclaimer
  • 🆘Support
    • System Status
    • Slack Channel
    • Discord
Powered by GitBook
LogoLogo

General

  • Website
  • Blog
  • Get $CHEQ

Product Docs

  • Product Docs
  • cheqd Studio
  • Creds.xyz

Technical Docs

  • Node Docs
  • GitHub
  • Block Explorer

Learning Docs

  • Learning Docs
  • Governance Docs
  • Governance Forum
  • Governance Explorer
On this page
  • Overview
  • Payment models explained

Was this helpful?

Edit on GitHub
Export as PDF
  1. $CHEQ

Credential Payments

Understand how $CHEQ is used for payments for verifiable credentials

Last updated 7 months ago

Was this helpful?

Overview

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.

Payment models explained

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 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 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.

new regulations like eIDAS 2.0
cheqd Studio