Greetings, I have a question , during the signing process of the xml , The certificate to be used is the returned value from Production CSID but to reach this step we have to pass the compliance check step where we have to submit three simplified invoices normal , credit and debit notes… so to create these 3 invoices and make sure they are complying we have to sign them … my question is what certificate should be used to sign these three simplified invoices for compliance check purposes… as this step is needed before the last step of getting the PCSID , Am I missing something?
Yes, you are missing something from the APIs. After completing the compliance CSID API, it will return you a security binary token. This is the first API that you need to complete by submitting a valid CSR. However, you should take the returned security binary token and decode it using base64. The output is the X.509 certificate that you will sign your invoices with in compliance checks (Compliance Invoice API). After that, you will use the production CSID API certificate to sign your invoices for reporting API.
Here is a summary of the two certificates:
- Compliance CSID certificate: This certificate is used to sign invoices for compliance checks. You can get this certificate by completing the compliance CSID API and decoding the security binary token that is returned.
- Production CSID certificate: This certificate is used to sign invoices for reporting . You can get this certificate by completing the production CSID API and decoding the security binary token that is returned.
I hope this answers your question. Please do not hesitate to ask any further questions.
make sure to decode the returned security binary tokens with (base64), the output after decoding is the certifecate you will sign your invoices with.
Yes, you are missing something from the APIs. After completing the compliance CSID API, it will return you a security binary token. This is the first API that you need to complete by submitting a valid CSR. However, you should take the returned security binary token and decode it using base64. The output is the X.509 certificate that you will sign your invoices with in compliance checks (Compliance Invoice API). After that, you will use the production CSID API certificate to sign your invoices for reporting or clearance APIs.
Here is a summary of the two certificates:
- Compliance CSID certificate: This certificate is used to sign invoices for compliance checks. You can get this certificate by completing the compliance CSID API and decoding the security binary token that is returned.
- Production CSID certificate: This certificate is used to sign invoices for reporting or clearance. You can get this certificate by completing the production CSID API and decoding the security binary token that is returned.
I hope this answers your question. Please do not hesitate to ask any further questions.