âģī¸Charge for Verifiable Credentials
Charge for Verifiable Credentials using encrypted DID-Linked Resources (DLRs) with Access Control Conditions, and build Verifier-pays-Issuer payment flows.
Last updated
Was this helpful?
Charge for Verifiable Credentials using encrypted DID-Linked Resources (DLRs) with Access Control Conditions, and build Verifier-pays-Issuer payment flows.
Last updated
Was this helpful?
Credential Payments brings a significant evolution to the Verifiable Credentials landscape, allowing verifiers to directly pay issuers to unlock Credential Status information. Underneath the hood, we've engineered a robust and secure payment flow that streamlines the end-to-end payment process, with accuracy, speed, and cryptographic integrity.
Create encrypted Status Lists on-ledger, and pay to unlock the Access Control Conditions in CHEQ, using our cheqd Studio Payments APIs:
Charge for Status List
With Credential Payments, Issuers are able to create payment-gated Status Lists in order to charge for the verification of Credential Status information.
Issue Credential with Encrypted Status List
Issue a Verifiable Credential referencing an encrypted Status List in the body, with a specified bitstring index.
Verifier pays Issuer
Understand how a Verifier pays an Issuer in CHEQ to unlock Status List and verify Credential Status.
Bulk Update or Rotate Encryption Keys
Update a set of Credential indices or rotate the encrypted symmetric key for the Status List.
Build your understanding of How Credential Payments work, including Access Control Conditions and how the model preserves privacy.
Understanding Credential Payments
Before diving into Credential Payments, developers may want to learn how the Payment gating and Access Control condition logic works.
Why are we payment gating Status Lists?
Learn about the role of cheqd in Trusted Data Markets and why we are payment gating the "reputability" of Credentials.
Below are a list of alternatives for using Credential Payments.
