> 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-public-trust-certificates/phase-2-steps-via-email-and-emsign/organization-verification.md).

# Organization Verification

### Action 5 - Organization Verification

&#x20;

The CA verifies that your organization is a real, legally registered entity. This is the most detailed verification step for EV certificates. The CA first attempts automatic verification using public business registries.

### Automatic Verification

If the CA can verify your organization automatically through public business registries, *this step completes without any action from you - it will simply move to "Completed". Only if automatic verification cannot confirm your organization will a Verified Professional Letter (VPL) be requested.*

&#x20;

### Verified Professional Letter (VPL)

*If automatic verification fails, the CA will request a Verified Professional Letter.*

&#x20;

**Step A - Email requesting VPL:**

<figure><img src="/files/QTPvs24iP5Fbz1QktgVa" alt=""><figcaption></figcaption></figure>

&#x20;

•       Subject: ORDER #\[ID] - Submit Verified Professional Letter for SSL EV request

*•       The email explains that the CA could not verify your organization through public sources and requests a VPL.*

*•       Click the orange "Submit Verified Professional Letter" button.*

&#x20;

**Step B - VPL Upload Form in emSign Portal:**

The VPL is an official letter on your organization's letterhead (or from a legal authority) that establishes your organization's identity. It should confirm: Legal name, DBA name (if applicable), Physical address, Contract Signer authority, and Certificate Approver authority.

&#x20;

<figure><img src="/files/DtKHpxjvd7wk6wbp27ny" alt=""><figcaption></figcaption></figure>

&#x20;

**Organization Name**

Auto-filled with your organization's name. Read-only. No action needed. Verify it displays your correct organization name.

&#x20;

**Document Source \*(required)\***

Describes the origin or type of the letter. *Enter a brief description of the document source (e.g., "Company Official Letterhead", "Notarized Business Registration Document").*

&#x20;

**Document (PDF only) \*(required)\***

The actual VPL file to upload. Platform accepts PDF files only. *Click "Choose File", select your VPL PDF file, and confirm the upload. Ensure the file is not password-protected.*

&#x20;

**Document Description \*(required)\***

A brief description of what the document contains. *Enter a short description (e.g., "Professional letter verifying ABC Inc legal registration and authorized signatories").*

&#x20;

**Issuer Name \*(required)\***

Full name of the person who prepared or signed this letter. *Enter the full name of the attorney, notary, company officer, or authorized professional who issued the letter.*

&#x20;

**Issuer Email ID \*(required)\***

Email address of the person who issued the letter. *Enter a valid work email address for the Issuer. The CA validation agent may contact them to verify the letter.*

&#x20;

**Issuer Contact No. \*(required)\***

Phone number of the Issuer. Select the country code and enter the full phone number. The CA may call to verify the letter.

&#x20;

•       *Click "Submit For Verification" to submit the VPL.*

&#x20;

Success: "Thank you for submitting the Legal Option Letter for \[organization] successfully."

### Organization Authentication Code

After the VPL is reviewed, the CA sends an Organization Authentication Code to the email address publicly listed for your organization (from public registries such as WHOIS or business databases).

&#x20;

**Two emails are sent simultaneously:**

•       An email to the publicly listed organizational contact containing the 6-digit Authentication Code.

•       An email to the Organization Representative containing a Verification Link to the emSign portal where the code must be entered.

&#x20;

<figure><img src="/files/4n00BgJSWWf9d7eI40oG" alt=""><figcaption></figcaption></figure>

&#x20;

<figure><img src="/files/Sfk0bCOHhHgDEDGCGVs0" alt=""><figcaption></figcaption></figure>

&#x20;

**Step C - Entering the Authentication Code:**

&#x20;

<figure><img src="/files/9nW7XTXl2Ckp6lF0r38m" alt=""><figcaption></figcaption></figure>

&#x20;

*•       Click the link in the Verification Link email.*

*•       On the emSign portal page, enter:*

*◦       Organization Authentication Code: Enter the 6-digit code received by the public registry contact.*

*◦       Designation: Enter your job title at the organization (e.g., "IT Manager", "Systems Administrator").*

*•       Click "Submit".*

&#x20;

Success: "Thank you for submitting the organization authentication code for \[organization] and completing the verification successfully."

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><p><strong>⚠ IMPORTANT</strong></p><p></p><p>The authentication code is sent to the publicly listed organizational contact - not necessarily to you. Coordinate internally with whoever receives that email to obtain the code.</p><p>The code expires in 24 hours. If it expires, use the Resync button next to Action 5 in the portal to trigger a new code.</p><p>Your Designation must reflect your actual role at the organization.</p></td></tr></tbody></table>


---

# 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-public-trust-certificates/phase-2-steps-via-email-and-emsign/organization-verification.md?ask=<question>&goal=<endgoal>
```

`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.
