Publisher Identity

Add your verified organization name to the seal; we manage CA/RA validation, renewals, and revocation. Works with Publisher - Trusted PDF Sealing. Recipients see the blue Certified banner in Adobe/Reader.

AATL eIDAS EUTL-recognized

Publisher Identity - AATL or EU Advanced OrgIDs

Choose the trust path that fits your reviewers: AATL OrgID (Adobe trust ecosystem) or EU Advanced OrgID (eIDAS Advanced/AdES for PAdES). Works with Publisher — Trusted PDF Sealing; includes the organization certificate and full lifecycle management.

Find your fit

Which Identity add-on is right for you?

Choose the right trust path for your business

Learn more →

Provided by Publisher

Included in monthly subscription

Learn more →

AP/Invoices

Accounts payable and invoice processing

Learn more →

Bids

Proposal and bidding processes

Learn more →

Compliance

Regulatory and compliance requirements

Learn more →

Your Name in the Seal, We Manage the Rest

Publisher Identity Add-ons give your organization a verified OrgID on the trust path your reviewers accept (AATL or EU Advanced/eIDAS). Requires Publisher for sealing; this service manages identity and certificate lifecycle.

Equip your organization with a standards-aligned OrgID, without burdening your technical team with certificate procurement or lifecycle management. We coordinate identity vetting with the CA, issue on the right trust path - AATL or EU Advanced under eIDAS, and manage renewals and revocation.

Use it with your existing Publisher automations. Your sealing automations, permissions and time-stamp settings (CLI/API/Zapier) stay the same — Identity only changes the content of your seal, not your workflow.

Why add your own OrgID: Make your legal entity the verified source of truth. Counter fraud at the document level, cut exceptions and callbacks, and meet policy/RFP language without adding a portal or changing workflows. Verification stays portable and exception-based in Acrobat/Reader.

If a partner asks you to seal PDFs, they may also require that you use your own OrgID —not a shared portal identity. The reverse is true, too: if you require sealed PDFs from vendors or customers, you can (and should) request they use their own OrgIDs.

This creates a mature document supply chain: each party signs as itself, so provenance and integrity are verifiable on open in Acrobat — no portals, no phone calls. And fraud detection stays focused on execptions management.

When each party signs as itself, provenance is obvious on open in Acrobat—no portals, no follow-ups. Resulting in fewer disputes, faster approvals, and audit-ready evidence.

What’s Included

  • Onboarding & validation: We coordinate CA/RA checks and evidence.
  • Certificate issuance & renewal Life-cycle handled end-to-end (white-labeled CA provider).
  • Key protection: FIPS 140-3 Level 3 HSM-backed custody.
  • Incident response: Compromise playbooks with CA provider coordination.
  • Admin controls: Manage authorized contacts and access; define who can issue/renew/revoke. We retain certificate and status logs and can furnish them via support or API.
  • Support: Implementation guidance.

Acronym Explainers

(click to expand)

X.509
ISO 32000
eIDAS/ETSI
PKI
FIPS 140-3
HSM
OCSP/CRL

Frequently Asked Questions

How do we make Acrobat show our organization as the signer?
Add Publisher Identity (AATL or EU Advanced) to your sealing service and your validated organizational name will be presented in Acrobat’s signature panel. Verify anytime with our PDF Validator.
What’s required to issue my Publisher Identity OrgId certificate? Can I bring my own?
Standard organization verification (e.g., legal entity checks and domain/account controls per the CA’s policy). We’ll guide you on what to provide based on the issuer aligned to your chosen trust path. We manage issuance and custody for security and lifecycle (no BYO).
Does using an Identity add-on change our workflow?
No—Publisher keeps your automations (CLI/API/Zapier); the add-on supplies the organizational Digital ID which changes the content of the seal. We associate your account with your AATL certificate on the backend. Optional: you can add keys to align to multiple certificates, or continue to use TS’s EU Advanced certificate for situations where you need it but do not want your organization’s name to appear.
How is EU Advanced OrgID different from AATL OrgID?
AATL OrgID targets Adobe’s trust path globally. EU Advanced Org ID targets the EU trust framework (EUTL) for AdES. Many recipients will see both paths validate in Acrobat; EU Advanced focuses on eIDAS recognition.
Do you offer a Qualified Electronic Seal (QSeal) as defined by eIDAS?
No— Publisher Identity - EU Advanced OrgID add-on provides Advanced (AdES) organizational seals. Qualified seals (QSeal) are not available.
How is pricing structured for Publisher sealing and Identity add-ons?
Publisher (sealing) is a usage-based sliding scale subscription. Identity (OrgID) — AATL or EU Advanced—is an annual add-on with rate breaks for multi-year terms. Identity can only be used with a Publisher service.
What if the certificate expires or is revoked?
We manage renewals. With LTV enabled, previously sealed PDFs remain verifiable based on time-of-signing evidence.
Can I have multiple org certificates (departments, brands, subsidiaries)?
Yes - you can have multiple organizational IDs and even different trust paths associated with your Publisher sealing account. You would associate specific API keys to the desired OrgID. Contact us for assistance.
Does Product Identity change compliance or LTV behavior?
Seals remain PAdES-compliant; enabling LTV/time stamping in your Publisher configuration preserves long-term verifiability even if a certificate expires or is revoked. AATL and EU Advanced options ensures Adobe trust recognition globally.

Trust & Standards

Publisher seals PDFs using Adobe-aligned standards (ISO 32000/PDF). Each sealed file can include an organizational X.509 certificate and chain, RFC 3161 trusted timestamp, and OCSP/CRL revocation data. By default this certificate is a Trusted Signatures OV certificate; timestamp and revocation embedding are optional (for LTV). You can set DocMDP permissions to allow specific post-seal changes (e.g., form-fill) without breaking certified status. Seals validate natively in Adobe Acrobat/Reader (blue "Certified" banner), and you can also check documents with our web Validator. Publisher Identity. We procure and manage your organization’s X.509 certificate via an Adobe-recognized CA (AATL) or an EUTL-listed provider for eIDAS Advanced (AdES) trust paths for PAdES. The CA vouches for your organization’s identity—while how the file is sealed stays the same.