Product
Prepare, send, sign, automate, manage and integrate document workflows in one WQ3 platform.
Resources
Resources
Everything you need to understand and start with WQ3: signature levels, contract verification, security, developers and common questions.
Related
Features
Explore WQ3 features for signing, documents, workflow, security, digital trust, teams and developers.
Trust Center
How WQ3 approaches security, privacy, digital signatures and the audit trail.
Frequently asked questions
One platform to prepare, send, sign, approve and manage digital document workflows.
Yes. WQ3 is designed for Arabic and English.
Three ways to use the same WQ3 platform.
Start here
Signature levels
Compare electronic, remote and token signing, and what each proves in law.
Contract verification
How anyone can check a signed contract with a QR code or reference number.
Trust Center
Security, privacy, audit trail and legal compliance.
Developers
A REST API to create documents, send them and download signed copies.
Pricing
Monthly and annual plans, starting free.
More questions
Is an electronic signature legally binding in Egypt?
Yes. E-Signature Law No. 15 of 2004 recognises it when its conditions are met.
Does the other party need an account?
No. Each signer gets a private link and can sign from any browser.
What is eKYC account verification?
An add-on that digitally verifies the account holder's identity with a live face match.
Can I upload Word files?
Yes. Upload a PDF or import Word and keep its layout.
How do I check a signed contract?
Scan the QR code on the certificate or enter its reference on the public check page.
Start with the decision you need to make
Before browsing, identify whether you are choosing a signing method, reviewing a completed file, or assessing an organisational workflow. For document preparation, write down each signer's requirements rather than assuming everyone needs the same signature level. WQ3 lets you assign different levels to signers within one document.
For everyday agreements, begin with the electronic signature guide; for formal or high-value contracts, review remote and token signing. If account-holder identity is central to your review, also consult the eKYC account-verification guidance. This separates the choice of signing level from the requirement to verify identity.
Read each piece of evidence for what it proves
When reviewing a completed document, distinguish file integrity, the sequence of actions, and signer identity. Verification compares the file's SHA-256 fingerprint with the stored fingerprint to reveal changes, while the audit trail explains who acted and when. These are complementary forms of evidence, not interchangeable answers.
Read the completion certificate alongside the audit trail rather than relying only on the visible signature. For internal review, keep the final copy and certificate together, and check that signer names, signature levels and event sequence match the intended process. If a result is unexpected, first confirm that you are reviewing the correct final file before treating it as verified.
Turn trust resources into review questions
Use the security, privacy and audit-trail resources to build a focused review checklist. Ask who should access each document, what identity checks are needed, and which records your organisation must retain after completion. Map those questions to WQ3's stated controls: roles and permissions, individual invitations, document locking after sending, and action recording.
For legal review, treat alignment with laws as a starting point for assessment, not a blanket guarantee for every use. The compliance resources cover Egypt's Personal Data Protection Law No. 151 of 2020 alongside electronic-signature frameworks in Egypt, the United States and the European Union. The relevant framework depends on the transaction, parties and applicable legal conditions.
Prepare a clear brief before implementation
Before opening developer resources, describe the workflow in terms both business and technical teams can understand. Identify the document to create, intended recipients, each signer's required level, and what your team needs after completion. This keeps the signing decision separate from the technical details used to implement it.
Next, map document creation, sending and signed-copy retrieval to the REST API guide. Record additional workflow questions rather than assuming every platform feature is available through the API. Before rollout, agree internally how the final file, completion certificate and audit trail will be reviewed, so the outcome supports both implementation and record keeping.
Start your first signing journey today.
Create your WQ3 account, or talk to us about your organization’s requirements.
Frequently asked questions
Must all signers use the same signature level?+
No. WQ3 allows different levels for different signers in the same document, according to the contract's requirements.
Does eKYC replace a signing level?+
No. It is an account-verification add-on usable with any of the three levels: electronic signature, remote signing and token signing.
Does a matching fingerprint prove everything about a contract?+
It establishes file integrity against the stored fingerprint. Identity, process history and legal conditions require their respective evidence.
What should I gather for an internal review?+
Bring together the final document, completion certificate and audit trail so reviewers can assess both content and signing evidence.
Does legal alignment automatically make every transaction compliant?+
No. Alignment describes the approach; the legal conditions applicable to the particular transaction still need assessment.