Error vs Errors Key during 400 response to PCISD request

Hello ZATCA team,

As a follow-up to the Nov 27 Q/A session, below is the point which needs further clarification:

  1. Error vs Erros Key during 400 response to PCISD request
  • Context: We are getting both “error” and error" keys;

{“requestID”: -2, “tokenType”: null, “dispositionMessage”: “NOT_COMPLIANT”, “binarySecurityToken”: null, “errors”: [“unable to submit and sign the csr in zatca side, caused : Error Parsing Request The request subject name is invalid or too long. 0x80094001 (-2146877439 CERTSRV_E_BAD_REQUESTSUBJECT)”]}

{‘type’: ‘ERROR’, ‘message’: ‘The provided Certificate Signing Request (CSR) is invalid. Maximum number of characters for Common name should be less than or equal to 64.’, ‘category’: ‘CSR_VALIDATION’, ‘code’: ‘EXCEED_CHARACTER_LIMIT’, ‘status’: ‘ERROR’, ‘status_code’: 400}

  • Question:
    • What is the actual schema of the API response in each case, as it seems the actual response does not follow the documentation referenced here: Zatca

We had sent an email to E-Invoicing E-invoicing@zatca.gov.sa, sp_support@zatca.gov.sa on Nov 28 but only recieved a response to call 19993 and submit a ticket.

Thank you!

cc: @Ankit.K.Tiwari

Hello ZATCA team,

Follow-up on this - thanks!

cc: @Ankit.K.Tiwari

This issue stems from the length of the serial number, which we have encountered previously. Please review this: