> For the complete documentation index, see [llms.txt](https://docs.certinext.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-ev-code-signing-certificates/phase-2-steps-via-email-and-emsign/organization-verification.md).
# Organization Verification
Organization Verification is the process by which emSign independently confirms that your organization is legitimate. This step is primarily managed by emSign's validation team, but you (or your team) may need to take action in one or both of the following ways:
#### Sub-Action 4A: Submit a Verified Professional Letter
*If emSign is unable to verify your organization through public databases, they will ask you to submit a Verified Professional Letter – a formal document from a qualified professional (such as a lawyer, accountant, or government-recognized authority) confirming your organization's details.*
**Email you will receive:**
• Subject: "ORDER #\[Order ID] – Submit Verified Professional Letter for SSL EV request"
• The email explains that emSign was unable to verify your organization through standard channels and requests that you submit a formal verification document.
• It contains a button labeled "Submit Verified Professional Letter."
**What the Verified Professional Letter should contain (according to emSign):**
• The Exact Organization Formal Legal Name or Assumed Name or DBA (Doing Business As) name
• Physical presence and address of place of business
• Signing Authority of Contract Signer
• EV Authority of Certificate Approver to act on behalf of the organization
**Fields on the submission form:**
**Organization Name**
Your organization's name (pre-filled from your application).
*Verify this is correct. Do not change it.*
**Document Source**
The source or issuer of the verification document (e.g., law firm, accounting firm, government authority).
*Enter the name of the institution or professional who issued the document.*
**Document**
The actual verification document file. Platform accepts PDF files only.
*Click "Choose File" and select your PDF document from your computer. Ensure the file is a valid, signed PDF. Do not upload Word documents or images.*
**Document Description**
A brief description of the document you are uploading.
*Enter a short description such as "Company Verification Letter - Signed by Legal Counsel."*
**Issuer Name**
The name of the professional or authority who issued and signed the document.
*Enter the full name of the issuer (e.g., "Jane Smith, Certified Public Accountant").*
**Issuer Email ID**
The professional email address of the issuer. emSign may contact this person to verify the document.
*Enter the issuer's professional email address. This should be an official business email, not a personal email.*
**Issuer Contact No.**
The phone number of the issuer, including country code.
*Enter the issuer's phone number with country code (e.g., +1 for the US).*
After filling in all fields, click the "Submit For Verification" button. A green success message will appear confirming the document has been submitted.
**⚠ IMPORTANT NOTE**
• Only PDF files are accepted. If your document is in another format, convert it to PDF before uploading.
• emSign's Validation Agent will review the submitted document and may contact the issuer to verify its authenticity.
• If the document is rejected, you will receive another email with the reason. You can then resubmit a corrected document.
• Make sure the issuer is reachable at the email and phone number provided, as emSign may contact them directly.
###
### Sub-Action 4B: Organization Authentication Code Verification
*As part of Organization Verification, emSign will also send an Organization Authentication Code to confirm that the Organization Representative is legitimately associated with the organization.*
**How this works:**
• emSign sends an email to the Organization Representative's email address with a unique numeric Authentication Code (e.g., 885190).
• A second email is sent with a verification link. The Organization Representative must click this link to open the verification page.
• On the verification page, the Organization Representative enters the code from the first email.
**Email 1 (Authentication Code):**
• Subject: "ORDER #\[Order ID] – Authentication Code for \[Organization Name] Organization"
• Contains a 6-digit authentication code (e.g., 885190).
• Important: This code expires in 24 hours. Do not delay in using it.
**Email 2 (Verification Link):**
• Subject: "ORDER #\[Order ID] – Authentication Code Verification Link for \[Organization Name] Organization"
• Contains a link to the verification page.
• Important: This link also expires in 24 hours.
**Fields on the verification form:**
**Organization Name**
Pre-filled with your organization's name.
*Verify this is correct.*
**Organization Authentication Code**
The 6-digit code sent in Email 1.
*Enter the exact code from your email (e.g., 885190). Do not add spaces or dashes.*
**Designation**
The job title of the person submitting the code.
*Enter your designation (e.g., "IT Manager").*
*Click the "Submit" button after entering the code. A green success message will confirm that the authentication code has been verified.*
**⚠ IMPORTANT NOTE**
• Both emails (Authentication Code and Verification Link) are sent to the Organization Representative's email. Act promptly - both expire in 24 hours.
• The authentication code and the verification link must be used together. Do not share the code with anyone outside your organization.
• If the code has expired before you could use it, contact CERTInext or emSign support to request a new code.
• Once submitted successfully, Action 4 (Organization Verification) will update to "Completed" in the tracker.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.certinext.io/documentation/certificate-lifecycle-management/ordering-a-certificate/as-a-customer/ordering-ev-code-signing-certificates/phase-2-steps-via-email-and-emsign/organization-verification.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.