Product Note
The Identity and Trust Layer for an Open, Interoperable Beckn Network
Executive Summary
Digital ecosystems across sectors—commerce, mobility, energy, sustainability, public services, and more—need a reliable way for participants to identify, authenticate, and communicate with each other. Today, this often requires custom integrations, manual key exchanges, or sector-specific directories that don’t scale.
The Beckn.One Registry Service, built on the DeDi Global infrastructure, an implementation of the Decentralized Directory Protocol (DeDi), provides a verifiable identity directory for any Beckn-enabled participant. It enables organizations of all types to publish network identity under their own domains, ensuring trusted addressability and interoperability across Beckn-based networks.
1. Why the Registry Service Matters
The Problem Today
Many facilitators and network operators maintain their own directories of participants. As networks expand, keeping these directories in sync, verifying identities, and updating configuration data becomes increasingly complex.
Because each directory is independently operated, they naturally become isolated, making cross-network interaction more difficult.
The Beckn.One Registry Service provides a shared, protocol-aligned foundation for publishing identity information while allowing facilitators to continue curating and governing their networks as they always have.
2. The Beckn.One Approach
The Registry Service provides:
✓ Global Addressability
Every Beckn-compatible participant gets a resolvable, protocol-standard identity under a verified namespace—making it straightforward for entities to reference, validate, and interact with one another.
✓ Self-Owned Identity Records
Participants publish their own subscriber information under their own domain, ensuring autonomy and reducing duplication across registries.
✓ Cryptographic Trust Without Manual Effort
Public keys, domain proofs, and signing details are published in a consistent, verifiable format. This removes the need for custom key exchanges or facilitator-specific trust setups.
✓ Seamless Integration with Beckn ONIX
Beckn ONIX automatically retrieves subscriber details during transactions. No additional registry APIs, integrations, or onboarding workflows are needed.
The result is a simpler, more coherent technical foundation that empowers facilitators while strengthening the entire network.
3. What the Registry Service Enables
a. Global Addressability
A uniform, protocol-defined way to reference participants across ecosystems—regardless of sector or facilitator.
b. Verifiable Trust Layer
Domain-anchored identities ensure:
Authenticity
Key validation
Signed request verification
All without manual coordination.
c. Structured Subscriber Data
Standardized schemas for:
Subscriber ID
Callback URLs
Domain codes
Network roles (BAP/BPP/CDS/etc.)
Public keys
Ensuring compatible, predictable integrations.
d. Facilitator Support
Facilitators can publish Subscription Reference Directories — curated sets of participants — while relying on the registry service as the technical backbone for addressing and validation.
e. Seamless Interoperability with Beckn ONIX
Beckn ONIX automatically:
Retrieves subscriber information
Fetches keys
Performs signing and verification
Allowing participants to transact smoothly without extra integration steps.
4. Key Benefits
⭐ Global Addressability
A unified reference system for interacting with Beckn participants across domains and networks.
🔒 Secure & Verifiable Interactions
Public keys and signing information are published in a consistent, verifiable manner.
⚡ Zero-Integration Onboarding
Participants simply publish their records—no additional registry API implementation required.
🧩 Self-Managed Identity
Participants maintain their own records with subscription data.
♻️ Applicable Across Sectors
Suitable for commerce, mobility, health, energy, sustainability, public services, and any domain adopting Beckn.
5. Who Should Use This Service
Organizations Building Beckn-Enabled Systems
Across any sector — energy, mobility, sustainability, commerce, public services, etc.
Developers
Implement Beckn flows without managing discovery, key-exchange setups, or custom integrations.
Facilitators & Network Operators
Curate and govern networks with ease, without carrying the full technical maintenance burden of identity/addressability infrastructure.
Enterprises & Agencies
Standardize trust and identity across wide-ranging digital ecosystems.
6. How It Works
Namespace Creation Create and verify domain ownership to establish an identity namespace.
Registry Publication Add a registry to list beckn subscriber details.
Subscriber Record Creation Publish callback URL, roles, domain codes, and public keys.
Root Registry Inclusion Submit your registry URL to Beckn.One for inclusion in the global root.
Beckn ONIX Interaction Beckn ONIX automatically resolves subscriber details during network interactions.
7. Typical User Journey
Step 1 - Create & Verify Namespace
Prove domain ownership and establish your identity namespace.
Step 2 - Add a Registry
Publish a registry following the Beckn subscriber schema.
Step 3 - Add Subscriber Records
Include your callback URLs, roles, domain codes, and keys.
Step 4 - Add to Root Registry
Submit your registry link to Beckn.One for global recognition.
Step 5 - Transact through Beckn ONIX
Start participating in Beckn interactions with automatic address resolution and trust validation.
8. Glossary
Namespace: A verified identity space tied to an organization’s domain and used as the root of trust for publishing participant information..
Registry: A list of subscriber records under your namespace.
Subscriber Record: The specific values describing how a participant can be addressed and authenticated—such as URLs, roles, domain codes, and public keys.
Facilitator: An entity that curates and governs networks using Beckn standards.
Domain Code: Represents a domain like mobility, commerce, energy, or sustainability.
Beckn ONIX: An enterprise-grade middleware adapter that enables seamless communication in Beckn-enabled networks by handling routing, key retrieval, and validation.
DeDi Global: Infrastructure implementing the Decentralized Directory Protocol.
9. Get Started
📘 User Guide
Detailed user guide available here.
📝 Publish Your Registry
Submit your registry details to Beckn.One for inclusion in the root directory here.
💬 Need Help?
Raise a support ticket here.
Last updated