Skip to content
WQ3

Features

Electronic seal

Apply your organization's seal to documents so recipients can see they were issued by your organization.

Why teams use it

Represents the organization, not an individual.

Useful for letters, certificates and official documents.

Recorded in the audit trail with the rest of the workflow.

Related

01

Certificate signing

Sign with an existing digital certificate or USB token on desktop, alongside electronic signatures.

02

USB token signing

Sign documents on desktop with a digital certificate stored on a USB token.

03

Government

Digital approval and signing workflows for public entities, with private deployment options.

Frequently asked questions

Only the users your organization authorizes. Talk to us about setting it up for your organization.

Define what the seal means in your process

Before adopting an electronic seal, document what applying it means internally: is the document ready for issue, or has a particular review been completed? A clear definition helps staff and recipients avoid interpreting the seal as approval of matters it does not cover. Your policy should distinguish authority to issue documents from authority to make commitments.

For documents that also require an individual's approval, define that person's signing requirements separately from the decision to use a seal. WQ3 allows a different signature level for each signer in the same document. Start with the decision-maker and the approval needed, then choose the appropriate signature level rather than relying on the seal alone.

Set controls before sending

Prepare a pre-issue checklist covering content accuracy, attachments, recipient details and necessary internal approvals. WQ3 locks documents once sent, making this review important before the workflow begins. If the content later needs correction, follow your organization's amendment and reissue procedure rather than treating the change as inconsequential.

Review the responsibilities of the people preparing, reviewing and issuing documents. WQ3 supports roles and permissions, while your organization remains responsible for defining each role's authority. When employees' responsibilities change, review the relevant access arrangements so your issuing process continues to reflect who is actually responsible for each decision.

Help recipients check the final file

When sharing a WQ3-signed contract bearing your organization's seal, direct recipients to verify the final file rather than rely on the seal's appearance. Every contract signed with WQ3 has a public check page accessible without an account, using its QR code or reference. QR codes appear on the final file and completion certificate.

Verification compares the file's SHA-256 fingerprint with the stored fingerprint to reveal changes after signing. Recipients can also review signer names, signature levels and the timestamps of workflow steps. These checks help assess the file's integrity and history, but do not replace reading its contents or checking the parties' authority for the transaction.

Separate seal, signature and identity requirements

A seal is not a fourth WQ3 signature level: the three levels are electronic signature, remote signing and token signing. eKYC is an account-verification add-on, and an eKYC-verified account can be required with any level. Assess the need for a seal separately from each person's signature level and account-verification requirements.

WQ3 is aligned with Egyptian E-Signature Law No. 15 of 2004 and its executive regulations; legal validity depends on meeting the applicable conditions. In the EU, eIDAS distinguishes electronic seals from electronic signatures, with requirements that vary by category. For regulated or cross-border transactions, check the recipient's requirements rather than assuming every seal has the same legal effect.

Start your first signing journey today.

Create your WQ3 account, or talk to us about your organization’s requirements.

Frequently asked questions

Can a seal replace an authorized person's signature?+

Do not assume so. Where a transaction requires personal approval or a signature, define that requirement separately and check the applicable rules.

Is eKYC required to use a seal?+

The available information does not state this requirement. eKYC verifies accounts; it is neither a signature level nor a seal category.

What should we retain after completion?+

Keep the final file, completion certificate and accompanying audit trail according to your organization's document-retention policy.

Is a seal's image enough to verify a file?+

No. For WQ3-signed contracts, use the public check page to inspect the file fingerprint and signing record rather than appearance alone.

Does a seal prove every statement in a document is accurate?+

It should not be treated as independent proof of content accuracy. Content review and required approvals remain the issuer's responsibility.