Publishing Subscriber Details

Dedi.global is a ready to use SaaS implementing the open DeDi protocol offered by the Network for Humanity Foundation. This allows registrars to effortlessly publish and manage their directories (aka public registries) on a robust decentralized infrastructure.

A namespace corresponds to a domain (and implicitly its organisation), serving as the starting point for trust. Think of it as the digital “root” under which all directories and records for that organization live.

For transacting in beckn.one you must create a namespace to add registries to store your subscription details and make yourself discoverable.

Step 0 : Whitelist your domain in DeDi

  1. Visit DeDi.Global and click on Support.

  2. Fill out the support form with your details.

  3. In the subject field, provide the subject as “Domain whitelisting request”.

  4. Specify the environment in which the domain should be whitelisted — Test or Production.

  5. After the request is processed, you will receive an email confirming that your domain has been successfully whitelisted.

Step 1: Login to DeDi.Global

  1. Users can register using (any) email to create a namespace.

    • By default users have access to create multiple namespaces, and registries, and records within. Users can create multiple namespaces (similar to how they can own multiple domains).

  2. Click on the register button on

  3. Enter your name and email address to receive an authentication link.

Step 2: Create Namespace and verify domain

  1. Create Namespace (Provide Name, Description)

    1. Name - Ideally your organisation name

    2. Description - Short description of your organisation

  2. Namespace should be linked to a domain to give it a “verified” status and make its contents accessible by the public.

  3. Before being verified currently the domain should be whitelisted by the DeDi team.

  4. The following steps should be followed to verify a namespace -

    1. Enter domain name. If the domain name is part of DeDi Global’s “list of allowed domains”, a TXT record will be generated.

    2. Copy the generated TXT record as it needs to be updated in the DNS configuration file of your domain.

    3. Click “Verify” after you have successfully updated the domain’s DNS file.

Step 3: Create Registry

A directory or registry is a list of records with a configurable schema, essentially the structured container of public information (like a registry of network participants or sanctioned entities) that sits under a namespace. The terms directory and registry are to be understood as equivalent and may be used interchangeably.

  1. Click on the namespace that was created.

  2. Click on Create Registry.

  3. Provide a name for the registry. This can be any string. (example: subscription-details)

  4. Provide a description of the registry. This can be any description. (example: Registry for beckn subscription details)

  5. Select a schema from the list of available schemas:

    • If you are a network participant select Beckn Subscriber.

    • If you are a facilitator creating a collection of network participants select Beckn Subscriber Reference.

Step 4: Add subscription details (For NPs)

  1. Click on the registry that was created.

  2. Click on Add Record.

  3. Provide a record name. This can be any string. (example: ev-charging-bap)

  4. Provide a description. This can be any string. (example: This record holds the subscription details of the EV charging BAP)

  5. Enter the following subscription details:

    • subscriber_id - A globally unique identifier of the platform this entry is referencing, typically it is the fully qualified domain name (FQDN) of the platform. (example: ev-charging.sandbox1.com)

    • url - Specifies the callback URL of the subscriber. It must share the same domain as subscriber_id.

    • type - Type of role played in the network

      • BAP - Beckn Application Platforms

      • BPP - Beckn Provider Platforms

      • CDS - Catalog Discovery Services

    • domain - Code of the operating industry domain that this subscriber offers its products or services in. (example: beckn.one:deg:ev-charging:2.0.0)

    • countries - Countries where the subscriber operates, provides services, or conducts business.

    • signing_public_key - The signing public key of the subscriber. Users can use the key generation utility on ONIX to create the key.

    • encr_public_key - The encryption public key of the subscriber. If the user is not implementing encryption, this field can be ignored.

  6. Once created, click on the new record. You would be able to see the record ID for the newly created record. This is to be used as the key_id which you would configure in ONIX.

Step 4: Add subscription references (For facilitators)

  1. Click on the registry that was created.

  2. Click on Add Record.

  3. Provide a record name. This can be any string. (example: example-np-details)

  4. Provide a description. This can be any string. (example: This record holds the subscription details example-np)

  5. Provide a description. This can be any string. (example: This record holds the reference to the subscription details of example np)

  6. Enter the following subscription details:

  • subscriber_id - Subscriber ID of the NP

  • url - Lookup URL of the registry/record created by the NP. Please refer to the section below to verify if the URL is correct.

  • type - Whether the entry references a record or a registry created by the NP. If the facilitator only wants to add a single record from the NP in their list, select record. If the facilitator wants to add the whole registry created by NP in their list select registry. If option registry is selected, it is equivalent to all the records in the registry being added to their list.

Validating and creating URL (can be delegated to NPs):

  1. Get the following details from the NP:

    • Verified Domain

    • Registry Name

    • Record ID (If type is record)

  2. Create the following URL

    • For type = Record

      • If environment is PROD

        • https://api.dedi.global/dedi/lookup/<verified-doman>/<registry-name>/<record-name>

      • If environment is TESTNET

        • https://test.dedi.global/dedi/lookup/<verified-doman>/<registry-name>/<record-name>

    • For type = Registry

      • If environment is PROD

        • https://api.dedi.global/dedi/lookup/<verified-doman>/<registry-name>

      • If environment is TESTNET

        • https://test.dedi.global/dedi/lookup/<verified-doman>/<registry-name>

  3. Log in to DeDi.Global

  4. Open a new tab in the same browser

  5. Paste the URL constructed in step 2

  6. If there are no issues, you will see the registry/record details with the message “Resource retrieved successfully”

Step 5: Share details to be added to beckn one root registry

Open the form and add details as per the instructions here.

Video demo

PreviousProduct Note

Last updated