Kindly be informed that after 24 of generating your CCSID, it will be revoked, The Only Use For the Compliance Check API is to ensure the compliance and you can’t use the compliance check API to validate your actual invoices after being onboarded successfully and received your PCSID
You can use ZATCA SDK to validate your invoices before sharing them through APIs.
Please find ZATCA SDK link ensure that you are installing the latest SDK version, Zatca
i am not able to onboard. after creating csid when i am hitting production/csids it is giving me 401. also on sandbox protal i am getting 401 after executing the api. Please check and let me know the steps to onboard successfully
To provide comprehensive support as usual, can I kindly ask you to mention the exact steps you followed to generate CCSID and what is the exact payload (body, header, and authorization ) when hitting /simulation/compliance/invoices API?
Thank you for the update and the detailed observation.
Could you please share more information on the technical reason behind this error? I’d like to understand what causes the issue when the compliance check is delayed and why regenerating the OTP and CSID resolves it.
This will help us ensure the process is optimized and prevent similar errors in the future.