> 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.md).

# Phase 2 Steps (via email & emSign)

After you pay, your certificate application enters a multi-step verification process managed by emSign (the Certificate Authority). You do not need to do everything yourself - some steps involve other people you nominated (the Contract Signer and Certificate Approver). However, you will receive emails at each stage and may need to take action or follow up with others.

 

The entire post-submission process consists of five sequential actions that must all be completed before your certificate is issued:

 

•     Action 1: Certificate Requester Verification (you)

•     Action 2: Subscriber Agreement (Contract Signer)

•     Action 3: EV Certificate Request Approval (Certificate Approver)

•     Action 4: Organization Verification (you or your team, with emSign)

•     Action 5: Certificate Download (you)

 

**⚠  IMPORTANT: Read Before You Begin**

•  All actions must be completed for your certificate to be issued. If any action is left incomplete, the certificate will not be issued.

•  You can track the status of all actions at any time by logging into CERTInext, going to Certificates > Orders, and clicking on your order.

•  If you encounter a "Track Order Status" button, click it to get a direct tracking link. You can also share this link with others involved in the process.

•  The typical issuance time is 1–5 business days after all actions are completed.

 

 


---

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