8000 ZATCA hashing issue for B2C Only · Issue #57 · wes4m/zatca-xml-js · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

ZATCA hashing issue for B2C Only #57

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
hamza-id opened this issue Jan 13, 2025 · 2 comments
Open

ZATCA hashing issue for B2C Only #57

hamza-id opened this issue Jan 13, 2025 · 2 comments

Comments

@hamza-id
Copy link

I recently implemented a taxation system in my application, and everything works perfectly in the development environment. As part of the process, I generated a certificate and moved on to test the simulation environment. i have successfully cleared the invoice for B2B but having issue only in B2B.

When I call the endpoint: https://gw-apic-gov.gazt.gov.sa/e-invoicing/simulation/compliance/invoices
this endpoint will give me that error. Could someone please guide or assist me with that

I encounter the following error:
"errorMessages": [ { "type": "ERROR", "code": "signed-properties-hashing", "category": "CERTIFICATE_ERRORS", "message": "Invalid signed properties hashing, SignedProperties with id='xadesSignedProperties'", "status": "ERROR" } ],

Here’s what I’ve done so far:

I generated the required certificate per ZATCA's guidelines.
Ensured the compliance XML payload was signed correctly using the generated certificate.
Verified that the request headers and payload adhere to the API specifications.

@mabaega
Copy link
mabaega commented Jan 14, 2025

@hamza-id
Copy link
Author

Thank you for pointing that out. However, this issue doesn't seem to be related to the URL change, as I have tested it on my end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0