> 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-dv-public-trust-certificates/phase-2-steps-via-email-and-emsign.md). # Phase 2 Steps (via email & emSign) ## Immediately After Payment – The Order View Screen The **Certificates :: Orders > View Order** page opens automatically after payment. This page serves as the central location for tracking and managing the certificate order within CERTInext.
### The Order Header Bar At the top of the page, a summary section displays the key details of the order. #### Order ID * A unique identifier assigned to the certificate order (for example: 1184216685). * This number is required when contacting support or searching for the order later. * Record the Order ID or take a screenshot of the page for future reference. #### Ordered Date * Displays the date and time when the order was submitted. * Confirms that the order was successfully created. #### Product * Displays the SSL/TLS certificate variant selected during the ordering process. * Verify that the displayed product matches the intended certificate type. #### Group * Displays the organization or account under which the certificate was ordered. * Confirms the billing and ownership account. #### CA Source * Displays the issuing Certificate Authority. * For emSign certificates, this field shows **emSign**. * Verify that the expected CA is displayed. #### Certificate Price * Displays the total amount charged for the certificate order in USD. * This amount should match the Grand Total shown during the Order Summary & Payment step. #### Order Status * Displays **Order Accepted** in an orange status badge. * This indicates that payment has been successfully received and the order has been recorded in CERTInext. * The certificate request has not yet been forwarded to the Certificate Authority for processing. * No action is required from the requestor at this stage. #### Certificate Status * Displays **Pending for Approver** in an orange status badge. * Indicates that the certificate request is awaiting approval from the organization's CERTInext Account Administrator. * The request cannot proceed until administrator approval has been completed. **If you are an Administrator:** * Use the 3-dot menu located in the upper-right corner of the page to approve the request. **If you are not an Administrator:** * Contact your IT department or CERTInext account administrator and provide the Order ID for approval. ### ⚠️ Important – Pending for Approver In enterprise CERTInext accounts, every new certificate order must be approved by an Account Administrator before it is forwarded to emSign for processing. * If you are the designated Administrator, approve the request using the 3-dot menu available on this page. * If you are not the Administrator, contact the responsible administrator or CERTInext account manager and request approval. * Include the Order ID when requesting approval to help locate the order quickly. ### What the Rest of the Order View Page Shows #### SSL Subscription Information Displays information about the certificate subscription. * **Subscription For:** Displays the selected subscription period (for example, 1 Year, 2 Years, or 3 Years). * **Subscription Start Date:** Displays as a dash (-) until the certificate is issued. * **Subscription End Date:** Displays as a dash (-) until the certificate is issued. * **Subscription Status:** Displays **Pending** in an orange status badge until issuance is completed. #### Auto-Renewal Configuration Displays the renewal settings selected during the order process. * Confirms whether automatic renewal is enabled. * Displays the configured number of days before certificate expiry when the renewal process should begin. #### Certificate Information Displays the certificate details entered during ordering. * Primary domain name. * Additional domains (SANs), if applicable. * Confirms the exact domains that will be included in the certificate. #### Certificate Requestor Information Displays the details of the user who submitted the certificate request. * Requestor Name. * Requestor Email Address. #### CSR Information Displays information extracted from the submitted Certificate Signing Request (CSR). * **Common Name (CN):** The primary domain name. * **Key Size:** Typically: * 2048-bit RSA for DV SSL and DV UCC certificates. * 4096-bit RSA for Wildcard certificate variants. * **Key Algorithm:** RSA. #### Ordered By Displays details of the individual who submitted the order. * User Name. * User Role. #### Renewal Notifications Displays the notification configuration for certificate renewal. * **Send Email Notifications:** Yes. * Renewal reminder emails will be sent before certificate expiration. #### Reissue History Displays the history of certificate reissues. * For a newly created order, the section displays: * **No records found** * This is expected because no certificate reissues have occurred yet. ### 📌 Note - Three Dot Menu Options *The 3-dot menu located in the upper-right corner of the Order View page provides access to additional order management functions.* Depending on the order status and user permissions, the menu may include: * Track Order (generate a public tracking URL) * Download Invoice * Replace CSR * Recall Request * Cancel Order * Download Certificate (available after issuance) * Reissue Certificate (available after issuance) These options allow administrators and authorized users to manage the certificate throughout its lifecycle. ## PHASE 2 will have below steps in a nutshell #### Order Confirmation After the order is submitted and payment is successfully processed: * A confirmation email is sent to the Requestor's registered email address. * The email contains a Track Order link. * Use this link to monitor the progress of the certificate request throughout the validation and issuance process. #### Domain Verification For all DV (Domain Validation) SSL/TLS certificates, domain ownership or control must be verified before certificate issuance. * Open the **emSign Subscriber Portal** using the link provided in the order emails. * Complete the Domain Control Validation (DCV) process using one of the available verification methods. * Domain verification confirms that you are authorized to request a certificate for the domain. * Certificate issuance cannot proceed until domain validation is successfully completed. #### Administrator Approval Applicable for enterprise accounts where approval workflows are enabled. * The certificate request is routed to the designated CERTInext Administrator. * The administrator reviews the request details, including: * Certificate product * Domain names * Requestor information * Organizational policies * The administrator can approve or reject the request. * Processing continues only after approval is granted. #### Certificate Issued Once all required validations and approvals have been completed: * emSign issues the SSL/TLS certificate. * Certificate issuance notifications are sent via email. * The certificate becomes available for download through CERTInext and the associated certificate management workflows. #### Download & Install After issuance: * Download the certificate files from CERTInext. * Download any required intermediate or CA chain certificates if applicable. * Install the certificate on the target server, application, load balancer, appliance, or device. * Verify that HTTPS/TLS services are functioning correctly after installation. * Perform post-installation validation to confirm successful deployment and secure connectivity. --- # 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-dv-public-trust-certificates/phase-2-steps-via-email-and-emsign.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.