> 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-doc-signer-certificates/phase-2-steps-via-email-and-emsign.md).

# Phase 2 Steps (via email & emSign)

After you complete Phase 1 and payment is processed, your order enters a multi-step verification workflow. This phase involves a series of verification tasks that must be completed to prove your identity and your organization's legitimacy. All steps are managed through the emsSign subscriber portal.

#### Verification Steps Overview

You will need to complete six verification steps on the emsSign subscriber portal. The steps and their initial statuses are as follows:

•       Step 1: Subscriber Agreement - Awaiting Customer Action

•       Step 2: Email Verification - Awaiting Customer Action

•       Step 3: Individual Verification - Awaiting Customer Action

•       Step 4: Organization Verification - Pending

•       Step 5: Face To Face Verification - Awaiting Customer Action

•       Step 6: Certificate Download - Issuance Pending

 

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">NOTE: Steps 1 through 5 must all be completed before Step 6 (Certificate Download) becomes available. You can complete steps in parallel where possible.</td></tr></tbody></table>

<table data-header-hidden><thead><tr><th valign="top"></th></tr></thead><tbody><tr><td valign="top">IMPORTANT: All verification links sent by email expire within 24 hours. Act promptly to avoid delays. If a link expires, contact CERTInext support to request a new one.</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-doc-signer-certificates/phase-2-steps-via-email-and-emsign.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.