Invalid OTP in Simulation

We generated the otp from simulation portal and we are getting this API response error

{“errors”:[{“code”:“Invalid-OTP”,“message”:“The provided OTP is invalid”}]}

And this is the CSR config

------------------------------------------------------------------

Default section for “req” command options

------------------------------------------------------------------

oid_section = OIDs
[ OIDs ]
certificateTemplateName= 1.3.6.1.4.1.1311.20.2

[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 (ASN1:UTF8String:TSTZATCA-Code-Signing - ASN1:UTF8String:ZATCA-Code-Signing)

certificateTemplateName = ASN1:PRINTABLESTRING:PREZATCA-Code-Signing
subjectAltName=dirName:dir_sect

[ dir_sect ]

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

SN = 1-Report Organization|2-WEB|3-352f3b639

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

UID = 311#######00003

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

title = 0100

Location (branch address or website)

registeredAddress = 0000 King Fahahd st, Khobar

Industry (industry sector name)

businessCategory = Other

------------------------------------------------------------------

Section for prompting DN field values to create “subject”

------------------------------------------------------------------

[my_req_dn_prompt]

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

commonName = INV60

Organization Unit (Branch name)

organizationalUnitName = Main Branch

Organization name (Tax payer name)

organizationName = Report

ISO2 country code is required with US as default

countryName = SA

from the config file it appears that you are using a simulation environment, did you obtain the OTP from the simulation environment in Fatoora portal?

Yes, we did and we still keep getting same response @lalomar

Yes, we did and we still keep getting same response

Dear @emyr

Thanks for reaching out,

Can I kindly ask you to send your full concerns with your .cnf file and the steps you are following with screens to API response to the below SP support email. To take a look and get back to you ASAP, and schedule meeting if needed.

SP email: sp_support@zatca.gov.sa.

Thanks,
Ibrahem Daoud.

We have sent an email and we are still waiting for a reply @idaoud @lalomar

Hello @idaoud @lalomar

Any update on the issue we sent ? We are still waiting for a reply, the email title is the same title as the post.

Thank you

Dear @emyr

Thank you for reaching out, kindly have you sent the details to the below emails?

sp_support@zatca.gov.sa
E-invoicing@zatca.gov.sa

And the team will get back to your concerns as soon as possible.

Thank you.

1 Like

Hello,

We are still waiting for a reply ?

It’s been 2 weeks now and we still haven’t received a reply, we are being delayed a lot due to this, as we are pass our internal deadline for this, also the problem is that when we post to community it takes 2 days for approval and then another 2 days for someone to reply and then again 2 days for approval of our reply and so on, this way it will take us weeks to resolve any issue / question we might have, and it’s been a week since we sent the issue to both emails and still no reply.@saalotaibi @idaoud @lalomar

Please reply ASAP

Thank you in advance

Did you get solution to this? we are so stuck. Facing same error

Dear @emyr

Can I kindly ask you to shear your email that you reached to SP mail from?

Thanks,
Ibrahem Daoud.

Do we have an issue with the portal? We have tried several times.
When I try, First am getting : invalid OTP error - ( 2 mins after generating OTP)
On trying with another OTP, I am getting error 409 (conflict) : Compliance transaction was submitted/generated before.