iAmPankajj
commented
1 year ago An added advantage is the transaction payload will get reduce and some PII data such as GST no, Bank account etc. need not be sent in transactions. All such data can be captured from the ONDC NP data message broadcast. Additionally ONDC may choose to expose API to fetch client data from Gateway Registry
For a ONDC Network Participant (NP) to execute a request/order from another eligible NP, the former needs to the know several information about the latter depending upon the request context. This includes several piece of client data that includes but is not limited to security data (such as public keys for authenticating signatures, encrypted data), financial related data (such as GST no, account no, addresses etc). Today some of these client data is fetched offline (such as cryptographic keys) and some other comes along with the (retail/logistic) order requests. In certain or most cases the receiving NP are constrained not to execute the client (sender NP) requests if the necessary client data is not present in its database. And if it is not already present the receiving NP has to dynamically onboard the client and then process the request. It may be desirable to receive a prospective client (NP) information prior to receiving any request/order from it. Thus proposing ONDC to setup a new protocol to disseminate NP information upon it's registration or change in information subsequently to all NPs. ONDC Gateway can broadcast the NP information to all other NPs who on their side can implement an API to process such messages and update their ONDC client records.