full code in simulation

[AhmedTarekYA]

does any one finish the full integration code ?

[thaifanisalla]

Yes , You can use this in simulation or production , Even in sandbox
we support the three modes

[AhmedTarekYA]

Unfortunately i get +"errorMessages": array:1 [ 0 => {#3201 +"type": "ERROR" +"code": "signed-properties-hashing" +"category": "CERTIFICATE_ERRORS" +"message": "Invalid signed properties hashing, SignedProperties with id='xadesSignedProperties'" +"status": "ERROR" } ] في أربعاء، 6 نوفمبر، 2024 في 11:31 ص، كتب Zaher Thaifani < ***@***.***>:

…

Yes , You can use this in simulation or production , Even in sandbox we support the three modes — Reply to this email directly, view it on GitHub <#45 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUGRNTQIUCBMPT6DYGAQEM3Z7HOVNAVCNFSM6AAAAABQVZ4O4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJZGEYTKMZZGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[thaifanisalla]

Hi @AhmedTarekYA
Could you please provide the steps you followed?

Here are some important notes:

• When generating the CSR, ensure the environment is set to "simulation" by passing 'simulation' using the setCurrentZatcaEnv(string $currentEnv) function here .
  here a full example of how to generate the CSR.
• Make sure to provide the correct private key when signing the invoice.
• For phpseclib, ensure you're using version "phpseclib/phpseclib": "3.0.x-dev".

[islamazouz]

i have the same problem

[hamza-id]

Any resolution i am also facing the same error.

[Hazem7575]

i too have same error

[hamza-id]

The issue relates to signed properties, specifically that their hash value does not match its calculated value. This discrepancy happens due to the formatting of signed properties before hashing.
The signed properties hash is highly sensitive and can change with even a single whitespace modification, causing it to fail reconciliation on ZATCA side in B2C or simplified case.

[T-Mohamed-adam]

Has anyone solved this issue? I'm facing the same error: Invalid signed properties hashing, SignedProperties with id='xadesSignedProperties'. Any help would be appreciated!

[hamza-id]

Finally, I resolved this error by having 36 spaces in the first line and 4 spaces after that. This changes the hash ofthe signed property hash value does not match its calculated value. The signed properties hash is highly sensitive and can change with even a whitespace.

                                     <xades:SignedSignatureProperties>
                                        <xades:SigningTime>2025-01-19T08:01:20</xades:SigningTime>
                                        <xades:SigningCertificate>
                                            <xades:Cert>
                                                <xades:CertDigest>
                                                    <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256" />
                                                    <ds:DigestValue>NTlhYjZjMDBiZmU5OGYzNmVlMmNhNzVlODhiOWQ0Nzc2ODk0ZGE4MDBkMjQ3YzgzZmQ4NDIzM2U3YzE0NWIxYQ==</ds:DigestValue>
                                                </xades:CertDigest>
                                                <xades:IssuerSerial>
                                                    <ds:X509IssuerName>0.9.2342.19200300.100.1.25=local/0.9.2342.19200300.100.1.25=gov/0.9.2342.19200300.100.1.25=extgazt, CN=PEZEINVOICESCA1-CA</ds:X509IssuerName>
                                                    <ds:X509SerialNumber>2207773857395212338642076460671910039858986559</ds:X509SerialNumber>
                                                </xades:IssuerSerial>
                                            </xades:Cert>
                                        </xades:SigningCertificate>
                                    </xades:SignedSignatureProperties>
                                </xades:SignedProperties>