What a QCDS Completed Package Contains When Attachments Are Used

When a completed Request includes signer Document Attachments, QCDS downloads a Completed Package ZIP instead of giving you only the PDF. The package keeps the verified completed document together with the protected original attachment files.

The Package Contains Two Evidence Layers

Inside the Request-specific package folder, QCDS includes:

• the current verified Completed PDF artifact for each completed Request document; and
• the retained original signer attachment files under an Attachments folder.

If a Request contains multiple completed PDF documents, QCDS includes each artifact with a numbered document filename rather than collapsing them into one file.

Why the Original Attachment Is Included

The Completed PDF contains an attachment presentation page. A field configured not to display its attachment plainly receives a privacy-obscured presentation derivative in the PDF.

The package separately preserves the protected original PNG/JPEG attachment. This means privacy presentation and evidence retention are not the same thing: hiding detail in the PDF does not erase or pixelate the authorized original evidence stored with the transaction.

Attachment Files Are Named for Records Use

QCDS gives packaged attachments deterministic record-oriented filenames built from the relevant completion/upload time, signer name, attachment number, field label, and image extension. Completed PDF/package naming likewise uses the Request title/number and the final required-signer completion moment in the Request time zone when available.

The PDF Already Carries Attachment Evidence

The Audit Trail inside the Completed PDF records each attachment's number, label, signer, upload time, whether the PDF presentation is displayed or privacy-obscured, the original filename/type/size, and the original attachment SHA-256. The separate file in the ZIP provides the original bytes that correspond to that evidence.

Packages Are Created Only When Needed

QCDS requires the Request to be completed and to contain at least one retained signer attachment before it will build a Completed Package. A Request with no signer attachments downloads its Completed PDF directly instead.

The ZIP is assembled on demand from protected artifacts, streamed as an authorized private download, and treated as temporary package output. Preserve the package in appropriately controlled records storage if your workflow requires both the final document and the original signer-supplied attachment evidence.

Community Discussion

Want to compare workflows, share practical tips, or discuss how you use this QCDS feature? Visit the QC Digital Signature Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.