# Simulation Onboarding Issue : Error Invalid CSR

**URL:** <https://zatca1.discourse.group/t/simulation-onboarding-issue-error-invalid-csr/4670>\
**Category:** Onboarding, renewal and revocation\
**Created:** [December 18, 2024, 2:55pm UTC](https://zatca1.discourse.group/t/simulation-onboarding-issue-error-invalid-csr/4670 "2024-12-18T14:55:12Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![UnitedDev](https://avatars.discourse-cdn.com/v4/letter/u/e9bcb4/32.png) [@UnitedDev](https://zatca1.discourse.group/u/UnitedDev)\
**Post date:** [December 18, 2024, 2:55pm UTC](https://zatca1.discourse.group/t/simulation-onboarding-issue-error-invalid-csr/4670/1 "2024-12-18T14:55:12Z")

</div>

**I will share all the information below step by step and with code i am using Please check :**

1- i have completed sandbox CSID and Compliance invoices successfully

2- i moved to fatoora Simulation environment and generated CSR , got successful response then i decoded binarysecurity token to use as X509 certificate

Link that generated CSR : [https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/compliance](https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/compliance)

3- After generating CSR , i used binarysecurity : security as authorization and submitted all 6 types invoice ( standard , debit , credit | simplified , debit and credit ) . In every invoice i got successful message.

Link i submitted all invoices : [https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/compliance/invoices](https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/compliance/invoices)

4- **in the last step i am getting an error** : i wanted to generate PCSID as per forum and document so used my “compliance\_request\_id” that generated in simulation CSID and used same authorization that generated in step 2.

Link to generate PCSID : [https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/production/csids](https://gw-fatoora.zatca.gov.sa/e-invoicing/simulation/production/csids)

* * *

below i am attaching that generate my CSR , please check what am i doing wrong

My CSR generating code to test in Google Collab : [click here](https://colab.research.google.com/drive/1SC_hotS3fDVQwITlUXna8VqTfM0NAMrq?usp=sharing)

to check my CSR generation code in file : [click here](https://we.tl/t-UK4keq1K1L)

---

<div class="post-metadata">

**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\
**Post date:** [December 19, 2024, 7:09am UTC](https://zatca1.discourse.group/t/simulation-onboarding-issue-error-invalid-csr/4670/2 "2024-12-19T07:09:39Z")

</div>

Dear @UnitedDev

Thanks for reaching out,

Can I kindly ask you to share the full concerns via below mail to schedule meeting if needed

SP mail: [sp\_support@zatca.gov.sa](mailto:sp_support@zatca.gov.sa)

Thanks,  
Ibrahem Daoud.

---

<div class="post-metadata">

**Author:** ![UnitedDev](https://avatars.discourse-cdn.com/v4/letter/u/e9bcb4/32.png) [@UnitedDev](https://zatca1.discourse.group/u/UnitedDev)\
**Post date:** [December 19, 2024, 9:37am UTC](https://zatca1.discourse.group/t/simulation-onboarding-issue-error-invalid-csr/4670/3 "2024-12-19T09:37:16Z")

</div>

please help me because in the 4th step while creating simulation PCSID i am getting this error

Here in this step i am getting this error :

{  
“errorCode”: “400”,  
“errorCategory”: “Invalid-CSR”,  
“errorMessage”: “The provided Certificate Signing Request (CSR) is invalid.”  
}

---

<div class="post-metadata">

**Author:** ![UnitedDev](https://avatars.discourse-cdn.com/v4/letter/u/e9bcb4/32.png) [@UnitedDev](https://zatca1.discourse.group/u/UnitedDev)\
**Post date:** [December 22, 2024, 8:25am UTC](https://zatca1.discourse.group/t/simulation-onboarding-issue-error-invalid-csr/4670/4 "2024-12-22T08:25:54Z")

</div>

okay thank you for your response, please check i have added every information and i have emailed you on : sp\_support@zatca.gov.sa

---

<div class="post-metadata">

**Author:** ![eCloud](https://dub1.discourse-cdn.com/flex013/user_avatar/zatca1.discourse.group/ecloud/32/629_2.png) [@eCloud](https://zatca1.discourse.group/u/eCloud)\
**Post date:** [December 22, 2024, 8:28am UTC](https://zatca1.discourse.group/t/simulation-onboarding-issue-error-invalid-csr/4670/5 "2024-12-22T08:28:10Z")

</div>

You may need to check what request you submitted to `/production/csid`. This endpoint has 2 actions **POST** and **PATCH** , make sure you send a POST Request to get the PCSID.

---

<div class="post-metadata">

**Author:** ![Adithya\_Raviraja](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@Adithya\_Raviraja](https://zatca1.discourse.group/u/Adithya_Raviraja)\
**Post date:** [January 21, 2025, 11:42am UTC](https://zatca1.discourse.group/t/simulation-onboarding-issue-error-invalid-csr/4670/6 "2025-01-21T11:42:06Z")

</div>

Hi,

We are facing a similar issue with a client of ours for simulation onboarding. Were you able to find a solution/workaround for this?

---

<div class="post-metadata">

**Author:** ![idaoud](https://avatars.discourse-cdn.com/v4/letter/i/f9ae1b/32.png) [@idaoud](https://zatca1.discourse.group/u/idaoud)\
**Post date:** [January 21, 2025, 12:04pm UTC](https://zatca1.discourse.group/t/simulation-onboarding-issue-error-invalid-csr/4670/7 "2025-01-21T12:04:24Z")

</div>

Dear @Adithya_Raviraja

Thanks for reaching out,

Can I kindly ask you to check it again and confirm if you are still facing the same response?

Thanks,  
Ibrahem Daoud.

---

<div class="post-metadata">

**Author:** ![Adithya\_Raviraja](https://avatars.discourse-cdn.com/v4/letter/a/91b2a8/32.png) [@Adithya\_Raviraja](https://zatca1.discourse.group/u/Adithya_Raviraja)\
**Post date:** [January 23, 2025, 7:39am UTC](https://zatca1.discourse.group/t/simulation-onboarding-issue-error-invalid-csr/4670/8 "2025-01-23T07:39:19Z")

</div>

Hi @idaoud ,

Thank you for your response, we will attempt to re-onboard the client in simulation next week and let you know. FYI though, this issue was seen only in the simulation the same client was onboarded successfully in production.
