The short answer
As of October 2026, Certum lists 1–5 days to issue a Standard code signing certificate and 1–7 days for EV. Neither figure says whether it counts business or calendar days, or when the count starts. The certificate authority's work sits between two steps that are yours: entering your details and verifying your identity first, then setting up signing after issuance. A code signing certificate is never instant.
My-SSL sells Certum certificates. Its Standard and EV code signing certificates are both delivered through Certum's SimplySign cloud service, so after issuance there is no token to wait for. Already ordered? Jump to what makes an order wait.
On this page
How long does each code signing certificate type take?
Certum's code signing page, last modified in July 2026, gives one "standard issue time" per product: 1–5 days for Open Source, 1–5 days for Standard and 1–7 days for EV. An older Certum support article from January 2024 still says 1–3 days for Open Source and Standard.
| Certum product | Listed issue time (Jul 2026) | Who can apply | Documents Certum lists |
|---|---|---|---|
| Open Source | 1–5 days | Individuals with an ongoing open source project | Identity check, utility bill in your name, the project's website address |
| Standard | 1–5 days | An individual or a company | Identity check; individuals add a utility bill; companies add a power of attorney or registration document only when needed |
| EV | 1–7 days | Registered companies only | Identity check, utility bill issued for the organization, confirmation of a physical office; a power of attorney or registration document when needed |
Two things the ranges leave out matter for planning. Certum does not say whether "days" means business days, and it does not say when the count begins. Certum's 2024 support article calls its figure the "time of issue after verification", which suggests the days may start only after Certum's checks are done, so allow time for those checks on top of the range. The Open Source tier is listed for completeness; My-SSL sells Standard and EV only.
What happens during code signing validation?
Certum's activation manual for a cloud code signing certificate runs in this order: you enter the subscriber, organization and authorization data in your account, you verify your identity, and Certum then checks what you entered. For a company, Certum confirms the company exists, by registration number or a document, and that the subscriber may act for it, by the registry or a document.
- Pay and open the order. Certum's purchase guide says the certificate becomes available for activation in your account once payment is received.
- Choose the variant and enter the data: Individual, Organization or Sponsor. The certificate carries what you enter here, so use the name exactly as it appears in the registry.
- Verify your identity. Certum recommends automatic verification: it e-mails a link to an identity service that uses a computer or phone camera and your ID document. The alternatives are a Certum Registration Point, a notary, or photos of you holding your ID.
- Certum verifies. If the registry cannot confirm something, Certum asks for a document. Its 2024 support article labels its range the "time of issue after verification"; the current product page does not say, so allow for both readings.
- Finish activation. Once Certum has verified you, you choose the certificate fields, generate the keys on a virtual cryptographic card in SimplySign, pick or create the SimplySign account and submit the certificate for issuance. It is installed on that SimplySign account.
Steps 1 to 3 and step 5 are not Certum's work; they move at your pace. What to gather for each variant is listed in our Certum code signing documents guide.
Why does EV code signing take longer?
EV code signing takes longer because the Code Signing Baseline Requirements ask for more evidence and Certum's EV document list is longer. Section 3.2.2.2.4 of the requirements says the CA must verify a telephone number, fax number, email address or postal address for the organization and get an affirmative response from the applicant through it. Every extra step is another wait for a reply.
Certum also lists more paperwork for EV: a utility bill issued for the organization and confirmation of a physical office, plus a power of attorney or a registration document when needed. Whether the extra days are worth it depends on what you ship. Microsoft requires an EV code signing certificate to register for the Windows Hardware Developer Program. For a desktop app, Microsoft says EV certificates no longer change SmartScreen behaviour, so a Standard certificate is often the faster purchase. If you do need EV, the EV code signing certificate page lists what Certum asks for, and the EV vs OV comparison works through the choice.
How long from "issued" to the first signature?
With a cloud certificate, the first signature can follow issuance once two apps are installed. Since June 1, 2023 the CA/Browser Forum has required every code signing private key to be generated and kept in certified hardware. Certum meets that rule for its cloud products with a virtual card in SimplySign, so nothing is shipped to you.
What you still need on your side is the SimplySign mobile app, which produces the access codes, and SimplySign Desktop, which connects your computer to the virtual card. Both are covered step by step in the SimplySign Desktop setup guide. A certificate on a physical card or USB token is different: it is not usable until the hardware reaches you, and no CA's issue time includes the courier. The cloud vs USB token comparison covers the other differences, including build servers.
What makes a code signing order wait?
A code signing order waits when Certum needs something it does not have yet. Going by Certum's activation manual and its required-documents page, that means an identity check that was never finished, a document the registry could not replace, or, for EV, a confirmation the applicant has not sent back. None of these is a rejection.
- The identity link was not used. Automatic verification starts with an e-mail to the subscriber. If it went to a shared or filtered inbox, nothing moves until someone opens it.
- The company is not in the registry Certum checks. Certum then needs a company registration document instead.
- The applicant cannot represent the company alone. A developer who is not a registered representative needs a power of attorney from someone who is.
- A utility bill is missing. Certum lists one, issued in the subscriber's name, for individual Standard and Open Source certificates, and one issued for the organization for EV.
- The details do not match the registry. A trading name entered where the registered legal name belongs gives Certum something to query.
How can you speed up code signing validation?
You cannot shorten Certum's checks, but you can make sure the order never sits waiting for you. Finish the identity check the day you order, enter your details exactly as the registry shows them, and have every document Certum lists for your variant ready before you start activation.
- Use automatic identity verification and send the link to an inbox the subscriber actually reads.
- Copy the legal name from the registry entry, suffix included (GmbH, Ltd, Inc.), rather than typing the brand name.
- Let a registered representative be the applicant, or have the power of attorney signed before you begin.
- Scan the utility bill now if your variant needs one.
- For EV, watch for the confirmation request on the phone number, e-mail or address the CA verified, and answer it the same day.
- Install the SimplySign apps while you wait, so signing can start as soon as the certificate is issued.
Do code signing renewals take as long?
Plan renewals with the same 1–5 or 1–7 days, because Certum does not publish a shorter renewal time. They also come round more often now: code signing certificates issued since March 1, 2026 may last at most 460 days, a limit the CA/Browser Forum set in ballot CSC-31, and Certum caps a single certificate at 459 days.
Certum sells two- and three-year products as a series of certificates with at least one free reissue in between, so the term you buy and the certificate you sign with are no longer the same length. Start each renewal a few weeks before expiry. That leaves room for a document request without a gap in signing. The 460-day validity guide explains what the limit means for multi-year purchases.
Updated October 16, 2026: issue times now follow Certum's current product page (1–5 days Standard, 1–7 days EV; the old page said 1–3 days for Standard and about a day for individuals); validation steps rewritten from Certum's activation manual and document list; the EV section now cites the Code Signing Baseline Requirements; unsourced courier times, callback hours and claims about our own order queue were removed. Earlier updates on October 14 and 12 corrected the product notes.
Frequently Asked Questions
Quick answers to related questions.
How long does it take to get a code signing certificate?
Certum lists 1–5 days for a Standard code signing certificate and 1–7 days for EV. The page does not say whether those are business or calendar days, or when the count starts, and an older Certum article calls its figure the time of issue after verification, so allow extra time for the checks themselves. Entering your data and verifying your identity come first, and they take as long as you take.
Can I get a code signing certificate instantly?
No. Every publicly trusted code signing certificate needs the certificate authority to verify a person or an organization, and Certum's own listed issue times start at one day. Sites that promise minutes are usually describing domain-validated SSL, which has no code signing equivalent.
How long does EV code signing validation take?
Certum lists 1–7 days for EV code signing. EV is for registered companies only, and the Code Signing Baseline Requirements add checks Standard does not have, such as a verified method of communication (phone, fax, email or post) through which the applicant has to confirm the request. Certum's EV list adds a utility bill issued for the organization and confirmation of a physical office.
Why is my code signing order still in verification?
Usually because Certum is waiting for something from you. Check your e-mail for the identity verification link, and whether Certum asked for a document: a utility bill, a company registration document when your company is not in the registry, or a power of attorney when the applicant cannot represent the company alone. For EV, check that you answered the confirmation request.
Do code signing renewals take as long?
Plan as if they do. Certum does not publish a separate renewal time, and since March 1, 2026 a code signing certificate lasts at most 460 days, so the wait comes back at least every 15 months. Start the renewal a few weeks before expiry so a document request cannot leave you without a valid certificate.
Order with the whole timeline in mind
My-SSL's Standard and EV certificates are issued by Certum and delivered to a SimplySign cloud card, so the wait ends at issuance, not at a courier. Compare the two on the code signing certificates page, and have your registry details and documents ready before you activate.