before january i was sending the sha 256 in the csr cnfg file
but when you told us the issue is fixed i faced the issue of invalidd csr on generating ccsid but when i read out the comments the issue was fixed
then i did some rnd and change this sha 256 to sha256 just removed the space and it works well i onboarded 4 differenr entites on simulation without any error again
@techcoder you shoulfd also review your xv csr cnfg file
To provide a comprehensive support as usual, can I kindly ask you to share your full concerns along with the steps that you followed to generate your CSR with your configuration file, to the below mail.
Dear idaoud,
Thanks for your quick response. some of my clients successfully onboarded simulation with same code i provided. i send the email with requested information. awaiting your kind advise.
I have a few inquiries and would appreciate any clarification:
Should the QR code be returned from the Clearance API? If not, how can I generate it myself?
From my understanding, when using the invoice type “1000”, I need to send three types of invoices to the Compliance API in order to obtain the PCSID. Will the same behavior apply in the production environment as well?
Thanks for reaching out. Welcome to our community.
Please find the answers below in order:
Yes, after successfully integrating with ZATCA and starting to use the clearance API to send your actual B2B invoices, the response should be the cleared invoice signed by ZATCA, including the QR. This invoice “Cleared one“ should be shared with the client.
Yes, you need to complete the compliance checks successfully to ensure the successful integration with ZATCA, or you will not be able to receive your PCSID.
I hope it’s clear enough now. Please do not hesitate to reach out if you require any further clarification.