Generate Certificate Hash

Signing process
1

What is the process of generating certificate hash? Page 5 of <SigningProcessUpdated.pdf> describes:

  1. Hash the x509 certificate using SHA-256 (output).
    e.g.:69a95fc237b42714dc4457a33b94cc452fd9f110504c683c401144d9544894fb
  2. Encode the hashed x509 certificate using base64 (ENCODER BASE64 ) (output).
    e.g.:NjlhOTVmYzIzN2I0MjcxNGRjNDQ1N2EzM2I5NGNjNDUyZmQ5ZjExMDUwNGM2ODNjNDAxMTQ0ZDk1NDQ4OTRmYg==

Why does the length of the HASH encoded by BASE64 become 88? Or where can I find more detailed step-by-step instructions?

2

Dear @zeimao77,
Thanks for reaching out.
Please do not repeat your inquiry.
*Please check the signing process on the technical guidelines (1st step is how to generate the hash):https://zatca.gov.sa/en/E-Invoicing/Introduction/Guidelines/Documents/E-invoicing-Detailed-Technical-Guideline.pdf 102

if the invoice is standard:**after hashing the invoice hash using: fatoora -generatehash -invoice [name.xml], you should edit it manually in the first “digestvalue” tag which represents the invoice hash in the XML

if the invoice is simplified : sign the invoice using SDK through this command : fatoora -sign -invoice [name.xml]

this step will edit the invoice hash inside the XML automatically & will generate a new invoice with the suffix [_signed]

Thanks.