Documentation Requirements

A code signing certificate is an identity certificate. Because of that there is a validation process through which you will have to prove to Sectigo that you are who you say you are.  It is important to note that every order is validated individually and that on some orders the documentation required might vary from the list below. The Sectigo validation team and the K Software support team will help you every step of the way. 

While someone at K Software is always available to answer questions, those questions directly related to validation are best answered by Sectigo as they have the final say (but please don't hesitate to reach out to K Software too!). You can reach their validation team at this link for pre-order support. The fastest way is to place your order first so that they can see all of the details up front. 

Remember, all orders are guaranteed with the best refund policy in the industry - you can order completely risk free. If you don't get your certificate (or don't want it after you do within a reasonable amount of time), you get a refund. Get the details here.

EV Code Signing Certificates are validated using the same standards as OV certificates for the most part. This is mainly due to Sectigo having already implemented the verification processes for OV certificates before the EV certificates were available -- that is why Sectigo's certificates are still trusted and so many other certificate authorities have been distrusted (Symantec, WooSign, StartCom, etc). If you already have an OV code signing certificate, most of your documentation can be re-used for an EV code signing certificate. The exception is individuals -- EV certificates cannot be issued directly to an individual person, there has to be a business entity (though that entity can be a sole proprietorship, it has to be registered as such).

Here are a few things you should know to help the validation process go smoothly :

• Use your legal name.

  When filling out the order form make sure you put your legal name in the Publisher Name field. Your legal name can be your personal name if you're ordering individually or a company name if you have a registered company. DBA (Doing Business As) companies can get a certificate in the business name if the name is registered. You will have to provide documentation that shows the business name and address. Documents like bank statements, phone bills and utility bills can be used for that purpose. 

  If you are ordering a code signing certificate in a registered company's name you'll be asked to provide one or more of the following :

  • Articles of Incorporation/Organization
  • Business License
  • DUNS details (e.g. your Dun & Bradstreet company number, if you have one)
  • A list of acceptable business documentation from all countries can be found at the bottom of this article.
  • Government-issued ID for the admin contact (to verify you're authorized to order for the company).

• If you are ordering a code signing certificate as an individual (the publisher name being your name), you'll be asked to provide some the following :

  • Copy of a valid driver’s license or passport *that includes an address*
  • If you do not have an address on your ID, you will also be asked to complete the "face to face" verification documented in the Sectigo Support Center here - that does require a notary, CPA or attorney to attest to your identity.
  • There is NO phone requirement for individuals any longer.

• Getting a DUNS number is free and fulfills the requirement for a phone listing (provided your phone number is listed with your company information). US customers can visit the Dunn & Bradstreet registration page and click on the "Get a DUNS Number" button at the bottom left. Non-US customers can contact their local D&B office through the Dunn & Bradstreet service center page. They have a number of paid services but their free level of registration is all you need to get a DUNS number.

Acceptable Documentation from Various Countries (**This is not a complete list, it's meant only as a guideline) :

** Please note, there are other documentation that can qualify. If you have any questions regarding validation or documentation, please contact Sectigo using their support ticket system at this link.