You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: