Thanks for reaching out, and welcome in our community.
Please provide the following details to ensure a comprehensive support as usual:
1- Which environment you are currently using?
2- Are you using our SDK or your tools?
3- Have you onboarded successfully and generate the PCSID?
Meanwhile, check the common errors related to the signing process during the onboarding process exactly during the compliance checks API, for production environment using .net SDK:
1- After generating the CCSID from the compliance API the response will contain
(BinarySecurityToken and Secret), you will use the BinarySecurityToken as the
userName in authentication for (compliance checks API), and the Secret will be the
Password.
2- Before sending any B2C invoice to be checked ensure to decode the
BinarySecurityToken using Base64 and put the decoded BinarySecurityToken to the
cert.pem fie following bath inside the SDK (zatca-einvoicing-sdk-238-
R3.3.3\Data\Certificates).
3- After that use the command for signing the invoice using your CCSID, you already
update it in the authorization (fatooranet sign -invoice “invoiceName.xml”).
After doing these steps you can fix the error that you provided.
I hope it’s clear now.
For any further support don’t hesitate to send a detailed information about your concerns to the SP email.
Kindly if you are still facing an issue provide all of the details to ensure a comprehensive support.
What is exactly the issue you are facing?
Which environment you are using?
Are you using ZATCA SDK or your own tools?
Have you onboarded successfully and generate the PCSID?
Please Share via
sp_support@zatca.gov.sa
E-invoicing@zatca.gov.sa