WQ3 API
Use WQ3 signing from inside your own applications and systems.
Deployment
WQ3 Cloud
A ready cloud workspace where your team prepares, sends and tracks documents for signature.
Why teams use it
Start in minutes with no installation.
Invite your team and share templates.
Start on the free plan and upgrade when needed.
Related
WQ3 Dedicated
A private environment for WQ3 that we plan with you around your requirements.
Pricing
Free, monthly, and annual Cloud subscriptions are available alongside API and dedicated deployment options.
What's included
A ready workspace
Arabic editor, templates, bulk send and reminders.
Team management
Users, roles and permissions.
Continuous updates
New features with nothing to install.
How to start
Create a free account, invite your team and send your first document for signature in minutes.
Common questions
Are the features the same in every option?
Yes. Cloud, API and Dedicated are different ways to use the same WQ3 platform.
Can we start with one and move later?
Yes. Many teams start on the cloud, then add the API or move to a dedicated environment.
Set signing requirements before sending
Start by identifying the documents your team will handle in WQ3 Cloud and the identity assurance each needs. WQ3 offers exactly three levels: electronic signature, remote signing and token signing. Electronic signature suits everyday agreements, while remote or token signing should be considered for formal or high-value contracts.
Not every participant needs the same level: you can assign a different signing level to each signer within one document. Where proving the account holder’s identity is necessary, require an eKYC-verified account alongside the chosen level. eKYC is an account-verification add-on, not a fourth signing level.
Make the pre-send review count
Establish a review checklist for agreements leaving your cloud workspace. Check the final wording, intended recipients, each person’s signing level and any account-verification requirement. This matters because WQ3 locks documents once sent, so sending should mark the end of drafting rather than another review stage.
Each signer accesses their material through an individual invitation and a private link showing only what belongs to them. Data travels over TLS 1.2 or newer, and every action is recorded throughout the signing workflow. Support these controls with practical team habits: confirm recipients before sending and direct signers to their own invitations rather than circulating another person’s link.
Prepare a record that remains useful
Decide what colleagues will need when reviewing a completed agreement, rather than treating the signature as the last administrative step. Every completed document includes an audit trail and a completion certificate, covering actions from sending to final signature. For internal record keeping, retain the final document and its completion certificate together under your organisation’s records procedures.
WQ3 also provides a public verification page accessible through a QR code and reference, without an account. It shows signer names, signature level and step timestamps, and compares the file’s SHA-256 fingerprint with the stored fingerprint to reveal changes. Direct reviewers there when they need to check a signed copy’s authenticity.
Review legal fit and data requirements
Choosing a ready cloud workspace does not replace reviewing the requirements of your particular agreement. WQ3 is aligned with Egyptian E-Signature Law No. 15 of 2004 and its executive regulations; equivalence with handwritten signatures and paper documents depends on meeting the applicable conditions. Select signing and identity requirements accordingly.
WQ3’s privacy materials address processing under Egypt’s Data Law 151/2020. Before introducing sensitive documents, review the Trust Center and identify any further information your organisation needs about hosting location, retention or internal access procedures. The compliance page also describes alignment with ESIGN, UETA and eIDAS; assess their relevance to your specific agreement.
Start your first signing journey today.
Create your WQ3 account, or talk to us about your organization’s requirements.
Frequently asked questions
Can two parties use different signing levels?+
Yes. Assign electronic signature, remote signing or token signing separately to each signer within the same document.
Do I need eKYC for every signature?+
eKYC is an account-verification add-on. Require it when your workflow needs proof of the account holder’s identity.
Can a document still be edited after sending?+
WQ3 locks documents once sent. Complete your content, recipient and signing-level checks before sending.
Does a reviewer need an account to verify a contract?+
No. The public check page works without an account; its QR code appears on the completion certificate and final file.
Where is Cloud data hosted, and how long is it retained?+
This page does not specify hosting location or retention periods. Confirm both with WQ3 before adopting it for a use case with specific requirements.