Switching onboarding paths

Move an NFO or NP between the hosted (dedi.global) path and the file-based path without leaving the NFH fabric.

An entity may adopt either of the two onboarding paths onto the NFH fabric, and may switch between them at any time. An entity (NFO or NP) cannot simultaneously use the hosted (dedi.global) and file-based paths for any write operations — so a switch always ends with exactly one active write path.

In both directions, you first establish your presence on the new path, then remove it from the old one.

Moving from dedi.global to file-based

There is a one-time delay of about 15 minutes while the switch takes effect.

1. Publish your DeDi index file and the corresponding registry on your own domain, as described in File-based onboarding — a Beckn Subscriber registry if you are an NP, a Beckn Subscriber Reference registry if you are an NFO.
2. Log in to publish.dedi.global, click on your namespace card, select View TXT, and remove the verification.

Your registry URL changes form when you switch — from api.dedi.global/dedi/lookup/<domain>/<registry-name> to <domain>/dedi/<registry-name> (see Registry URL forms). If you are an NP, share the new URL with your NFO so it can update its reference record in the network registry.

Moving from file-based to dedi.global

1. Log in at dedi.global and set up your namespace and directories as described in Hosted onboarding.
2. Complete the DNS TXT verification.
3. Remove the DeDi files from your domain.

The same applies in this direction: your registry URL changes to the hosted lookup form, so if you are an NP, share the new lookup URL with your NFO.