# EGS not appear in device\_list

**URL:** <https://zatca1.discourse.group/t/egs-not-appear-in-device-list/3872>\
**Category:** Onboarding, renewal and revocation\
**Created:** [October 27, 2024, 9:09am UTC](https://zatca1.discourse.group/t/egs-not-appear-in-device-list/3872 "2024-10-27T09:09:36Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![AhmedTarekYA](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AhmedTarekYA](https://zatca1.discourse.group/u/AhmedTarekYA)\
**Post date:** [October 27, 2024, 9:09am UTC](https://zatca1.discourse.group/t/egs-not-appear-in-device-list/3872/1 "2024-10-27T09:09:36Z")

</div>

I created CSR and private key and when use the OTP that i get from fatoora i get the ICSR Successfully but device\_list is always empty and when try to report the invoice i get error in (Invalid signed properties hashing, SignedProperties with id=‘xadesSignedProperties’) while every thing is working fine in developer mode .. this is my csr config temp \<?php

// 2.2.2 Profile specification of the Cryptographic Stamp identifiers. & CSR field contents / RDNs.  
return \<\<\<TEXT

# ------------------------------------------------------------------

# Default section for “req” command options

# ------------------------------------------------------------------

[req]

# Password for reading in existing private key file

# input\_password = SET\_PRIVATE\_KEY\_PASS

# Prompt for DN field values and CSR attributes in ASCII

prompt = no  
utf8 = no

# Section pointer for DN field options

distinguished\_name = my\_req\_dn\_prompt

# Extensions

req\_extensions = v3\_req

[v3\_req]  
#basicConstraints=CA:FALSE  
#keyUsage = digitalSignature, keyEncipherment

# Production or Testing Template (TSTZATCA-Code-Signing - ZATCA-Code-Signing)

1.3.6.1.4.1.311.20.2 = ASN1:UTF8String:SET\_PRODUCTION\_VALUE  
subjectAltName=dirName:dir\_sect

[dir\_sect]

# EGS Serial number (1-SolutionName|2-ModelOrVersion|3-serialNumber)

SN = SET\_EGS\_SERIAL\_NUMBER

# VAT Registration number of TaxPayer (Organization identifier [15 digits begins with 3 and ends with 3])

UID = SET\_VAT\_REGISTRATION\_NUMBER

# Invoice type (TSCZ)(1 = supported, 0 not supported) (Tax, Simplified, future use, future use)

title = 0100

# Location (branch address or website)

registeredAddress = SET\_BRANCH\_LOCATION

# Industry (industry sector name)

businessCategory = SET\_BRANCH\_INDUSTRY

# ------------------------------------------------------------------

# Section for prompting DN field values to create “subject”

# ------------------------------------------------------------------

[my\_req\_dn\_prompt]

# Common name (EGS TaxPayer PROVIDED ID [FREE TEXT])

commonName = SET\_COMMON\_NAME

# Organization Unit (Branch name)

organizationalUnitName = SET\_BRANCH\_NAME

# Organization name (Tax payer name)

organizationName = SET\_TAXPAYER\_NAME

# ISO2 country code is required with US as default

countryName = SA  
TEXT;

---

<div class="post-metadata">

**Author:** ![saalotaibi](https://avatars.discourse-cdn.com/v4/letter/s/f9ae1b/32.png) [@saalotaibi](https://zatca1.discourse.group/u/saalotaibi)\
**Post date:** [October 27, 2024, 12:25pm UTC](https://zatca1.discourse.group/t/egs-not-appear-in-device-list/3872/2 "2024-10-27T12:25:05Z")

</div>

Dear @AhmedTarekYA

Regarding the devices not being appeared in the device list, you need to take the production CSID for the device to show.  
Below on boarding steps:

1- Get the compliance CSID  
2- Compliance checks  
3- Request compliance CSID

After successfully calling the production CSID API the device will appear in the device list.

Also, you can follow the below steps to solve your signing problem:

1-After submitting the Certificate Signing Request (CSR) via the Compliance Request CSID API, you will receive a BinaryToken and a secret.  
2-Decode the BinaryToken using a base64 decoder. The decoded value will be the x.509 certificate.  
3-Navigate to the SDK directory: SDK/Data/Certificates/Cert.pem.  
4-Replace the contents of the Cert.pem file with the x.509 certificate obtained from the decoded BinaryToken.  
5-Insert the newly generated private key into the ec-secp256k1-priv-key.pem file.  
6-if you use JAVA SDK, run the following command: fatoora -sign -invoice “invoice.xml”.  
else the .Net SDK, run the following command: fatooranet sign -invoice “invoice.xml”  
7-The invoice will now be signed and can be successfully submitted during the compliance checks phase via the Compliance Invoice API.

Do the same steps with production CSID to sign and submit e invoices to the reporting APIs.

If you are still facing issue, kindly reach out to the below emails:  
E-invoicing@zatca.gov.sa  
sp\_support@zatca.gov.sa

Thank you.

---

<div class="post-metadata">

**Author:** ![AhmedTarekYA](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AhmedTarekYA](https://zatca1.discourse.group/u/AhmedTarekYA)\
**Post date:** [October 28, 2024, 7:20am UTC](https://zatca1.discourse.group/t/egs-not-appear-in-device-list/3872/3 "2024-10-28T07:20:05Z")

</div>

> [@saalotaibi](#):
>
> Request compliance CSID

end point to Request compliance CSID ?

---

<div class="post-metadata">

**Author:** ![AhmedTarekYA](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@AhmedTarekYA](https://zatca1.discourse.group/u/AhmedTarekYA)\
**Post date:** [October 28, 2024, 7:20am UTC](https://zatca1.discourse.group/t/egs-not-appear-in-device-list/3872/4 "2024-10-28T07:20:41Z")

</div>

error is Invalid signed properties hashing, SignedProperties with id=‘xadesSignedProperties’ in simulation mode but all is ok in test mode

---

<div class="post-metadata">

**Author:** ![hashika](https://avatars.discourse-cdn.com/v4/letter/h/ce7236/32.png) [@hashika](https://zatca1.discourse.group/u/hashika)\
**Post date:** [April 8, 2025, 8:46am UTC](https://zatca1.discourse.group/t/egs-not-appear-in-device-list/3872/5 "2025-04-08T08:46:11Z")

</div>

I have onboarded my EGS unit to ZATCA with below flow

Make the CSR using SDK  
Call the compliance CSID API  
Call production CSID API by authorizing the response of Compliance CSID API

My issue is that the onboarding process was successfully completed with API calls, but my EGS does not appear in fatoora registered device list?