A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Use email address associated to the entity not the ones with free host domains
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Organization: Sivants LLC Subscription ID: [Removed PII] Artifact Signing account: SivantsLLC1703 Prior ticket reference: [Removed PII] (closed — was on Basic support, now upgraded)
I've had three Public Organization identity validation attempts fail, with no reason exposed anywhere in the portal on any of them:
One additional observation: during the personal identity verification step via the Microsoft Authenticator app, my postal code displayed as "347340000" instead of my actual ZIP+4, "34734-5130" — this looks like a parsing bug (the ZIP+4 dash apparently being replaced with zeros). I retried using just the 5-digit ZIP ("34734") to rule this out as the cause, and it still failed, so it may be unrelated to the validation failures, but it's a data-handling bug worth flagging regardless.
Given three failed attempts with zero diagnostic information exposed, please check backend logs for the actual rejection reason(s) and advise on the correct way to get a successful validation for Sivants LLC — whether that's a fourth attempt with specific corrections, or something needs to be reset/cleared on your end first.
A fully managed end-to-end service for digitally signing code, documents, and applications. (formerly Trusted Signing)
Use email address associated to the entity not the ones with free host domains
Its been several days with no support? Why am I paying for this service?