# X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) **URL:** \ **Category:** General\ **Created:** [September 9, 2025, 3:14pm UTC](https://zatca1.discourse.group/t/x509certificate-ccsid-pcsid-used-for-signing-is-not-valid-certificate-ccsid-pcsid/8374 "2025-09-09T15:14:52Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![mohamedshamoon](https://avatars.discourse-cdn.com/v4/letter/m/f14d63/32.png) [@mohamedshamoon](https://zatca1.discourse.group/u/mohamedshamoon)\ **Post date:** [September 9, 2025, 3:14pm UTC](https://zatca1.discourse.group/t/x509certificate-ccsid-pcsid-used-for-signing-is-not-valid-certificate-ccsid-pcsid/8374/1 "2025-09-09T15:14:52Z")
We’re facing this error during the onboarding of new devices, this issue started happening after the release of the latest SDK: We’ve updated the SDK to version **SDK Version 3.4.4** We get the certificate using this endpoint: **POST/compliance** and it works fine We start sending the latest samples to **POST/compliance/invoices** and the issue happens as follows: Standard\_Invoice.xml **Pass** Standard\_Credit\_Note.xml **Pass** Standard\_Debit\_Note.xml **Pass** Simplified\_Invoice.xml **Error** Simplified\_Credit\_Note.xml **Error** Simplified\_Debit\_Note.xml **Error** Error Message: ```auto { "status_code": 500, "error_message": "Error, PostComplianceInvoicesAPI : General Error : {\"validationResults\":{\"infoMessages\":[{\"type\":\"INFO\",\"code\":\"XSD_ZATCA_VALID\",\"category\":\"XSD validation\",\"message\":\"Complied with UBL 2.1 standards in line with ZATCA specifications\",\"status\":\"PASS\"}],\"warningMessages\":[{\"type\":\"WARNING\",\"code\":\"invalid-signing-certificate\",\"category\":\"CERTIFICATE_ERRORS\",\"message\":\"X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.\",\"status\":\"WARNING\"}],\"errorMessages\":[],\"status\":\"WARNING\"},\"reportingStatus\":\"REPORTED\",\"clearanceStatus\":null,\"qrSellertStatus\":null,\"qrBuyertStatus\":null}" } ``` Any idea what is the issue? and how can we fix it? ---
**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\ **Post date:** [September 9, 2025, 3:23pm UTC](https://zatca1.discourse.group/t/x509certificate-ccsid-pcsid-used-for-signing-is-not-valid-certificate-ccsid-pcsid/8374/2 "2025-09-09T15:23:55Z")
Dear @mohamedshamoon Thanks for reaching out, To provide comprehensive support as usual, Can you please share the exact HTTP response from ZATCA? Thanks, Ibrahem Daoud. ---
**Author:** ![mohamedshamoon](https://avatars.discourse-cdn.com/v4/letter/m/f14d63/32.png) [@mohamedshamoon](https://zatca1.discourse.group/u/mohamedshamoon)\ **Post date:** [September 10, 2025, 12:48pm UTC](https://zatca1.discourse.group/t/x509certificate-ccsid-pcsid-used-for-signing-is-not-valid-certificate-ccsid-pcsid/8374/3 "2025-09-10T12:48:00Z")
“status\_code”: 202 ```auto { "validationResults": { "infoMessages": [ { "type": "INFO", "code": "XSD_ZATCA_VALID", "category": "XSD validation", "message": "Complied with UBL 2.1 standards in line with ZATCA specifications", "status": "PASS" } ], "warningMessages": [ { "type": "WARNING", "code": "invalid-signing-certificate", "category": "CERTIFICATE_ERRORS", "message": "X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.", "status": "WARNING" } ], "errorMessages": [], "status": "WARNING" }, "reportingStatus": "REPORTED", "clearanceStatus": null, "qrSellertStatus": null, "qrBuyertStatus": null } ``` ---
**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\ **Post date:** [September 10, 2025, 1:57pm UTC](https://zatca1.discourse.group/t/x509certificate-ccsid-pcsid-used-for-signing-is-not-valid-certificate-ccsid-pcsid/8374/4 "2025-09-10T13:57:13Z")
Dear @mohamedshamoon Thanks for your collaboration, can I kindly ask you to check and confirm if you are signing the B2C invoices with the CCSID Decoded based64 “Binary Security Token” that you received from the compliance? Thanks, Ibrahem Daoud. ---
**Author:** ![mohamedshamoon](https://avatars.discourse-cdn.com/v4/letter/m/f14d63/32.png) [@mohamedshamoon](https://zatca1.discourse.group/u/mohamedshamoon)\ **Post date:** [September 10, 2025, 2:32pm UTC](https://zatca1.discourse.group/t/x509certificate-ccsid-pcsid-used-for-signing-is-not-valid-certificate-ccsid-pcsid/8374/5 "2025-09-10T14:32:40Z")
Yes, we sign them with the CSID we received from [https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/compliance](https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/compliance) I have sent the 6 XMLs to **sp\_support@zatca.gov.sa** for you to check. they are all having the same certificate. ---
**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\ **Post date:** [September 11, 2025, 6:04am UTC](https://zatca1.discourse.group/t/x509certificate-ccsid-pcsid-used-for-signing-is-not-valid-certificate-ccsid-pcsid/8374/6 "2025-09-11T06:04:19Z")
Dear @mohamedshamoon Thanks for your collaboration in raising this, please note that it’s a known issue, currently our team working on it, However, you can complete the onboarding process and receive your PCSID successfully. Appreciate your understanding. Thanks, Ibrahem Daoud. ---
**Author:** ![Hari](https://avatars.discourse-cdn.com/v4/letter/h/cdc98d/32.png) [@Hari](https://zatca1.discourse.group/u/Hari)\ **Post date:** [September 17, 2025, 7:45am UTC](https://zatca1.discourse.group/t/x509certificate-ccsid-pcsid-used-for-signing-is-not-valid-certificate-ccsid-pcsid/8374/7 "2025-09-17T07:45:04Z")
Dear @idaoud @mohamedshamoon ‘warningMessages’: [{‘type’: ‘WARNING’, ‘code’: ‘invalid-signing-certificate’, ‘category’: ‘CERTIFICATE\_ERRORS’, ‘message’: ‘X509Certificate (CCSID / PCSID) used for signing is not valid certificate (CCSID / PCSID) for this VAT Registration Number.’, ‘status’: ‘WARNING’}] Any update on the mentioned Issue we are also currently facing this same problem now . and is it ok to onboard the device and Report Simplified Invoices with this existing warning messages ?