Adding trust in transactions using credentials #468
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s components - Updating the existing Credential Objects in the schema/ folder, adding more details in it - Adding the Credntial schema in Agent, Customer, Organisation, Payment, Provider, Subscriber, Fulfillment, Item, Order objects - Added 2 more endpoints, cred/ and on_cred/
…ot standarised by VC specification
…o credentialSchema
… it backword compatible.
rajaneeshk90
changed the title
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The Beckn-One is a decentralized infrastructure designed to transform how network participants build trust and transact in a secure, scalable, and transparent environment. The goal is to embed trust into the flow of transactions.
As part of the effort, it is essential to have a Credential object in the transaction flow. This Credential object must support various types of credentials and it needs to be included in various components used in transaction, like Agent, Customer, Organisation, Payment, Provider, Subscriber, Fulfillment, Item, Order etc.
Summary of the changes
A new schema has been introduced to represent Verifiable Credentials. This allows the protocol server to handle Verifiable Credentials more effectively.
The existing Credential schema has been updated to support multiple credential types. A new field was added to accommodate credentials in the form of documents, such as PDFs or images, allowing entities to provide proofs in these formats. Another field was added specifically for Verifiable Credentials, enabling entities to provide proofs in this secure format.
The updated Credential schema has been embedded in the Organization, Payment, Provider, Subscriber, Fulfillment, Item, and Order objects. This integration builds trust into the transaction process, allowing sellers and buyers to include credentials directly in API calls (e.g., on_search, select).
The above change allows the network participants to embed trust in the transaction flow, i.e existing API endpoints.
Two new endpoints, cred/ and on_cred/, are added. These endpoints can be used when sellers or buyers do not send the required credentials in transactional API calls (such as on_search or select). In these cases, the seller or buyer can explicitly request the necessary credentials using these endpoints.
Changes
schema/VC.yamlto represent a verifiable credential object.schema/Credential.yamlto support Verifiable Credentialsschema/CredentialRequest.yamlschema to represent a credential request object for the cred/ api.cred/endpoint to be used to request a credential from an entityon_cred/endpoint to be used as callback to provide the requested credentials.verifiedfield in the context schemaMigration Impact
The changes are fully backward compatible. All modifications involved either the creation of new schemas or the addition of new fields to existing schemas.