title: Difference between code signing certificate and document signing certificate
body: <p>I am looking at getting a document signing certificate to sign PDFs as per Adobe's AATL however I noticed, for example that Digicert charge significantly different prices for a <a href="https://www.digicert.com/document-signing/" rel="nofollow" title="Document Signing Certificate">Document Signing Certificate</a> than a <a href="https://www.digicert.com/code-signing/code-signing.htm" rel="nofollow" title="Code Signing Certificate">Code Signing Certificate</a>. We plan to use the certificate to do automated signing of PDFs so I can't see the USB token (offered by the Document signing certificate) being that useful. Considering both certificate/private key pair as signed by the same CA: Digicert, and are on the AATL (and therefore their root cert be the same?) would using a code signing certificate be suffice to validate on Adobe readers? </p>
  
  <p>Customer support at Digicert say:  </p>
  
  <blockquote>
    <p>if you're using the certificate through your own software then a code
    signing certificate may work since it chains back to the trusted
    DigiCert root. I can't confirm whether or not the code signing
    signature will translate to a PDF however since we don't officially
    support PDF signing with a code signing certificate.</p>
  </blockquote>
  
  <p>If anyone has experience with this I'd appreciate it. </p>