Onboarding Staging Q&A #31
Replies: 154 comments 305 replies
-
|
Hi @92shreyansh , I have submitted our Subscriber ID, our stagging environments domain name for whitelisting purpose yesterday. As of now i have not got any notification regarding its whitelisting status on my mail. how will i know domain name is whitelisted or not. Can you please help me for the same. |
Beta Was this translation helpful? Give feedback.
-
|
the subsciber_id should be without |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @92shreyansh, Noted. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @92shreyansh , Could you please confirm our FQDN is whitelisted or not. |
Beta Was this translation helpful? Give feedback.
-
|
You would receive a email once it is whitelisted the may be some delay due to some technical challenges at our end |
Beta Was this translation helpful? Give feedback.
-
|
Hi @92shreyansh we got onbaorded for buyer and seller , now we would like to onboarded for credit buyer and seller . |
Beta Was this translation helpful? Give feedback.
-
|
Submit the form which is part of this doc We would update this soon in github |
Beta Was this translation helpful? Give feedback.
-
|
@92shreyansh submitted |
Beta Was this translation helpful? Give feedback.
-
|
Hi @92shreyansh we have submitted the google form to whitelist our Subscriber ID but we are yet to receive an update. Please help with the confirmation whether its done or not. |
Beta Was this translation helpful? Give feedback.
-
|
You would receive a email once it is whitelisted the may be some delay due to some technical challenges at our end |
Beta Was this translation helpful? Give feedback.
-
|
Hi @92shreyansh We have not received any update on the whitelisting of Subscriber ID after submission of the new Google form as well. |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I've a query. Let's say I register "xyz.com/abc" as my subscriberID, do I have an option to change the "abc" with "xyx"? FQDN xyz.com will remain same. |
Beta Was this translation helpful? Give feedback.
-
|
no In this case the subsciber_id will be xyz.com only for scenario in which you wish to receive the Transaction API call add "/abc" in the subsciber_url. Fundamentally a BAP & BPP would validate the bap_id, bap_url, bpp_id & bpp_url which come in context against the entry in the registry |
Beta Was this translation helpful? Give feedback.
-
|
Hi @92shreyansh , For the response of Search API , Acknowledgement has to be sent by Provider Platform to Consumer Platform Please clarify which values to be passed in "String" for parameters which are mentioned in sample Acknowledgement in Swagger UI, "message": { |
Beta Was this translation helpful? Give feedback.
-
|
The example actually contains no explicite example for ACK the stabdard payload is without tags |
Beta Was this translation helpful? Give feedback.
-
|
@92shreyansh , |
Beta Was this translation helpful? Give feedback.
-
|
@MahadevanAlagar1978 & @2316Meheraj is your issue resolved. Let know the souldtion here for the community as well |
Beta Was this translation helpful? Give feedback.
-
|
we are also getting the same domain verification error. How do we fix it? |
Beta Was this translation helpful? Give feedback.
-
|
@92shreyansh getting same issue for me as well. I have done the necessary changes. Can you please help me on here. { |
Beta Was this translation helpful? Give feedback.
-
|
Domain verification failed is fundamentally when the subsciber_id or ondc-site-verification.html is not aceesable, It may also occur in case your signature prrsent in ondc-site-verification.html is not verified with the public siging key and request_id passed in subscibe payload |
Beta Was this translation helpful? Give feedback.
-
|
Hi @92shreyansh , Can any one tell me How do we create the signature of request id. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
OSCP validation is facing for the provided domain i.e. https://iktaratech.com/. Registry is facing below error "unable to find valid certification path to requested target". Will analize and get back, mean time can you also provide details of the certificate available at this DNS as this issue is not faced by other NPs. Mostly the type of certificate or CA is the issue here. |
Beta Was this translation helpful? Give feedback.
-
|
I also encountered a similar issue. In my case, the problem was related to the CA certificate installed on the domain. The solution is that the certificate file (.crt) should also include the bundle key. |
Beta Was this translation helpful? Give feedback.
-
|
This issues is solved in my case by concatenating the root certificate with all intermediate certificate to make a bundle.crt and then using this certificate will fix the problem of oscp validation. |
Beta Was this translation helpful? Give feedback.
-
|
We are facing Domain verification is failed.. How we can do that please suggest us some solutions. |
Beta Was this translation helpful? Give feedback.
-
|
Domain verification failures would be a result to possibly 2 issue
|
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Can we take specification specific question in respective repos and keeps this for on boarding only. Request to move this discussion under FIS and delete the comment here once done, Thank you |
Beta Was this translation helpful? Give feedback.
-
|
Done |
Beta Was this translation helpful? Give feedback.
-
|
@92shreyansh the https://github.com/ONDC-Official/developer-docs/blob/main/registry/Onboarding%20of%20Participants.md the details only have pre-prod and prod "ONDC public keys".Can you update the staging ondc public keys as well |
Beta Was this translation helpful? Give feedback.
-
|
@jkritika20 It would be great if you can raise a doc update PR and update the details using this doc. Just mention these details as staging GCP to avoid confusion as we have 2 stagging 1 legacy stagging which is soon to be decommissioned. |
Beta Was this translation helpful? Give feedback.
-
|
@92shreyansh , |
Beta Was this translation helpful? Give feedback.
-
|
Thank you @92shreyansh for your help. |
Beta Was this translation helpful? Give feedback.
-
|
@2316Meheraj |
Beta Was this translation helpful? Give feedback.
-
|
@2316Meheraj |
Beta Was this translation helpful? Give feedback.
-
|
Please share the signing string format for search api. |
Beta Was this translation helpful? Give feedback.
-
|
Has anyone resolved this issue? If so, could you please assist with it? |
Beta Was this translation helpful? Give feedback.
-
|
Can you tell me how to sign the request id any code or example will help |
Beta Was this translation helpful? Give feedback.
-
|
Python utilities are available at the URL below, but I didn't use them. |
Beta Was this translation helpful? Give feedback.
-
|
Signature keyId="buyer-app.ondc.org|207|ed25519",algorithm="ed25519",created="1641287875",expires="1641291475",headers="(created) (expires) digest",signature="fKQWvXhln4UdyZdL87ViXQObdBme0dHnsclD2LvvnHoNxIgcvAwUZOmwAnH5QKi9Upg5tRaxpoGhCFGHD+d+Bw==" |
Beta Was this translation helpful? Give feedback.
-
|
@harsh-refo, I took a look at the URL https://ondc-official.github.io/developer-docs/org/ondc/crypto/util/package-summary.html. I could find the documentation but I'm not able to use the package as such. Would you be able to help me understand how can we use it? |
Beta Was this translation helpful? Give feedback.
-
|
Java source code is available at the following URL. |
Beta Was this translation helpful? Give feedback.
-
|
@harsh-refo, Thank you for the source code URL. This helps |
Beta Was this translation helpful? Give feedback.
-
|
we are constantly facing issues with nponbording This is the code for sending request to the server import requests |
Beta Was this translation helpful? Give feedback.
-
|
Rerefering you same comment above. Other NPs have also provided there resolutions there please check. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @92shreyansh |
Beta Was this translation helpful? Give feedback.
-
|
curl --location 'https://staging.registry.ondc.org/lookup' [ |
Beta Was this translation helpful? Give feedback.
-
|
Now it's giving the result with our details which means we are subscribed, now what is the next step? |
Beta Was this translation helpful? Give feedback.
-
|
i am getting the same issue while |
Beta Was this translation helpful? Give feedback.
-
|
function decryptAES256ECB(encrypted) { const privateKey1 = crypto.createPrivateKey({ const publicKey2 = crypto.createPublicKey({ const sharedKey12 = crypto.diffieHellman({ const iv = Buffer.alloc(0); // ECB doesn't use IV let decrypted = decipher.update(encrypted, 'base64', 'utf8'); logger.info('Decrypted crypto key:', decrypted); Please use this code. All the keys are everything is self-explanatory |
Beta Was this translation helpful? Give feedback.
-
|
@yashb042 Great its working thanks |
Beta Was this translation helpful? Give feedback.
-
|
Hi @92shreyansh , As discussed in Today meeting we have once again submitted our Public FQDN as Subscriber ID for whitelisting purpose, please whitelist it. @jhawar12 FYI |
Beta Was this translation helpful? Give feedback.
-
|
Hi @92shreyansh |
Beta Was this translation helpful? Give feedback.
-
|
message.entity.address_of_authorised Signatory: is not required., |
Beta Was this translation helpful? Give feedback.
-
|
@jhawar12 & @RahulSatanure is your issue resolved. Let know the souldtion here for the community as well |
Beta Was this translation helpful? Give feedback.
-
|
Hi @92shreyansh, |
Beta Was this translation helpful? Give feedback.
-
|
These is no issue in the endpoint can you please share more details of the response object if any. Also please move this thread to corresponding domain which you are trying for better reach and visibility |
Beta Was this translation helpful? Give feedback.
-
|
@jkritika20 is your issue resolved. Let know the souldtion here for the community as well |
Beta Was this translation helpful? Give feedback.
-
|
Hi Yash,
Kindly confirm if you are using correct key pairs apart from that have you
used ONDC Public Key as per the environment.
Also you can refer to :
https://docs.google.com/document/d/15Dpy02lqtcU9tslyMqaI4UtnD2rtwnjAbn1narO0364/edit?tab=t.0#heading=h.nfolgk6iryqx
Thank You
With Regards
Nishtha Monga
Software Engineer
…On Thu, 7 Nov 2024 at 14:17, Yash Bansal ***@***.***> wrote:
@92shreyansh <https://github.com/92shreyansh> @nitinmish
<https://github.com/nitinmish>
For preprod environment, I am trying to subscribe
This is my requestURL
https://preprod.registry.ondc.org/ondc/subscribe
This is my payload
{
"context": {
"operation": {
"ops_no": 1
}
},
"message": {
"entity": {
"address_of_authorised_signatory": "LP",
"callback_url": "/",
"country": "IND",
"email_id": ***@***.***",
"gst": {
"business_address": "1st Floor, T Tower, KM Compound, Mumbai 013.",
"city_code": [
"std:080"
],
"gst_no": "06AAHCP1178L1Z4",
"legal_entity_name": "FT PRIVATE LIMITED"
},
"key_pair": {
"encryption_public_key": "MCowBQYDK2VuAyEAIzPFKlFiwBBJ8auu0OMa4bzyf9Vgg0l2nvgfoAzcbX4=",
"signing_public_key": "HwiOqNAanJPNWO4J1zzvtjeT4WjyHW321pVEW0SHD4M=",
"valid_from": "2024-11-07T18:27:54.101Z",
"valid_until": "2040-07-08T06:27:54.101Z"
},
"mobile_no": 7792013965,
"name_of_authorised_signatory": "NSSS",
"pan": {
"date_of_incorporation": "05/01/2022",
"name_as_per_pan": "FT PRIVATE LIMITED",
"pan_no": "AAHCP1178L"
},
"subscriber_id": "rb-ondc-intracitybus-preprod.redbus.in",
"unique_key_id": "67baa06d-f90a-486c-85e5-cc621b743f11"
},
"network_participant": [
{
"city_code": [
"*"
],
"domain": "ONDC:TRV11",
"msn": false,
"subscriber_url": "/",
"type": "buyerApp"
}
],
"request_id": "67baa06d-f90a-486c-85e5-cc621b743f58",
"timestamp": "2024-11-07T08:43:32.001Z"
}
}","time":"2024-11-07T08:43:32Z"}
Could you please help
I am not getting on_subscribe callback.
The ondc-site-verification.html is being called and my service is
returning a response to that.
I am getting the following error in the subscribe request
"message": "https://rb-ondc-intracitybus-preprod.redbus.in/on_subscribe :
Encryption verification is failed"
—
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BD3YNKYFW6UQ327W7ZFFTKLZ7MSIJAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCMJXGUYTIMA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Yes, I have used the correct key pairs, I have done it for 2 different domains and I am using the same code so it shouldn't be a problem |
Beta Was this translation helpful? Give feedback.
-
|
Subscribe Request Logs Server Logs |
Beta Was this translation helpful? Give feedback.
-
|
Hi Shreyansh, I am unable to understand why is domain verification still failing. Can you please help? |
Beta Was this translation helpful? Give feedback.
-
|
@92shreyansh can you please hint if this is an issue on our end or not? |
Beta Was this translation helpful? Give feedback.
-
|
I am unable to reach the domain URL which probably what’s failing. Please check.
<https://staging-api.transitpal.io/>
staging-api.transitpal.io<https://staging-api.transitpal.io/>
[X]<https://staging-api.transitpal.io/>
…Sent from my iPhone
On 31 Mar 2025, at 8:17 PM, Atul ***@***.***> wrote:
Subscribe Request Logs
=== Subscribe Request Logs ===
Generated signature: qlTqrxih23C1w3k+jAbG3kCxYn8V4CEkd//GOwjHQiwDn/MXLl8bLSSatYIR4lDzfEyeJy/v5984DomVCSS2Bg==
=== Setting Signature in Cache ===
Signature: qlTqrxih23C1w3k+jAbG3kCxYn8V4CEkd//GOwjHQiwDn/MXLl8bLSSatYIR4lDzfEyeJy/v5984DomVCSS2Bg==
Timestamp: 2025-03-31T14:42:09.976Z
Submitting subscribe request to https://staging.registry.ondc.org/subscribe...
Payload: {"context":{"operation":{"ops_no":1}},"message":{"request_id":"3fec67e4-3cb6-4d0b-98cd-259e2f2c4cc6","timestamp":"2025-03-31T14:42:09.968Z","entity":{"gst":{"legal_entity_name":"DUMMY","business_address":"DUMMY","city_code":["std:011"],"gst_no":"DUMMY"},"pan":{"name_as_per_pan":"DUMMY","pan_no":"DUMMY","date_of_incorporation":"DUMMY"},"name_of_authorised_signatory":"DUMMY","address_of_authorised_signatory":"DUMMY","email_id":"DUMMY","mobile_no":"DUMMY","country":"IND","subscriber_id":"staging-api.transitpal.io","unique_key_id":"3fec67e4-3cb6-4d0b-98cd-259e2f2c4cc6","callback_url":"/api/ondc","key_pair":{"signing_public_key":"MCowBQYDK2VwAyEAlyNrpEolBW9PBDEIMJYBpNOxmppxwbZd70OzzQ5slo4=","encryption_public_key":"MCowBQYDK2VuAyEAj7f+U8JPVr8sCynuq3pOVzTXZ/vhOi0XkgAsLaOqcE8=","valid_from":"2025-03-31T14:42:09.968Z","valid_until":"2026-03-31T14:42:09.977Z"}},"network_participant":[{"subscriber_url":"/","domain":"ONDC:TRV11","type":"buyerApp","msn":false,"city_code":["std:011"]}]}}
Request ID used for signature: 3fec67e4-3cb6-4d0b-98cd-259e2f2c4cc6
Generated Signature: qlTqrxih23C1w3k+jAbG3kCxYn8V4CEkd//GOwjHQiwDn/MXLl8bLSSatYIR4lDzfEyeJy/v5984DomVCSS2Bg==
Response: {"message":{"ack":{"status":"NACK"}},"error":{"type":"DOMAIN-ERROR","code":"129","path":null,"message":"https://staging-api.transitpal.io : Domain verification is failed "}}
Server Logs
=== Domain Verification Request Logs ===
Headers: {"x-forwarded-for":"35.200.232.136","x-forwarded-proto":"https","x-forwarded-port":"443","host":"staging-api.transitpal.io","x-amzn-trace-id":"Root=1-67eaa9c2-7237804152c951a4655162c7","user-agent":"Java/11.0.18","accept":"text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2"}
Body: {}
=== Getting Signature from Cache ===
Signature: qlTqrxih23C1w3k+jAbG3kCxYn8V4CEkd//GOwjHQiwDn/MXLl8bLSSatYIR4lDzfEyeJy/v5984DomVCSS2Bg==
Timestamp: 2025-03-31T14:42:10.055Z
=== Generated HTML ===
<!DOCTYPE html>
<html>
<head>
<title>ONDC Site Verification</title>
<meta name="ondc-site-verification" content="qlTqrxih23C1w3k+jAbG3kCxYn8V4CEkd//GOwjHQiwDn/MXLl8bLSSatYIR4lDzfEyeJy/v5984DomVCSS2Bg==" />
</head>
<body>
<h1>ONDC Site Verification</h1>
<p>This is a verification file for ONDC domain ownership.</p>
</body>
</html>
@92shreyansh<https://github.com/92shreyansh>
—
Reply to this email directly, view it on GitHub<#31 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AE3TNSBFE5MPHZ6AIMTXG2T2XFIO3AVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRXG42TKMY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for prompt reply. I added the homepage, still the same issue @nitinmish |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
Thank you for reaching out to us.
+ @sharique Zafar ***@***.***> ,Could you kindly provide your
assistance with this matter at your earliest convenience?
…On Tue, 1 Apr 2025 at 11:25, Atul ***@***.***> wrote:
@92shreyansh <https://github.com/92shreyansh> can you please hint if this
is an issue on our end or not?
—
Reply to this email directly, view it on GitHub
<#31 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEO4U6Z4EBOC7EIRYPZDLXD2XIS6HAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRYGQYTINQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Atul,
Could you please let me know what your query is?
Best Regards
Sharique Zafar
Software Engineer
…On Tue, 1 Apr 2025 at 11:39, Tech Support ***@***.***> wrote:
Hi,
Thank you for reaching out to us.
+ @sharique Zafar ***@***.***> ,Could you kindly provide your
assistance with this matter at your earliest convenience?
On Tue, 1 Apr 2025 at 11:25, Atul ***@***.***> wrote:
> @92shreyansh <https://github.com/92shreyansh> can you please hint if
> this is an issue on our end or not?
>
> —
> Reply to this email directly, view it on GitHub
> <#31 (reply in thread)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BEO4U6Z4EBOC7EIRYPZDLXD2XIS6HAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRYGQYTINQ>
> .
> You are receiving this because you were mentioned.Message ID:
> <ONDC-Official/developer-docs/repo-discussions/31/comments/12684146@
> github.com>
>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi, thanks for reply. I am getting following error while subscribing to ONDC staging environment. |
Beta Was this translation helpful? Give feedback.
-
|
Hi Atul,
*Resolution:-*
Utilize Plain Request_ID: Network Participants are advised to use the
request_id as is, without applying any hashing, when generating the
signature. Maintain Consistent Request_ID: Network Participants should
ensure the request_id in the request body matches the one used during
signature generation to guarantee successful validation. Verify Signing
Public Key: Network Participants should include the same signing public key
in the request body that corresponds to the signing private key used during
the signing process.
Best Regards
Sharique Zafar
Software Engineer
…On Tue, 1 Apr 2025 at 11:55, Sharique Zafar ***@***.***> wrote:
Hi Atul,
Could you please let me know what your query is?
Best Regards
Sharique Zafar
Software Engineer
On Tue, 1 Apr 2025 at 11:39, Tech Support ***@***.***> wrote:
>
> Hi,
> Thank you for reaching out to us.
> + @sharique Zafar ***@***.***> ,Could you kindly provide your
> assistance with this matter at your earliest convenience?
>
>
>
>
>
> On Tue, 1 Apr 2025 at 11:25, Atul ***@***.***> wrote:
>
>> @92shreyansh <https://github.com/92shreyansh> can you please hint if
>> this is an issue on our end or not?
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#31 (reply in thread)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/BEO4U6Z4EBOC7EIRYPZDLXD2XIS6HAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRYGQYTINQ>
>> .
>> You are receiving this because you were mentioned.Message ID:
>> <ONDC-Official/developer-docs/repo-discussions/31/comments/12684146@
>> github.com>
>>
>
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Atul,
Did you have a chance to look at following link:
https://github.com/ONDC-Official/developer-docs/blob/main/registry/Onboarding%20of%20Participants.md
[https://opengraph.githubassets.com/cdc6a63480eb5c78d7288695bc06b12c076a9e76ef1b634b6fe384a04a4b1a49/ONDC-Official/developer-docs]<https://github.com/ONDC-Official/developer-docs/blob/main/registry/Onboarding%20of%20Participants.md>
developer-docs/registry/Onboarding of Participants.md at main · ONDC-Official/developer-docs - GitHub<https://github.com/ONDC-Official/developer-docs/blob/main/registry/Onboarding%20of%20Participants.md>
SSL Certificate: Obtain a valid SSL certificate for your domain.This certificate is used for Online Certificate Status Protocol (OCSP) validation. Whitelisting: Get approval for your Staging, Pre-Production, and Production subscriber_id by submitting a request on the Network Participant Portal:. Sign up on the Network Participant Portal here and submit your request.
github.com
Please see Step 5 specifically. It seems you are returning JSON from the link, where as the expectation is an html from site-verification URL.
Regards,
Nitin
________________________________
From: TechSupportONDC ***@***.***>
Sent: 01 April 2025 12:14
To: ONDC-Official/developer-docs ***@***.***>
Cc: nitinmish ***@***.***>; Mention ***@***.***>
Subject: Re: [ONDC-Official/developer-docs] Onboarding Staging Q&A (Discussion #31)
Hi Atul,
*Resolution:-*
Utilize Plain Request_ID: Network Participants are advised to use the
request_id as is, without applying any hashing, when generating the
signature. Maintain Consistent Request_ID: Network Participants should
ensure the request_id in the request body matches the one used during
signature generation to guarantee successful validation. Verify Signing
Public Key: Network Participants should include the same signing public key
in the request body that corresponds to the signing private key used during
the signing process.
Best Regards
Sharique Zafar
Software Engineer
On Tue, 1 Apr 2025 at 11:55, Sharique Zafar ***@***.***> wrote:
Hi Atul,
Could you please let me know what your query is?
Best Regards
Sharique Zafar
Software Engineer
On Tue, 1 Apr 2025 at 11:39, Tech Support ***@***.***> wrote:
>
> Hi,
> Thank you for reaching out to us.
> + @sharique Zafar ***@***.***> ,Could you kindly provide your
> assistance with this matter at your earliest convenience?
>
>
>
>
>
> On Tue, 1 Apr 2025 at 11:25, Atul ***@***.***> wrote:
>
>> @92shreyansh <https://github.com/92shreyansh> can you please hint if
>> this is an issue on our end or not?
>>
>> —
>> Reply to this email directly, view it on GitHub
>> <#31 (reply in thread)>,
>> or unsubscribe
>> <https://github.com/notifications/unsubscribe-auth/BEO4U6Z4EBOC7EIRYPZDLXD2XIS6HAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRYGQYTINQ>
>> .
>> You are receiving this because you were mentioned.Message ID:
>> <ONDC-Official/developer-docs/repo-discussions/31/comments/12684146@
>> github.com>
>>
>
—
Reply to this email directly, view it on GitHub<#31 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AE3TNSEY2XDFGBAD3YPM2ST2XIYVZAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRYGQ3DGMY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
I am attaching more information for your team to help me.
please help, we can get on a 10min gmeet call to resolve this p.s. i am not trying on pre-prod environment rather than staging, still same issue |
Beta Was this translation helpful? Give feedback.
-
|
The subscriber ID and the URL mentioned below are different. Registry looks at Subscriber ID and reference URL.
You are passing"subscriber_id":"staging-api.transitpal.io" where as the HTML is hosted at https://pre-prod-api.transitpal.io/ondc-site-verification.html
Please send out correct Subscriber ID and see if it works.
If not, will request someone from tech support team to help you.
Regards,
Nitin
…________________________________
From: Atul ***@***.***>
Sent: 01 April 2025 12:33
To: ONDC-Official/developer-docs ***@***.***>
Cc: nitinmish ***@***.***>; Mention ***@***.***>
Subject: Re: [ONDC-Official/developer-docs] Onboarding Staging Q&A (Discussion #31)
I am attaching more information for your team to help me.
* the output of the -- https://pre-prod-api.transitpal.io/ondc-site-verification.html (which seems to be HTML only)
* the signatures are also same in both html and subscribe payload
* i have gone through the above resources thoroughly, possible I am missing some small point, but couldn't point to it
please help, we can get on a 10min gmeet call to resolve this
p.s. i am not trying on pre-prod environment rather than staging, still same issue
—
Reply to this email directly, view it on GitHub<#31 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AE3TNSH74NRBPDEN3QZEED32XI22VAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRYGQ3TONY>.
You are receiving this because you were mentioned.
|
Beta Was this translation helpful? Give feedback.
-
|
The previous payload was from earlier attempt. Here are the latest logs for you reference, we are sending same pre-prod subscriber id |
Beta Was this translation helpful? Give feedback.
-
|
@TechSupportONDC please check if the signing of Unique_req_Id is being done correctly. Please have a word with @atul-kiwimesh and help him subscribe. The Pre-Prod key is: "MCowBQYDK2VuAyEAa9Wbpvd9SsrpOZFcynyt/TO3x0Yrqyys4NUGIvyxX2Q=" |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Can you try once again @atul-kiwimesh ? Seems your URL was not working till 12:25 PM. Its working now. |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
Lets connect at 1:15 PM to resolve the issue.
Re: [ONDC-Official/developer-docs] Onboarding Staging Q&A (Discussion #31)
Tuesday, 1 April · 1:15 – 2:15pm
Time zone: Asia/Kolkata
Google Meet joining info
Video call link: https://meet.google.com/bbt-pfez-tfu
Or dial: (US) +1 402-921-2198 PIN: 136 234 365#
More phone numbers: https://tel.meet/bbt-pfez-tfu?pin=9862551396869
Re: [ONDC-Official/developer-docs] Onboarding Staging Q&A (Discussion #31)
1 Apr 2025, 1:15pm – 1 Apr 2025, 2:15pm
(GMT+05:30) India Standard Time - Kolkata
…On Tue, 1 Apr 2025 at 12:49, nitinmish ***@***.***> wrote:
@TechSupportONDC <https://github.com/TechSupportONDC> please check if the
signing of Unique_req_Id is being done correctly. Please have a word with
@atul-kiwimesh <https://github.com/atul-kiwimesh> and help him subscribe.
The Pre-Prod key is:
"MCowBQYDK2VuAyEAa9Wbpvd9SsrpOZFcynyt/TO3x0Yrqyys4NUGIvyxX2Q="
—
Reply to this email directly, view it on GitHub
<#31 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BEO4U63IPRIP5JPQOVBRAGL2XI4YFAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRYGQ4TINA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
thanks sharique and nitin, it was resolve |
Beta Was this translation helpful? Give feedback.
-
|
@TechSupportONDC , please document the help here so that we have a record and a reference for others to help themselves. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Hi Atul,
Now that we've resolved the issue over the call, I'll close this thread. If
you need any further assistance, please feel free to start a new thread.
Best Regards
Sharique Zafar
Software Engineer
…On Tue, 1 Apr 2025 at 12:13, Sharique Zafar ***@***.***> wrote:
Hi Atul,
*Resolution:-*
Utilize Plain Request_ID: Network Participants are advised to use the
request_id as is, without applying any hashing, when generating the
signature. Maintain Consistent Request_ID: Network Participants should
ensure the request_id in the request body matches the one used during
signature generation to guarantee successful validation. Verify Signing
Public Key: Network Participants should include the same signing public key
in the request body that corresponds to the signing private key used during
the signing process.
Best Regards
Sharique Zafar
Software Engineer
On Tue, 1 Apr 2025 at 11:55, Sharique Zafar ***@***.***> wrote:
> Hi Atul,
>
> Could you please let me know what your query is?
>
> Best Regards
> Sharique Zafar
> Software Engineer
>
>
> On Tue, 1 Apr 2025 at 11:39, Tech Support ***@***.***> wrote:
>
>>
>> Hi,
>> Thank you for reaching out to us.
>> + @sharique Zafar ***@***.***> ,Could you kindly provide your
>> assistance with this matter at your earliest convenience?
>>
>>
>>
>>
>>
>> On Tue, 1 Apr 2025 at 11:25, Atul ***@***.***> wrote:
>>
>>> @92shreyansh <https://github.com/92shreyansh> can you please hint if
>>> this is an issue on our end or not?
>>>
>>> —
>>> Reply to this email directly, view it on GitHub
>>> <#31 (reply in thread)>,
>>> or unsubscribe
>>> <https://github.com/notifications/unsubscribe-auth/BEO4U6Z4EBOC7EIRYPZDLXD2XIS6HAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRYGQYTINQ>
>>> .
>>> You are receiving this because you were mentioned.Message ID:
>>> <ONDC-Official/developer-docs/repo-discussions/31/comments/12684146@
>>> github.com>
>>>
>>
|
Beta Was this translation helpful? Give feedback.
-
|
Just curious, you own Signature Generator should have generated ED25519 keys. Was it generating something else?
Regards,
Nitin
…________________________________
From: Atul ***@***.***>
Sent: 01 April 2025 14:40
To: ONDC-Official/developer-docs ***@***.***>
Cc: nitinmish ***@***.***>; Mention ***@***.***>
Subject: Re: [ONDC-Official/developer-docs] Onboarding Staging Q&A (Discussion #31)
1. I was using my own signature generator instead of the one in the utility repo<https://github.com/ONDC-Official/reference-implementations/tree/main/utilities/signing_and_verification>
2. I did not have the public keys for ondc environment
—
Reply to this email directly, view it on GitHub<#31 (reply in thread)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AE3TNSFYC3WFL4VPCQVVFFD2XJJZXAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTENRYGYYTGMY>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
We are encountering an issue while attempting to subscribe using the following subscriber ID: staging-xcellntapps-buyer.sumasoft.com Despite having whitelisted this ID for all domains, we are receiving the following error response: { Could you please guide us on resolving this issue? Is there any additional configuration or step required to complete the subscription process? Looking forward to your assistance. |
Beta Was this translation helpful? Give feedback.
-
|
What is the format of date for date_of_incorporation for PAN please? I have tried every date format I could think of. Nothing is working. Please help. |
Beta Was this translation helpful? Give feedback.
-
|
Kindly share your CURL command for subscribe API to debug further.
[image: photo]
*Warm RegardsNishtha MongaSoftware Engineer*
*Need help fast?* Chat with Buddy, your ONDC assistant → buddy.ondc.org
🔗 Explore our GitHub Repository: github.com/ONDC-Official
📅 Join our Community Calls: View schedule and details
<https://docs.google.com/document/d/1z4lsWi-04HNqhSKf4jDLfi7cvt4NgyZ-BfEtqOW2VwY/>
📨 Contact us: ***@***.***
*Submit Your Cloud Credits Request Click here
<https://docs.google.com/forms/d/e/1FAIpQLSdQPANjGTUVIRM7dKvukt7tzEswR091jCYM9AuHpMwmx0XOng/viewform>*
…On Wed, 11 Jun 2025 at 19:30, ramsabi ***@***.***> wrote:
What is the format of date for date_of_incorporation for PAN please?
My PAN has been entered in ONDC and verified. I am giving the identical
details for registering in the staging environment:
"pan": {
"name_as_per_pan": "First Name Last Name",
"pan_no": "Correct Number",
"date_of_incorporation": "DD/MM/YYYY"
},
I get the following error:
Status Code: 200
Response:
{"message":{"ack":{"status":"NACK"}},"error":{"type":"JSON-SCHEMA-ERROR","code":"124","path":null,"message":"Please
provide valid Pan date_of_incorporation"}}
I have tried every date format I could think of. Nothing is working.
Please help.
—
Reply to this email directly, view it on GitHub
<#31 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BD3YNK4FG3RU5WFSZY5KDRL3DAY7XAVCNFSM6AAAAAA4CZDQZGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGNBTGM4DCNA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Sorted out thank you. |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi All,
Please use this discussion board to add comments regarding any staging onboarding questions.
This is for the staging with staging URL is https://staging.registry.ondc.org
For the process to onboard refer the doc, Will update the github soon
For resolving queries please feel free to join Open Hours call that is daily
ONDC Registry Onboarding (Subscribe API) Walkthrough
Friday, 8 December · 10:00 – 10:45am
Time zone: Asia/Kolkata
Google Meet joining info
Video call link: https://meet.google.com/qjs-xupv-zdk
Or dial: (US) +1 704-248-7520 PIN: 766 903 209#
More phone numbers: https://tel.meet/qjs-xupv-zdk?pin=4108409403601
Beta Was this translation helpful? Give feedback.
All reactions