Skip to content
The contract journey, step by step

How Wthaiq works: from the document
into a signed, authenticated contract.

This page explains what actually happens at each step, not general promises. You will find the creator's path, preparing the contract and sending it, and the signer's path, receiving the link and signing, then what is computed and stored technically behind the scenes: the verification code, the audit trail and the HMAC-SHA256 / SHA-256 fingerprint that exposes any change to the contract after signing.

Start your first contract Read the steps
The creator’s path The signer’s path Types of path Signature levels What happens technically How long it takes Before you begin Objections answered
What you receive at the end
1Final PDF copy Sealed after the last signature
2Completion certificate with each signatory’s details and verification method
3A timestamped event log For every step in the contract
4HMAC-SHA256 fingerprint for the document, revealing any change to it
5A verification reference and a QR code to a public verification page
HMAC-SHA256 (illustrative example): 9f2a1c7e…b4d8e6ff
Whatever your starting point, the path is the same

Six stages —
each one hands over to the next

Whether you start with a contract you write yourself, a template you saved, or a PDF you upload, you then go through the same six stations.

CreateYour contract, your template or a PDF
Fill inData and fields for each party
Set the partiesand the signature level for each party
SendA signing link for each party
Sign and verifyA code, an identity check or a token
Authenticate and trackA certificate, a fingerprint and public verification
First path

The creator's journey:
Six numbered steps.

You are the party who prepares the contract, sends it and tracks it. Here is what you do, in order, and what you get at the end of each step.

Step one · Creation

Choose your starting point

You never start from a blank page unless you want to. There are three ways in: write your own contract in the professional editor with AI assistance, start from a template you saved in your account, or upload a PDF file you already have. All three routes complete the same authenticated journey; the only difference is preparation time — not the strength of the contract that comes out of it.

Saved templatePurpose-built editorPDF upload
The result: A contract draft inside your account with its own document number.
Step two · Filling in

Fill in the data and set the fields

Write the details you already know into the contract text: the parties' names, the value, the term and the effective date. Whatever someone else must fill becomes a field: type @ in the editor or drag the field into place, then assign it to its owner — such as the other party's signature, ID number and date of acknowledgement — and they fill it in themselves at signing. And if you start from a PDF, you drag the fields onto the page and place them exactly.

Drag and dropFields assigned to each partyMandatory fields
The result: A contract with every detail filled in, and a clear field map for each party.
Step three · Parties

Add the parties and choose the signature level

Add each signer by email, then choose the verification level that suits their role: an electronic signature with an OTP code for everyday contracts, identity-verified signing for sensitive transactions and for parties you are dealing with for the first time, or token-based signing with its accredited certificate when the receiving authority requires the highest level. The level is set for each signer separately — a manager can sign with a token while a supplier signs with an OTP code on the very same contract.

One signer or moreA level for each partyReview before sending
The result: A list of signers, each with the verification method required of them.
Step four · Sending

Send the signing link

As soon as you send, each party receives their own signing link by email. The link requires no account and no app from the recipient, and works on phone or computer. From the moment you send, events start being recorded: who it went to, when, and its current status — all visible to you in the dashboard.

A link for each partyNo account for the recipientWorks on a phone
The result: A contract in "awaiting signature" status, and an event log that has started running.
Step five · Follow-up

Track each party’s status

The dashboard shows the status of every contract — draft, awaiting signature, signed — and who has signed and who has not yet. Tracking here is not an administrative luxury: it is what tells you the delay is because a party has not opened the link, not because something is wrong with the contract. And you can set a reminder date for any contract, so renewal alerts reach you before that date and no supplier or tenancy contract runs out without anyone noticing.

Live statusEffective dateRenewal alerts
The result: A clear picture of where every contract stands, with no chasing by email.
Step six · authentication

Receive the authenticated copy

After the last signature the contract is sealed, and you receive a final PDF, a completion certificate carrying the signers' details, how each of them was verified and the signing times, a timestamped event log, and a fingerprint HMAC-SHA256 / SHA-256 fingerprint of the document (the former for platform contracts, the latter for uploaded PDFs), and a QR code and verification reference leading to The public verification page. From that moment, any change to the stored contract alters its fingerprint and the verification page exposes it — which is what makes denying the contract difficult. What the certificate contains is set out on the E-signature certificate.

Completion certificateHMAC-SHA256 / SHA-256 fingerprintQR code for verification
The result: A signed, authenticated contract that anyone can verify at any time.
The second path

The signatory’s experience —
the other party

Whoever receives the contract does not see what you see. Their experience is shorter and simpler: a link, a review, a verification, a signature. Understanding it saves you half the questions you would otherwise be asked.

1 Receives

A link to their email

They receive an email in your name containing a signing link that is theirs alone. No account, no password, no app to install.

2 reviews

It reads the whole contract

They open the document on a phone or a computer and read it in full before doing anything, with the fields required of them clearly marked.

3 verifies

Proves they are who they say they are

According to the level you chose: entering a one-time code (OTP) sent to them, identity verification with an official document and a live face check, or signing with a token and its certificate.

4 Signs

They place their signature

They draw their signature in the space provided and fill in only the fields assigned to them — they cannot change the contract text.

5 is reassured

receives their copy

They receive the authenticated copy and can later confirm its validity themselves on the public verification page, using the verification reference or the QR code.

A practical tip: What unsettles the other party is rarely the technology — it is an email they were not expecting. So send them a short note saying you have sent the contract for electronic signature and that the link will arrive from Wthaiq. If they want further reassurance, ask them to open The verification page after signing, to see the document authenticated for themselves. For more on use cases in shipping, HR and law firms, see How we help.

Choose your starting point

Four paths,
and one authenticated ending.

The paths differ in where they start and how many parties are involved, but they meet at the same seal: a completion certificate, a fingerprint and an audit trail.

A template saved in your account

You save a contract you wrote in the editor as a template with its fields, then start from it each time and fill in the new party's details, and the contract is ready to send.

When do you use it? A recurring contract you use with different parties: employment, lease, services, supply, confidentiality.

A custom contract you write

Write in the professional editor from scratch or import a Word file, and let the AI help you strengthen the drafting and order the clauses.

When do you use it? A non-standard agreement, or terms you negotiated that no template covers.

Upload a PDF for signature

Is your document final in its approved form? Upload it as it is, drag the signature and data fields onto it and assign each field to its owner.

When do you use it? A document your lawyer prepared, or one that reached you from the other party, whose text may not be changed.

Multi-party signing

A contract with more than one signer? Each party receives their own link and signs from their own device, and the dashboard shows who has signed and who has not yet. The final seal and the completion certificate are issued only after the last signature.

When do you use it? Several partners, or a contract needing the employee, their manager and HR to sign.

The rule for choosing: Start from a ready-made template if the contract is standard — faster and less prone to slips. Move to the custom editor if you have negotiated specific clauses. And upload a PDF if the wording is locked and must not be touched. In all three cases, the signature level is set independently of the route. See FAQ If you are on the fence.

You choose

Three signature levels,
according to how important the contract is.

The greater the contract's value or the more sensitive your dealings with the other party, the higher the level you should choose. The level is set for each signer separately.

Electronic signature

The signer draws their signature and confirms it with a verification code (OTP) sent to them, and the successful verification is recorded with its time in the audit trail.

Suitable for: Everyday contracts and quick agreements with parties you know.
Verification level: basic

Signing with ID verification

Before signing, the signer is verified with an official document and a live face check, so their identity is confirmed — not merely an email address they happen to own.

Suitable for: Sensitive transactions, and parties you are dealing with for the first time.
Verification level: advanced

The accredited signing token

A digital signature with an accredited certificate held on the token, embedded inside the file under the PAdES so it becomes part of the document itself.

Suitable for: Official documents and bodies that require an accredited signature.
Verification level: highest
Behind the scenes

What happens technically
at every step?

What you see on screen is only the surface. This table sets out what is computed or verified at each step, and what is recorded and stored at that point — because the strength of an electronic contract comes from that record, not from a picture of a signature.

Note: transmission between your browser and the platform runs over TLS 1.2+, and every document has a digital fingerprint (HMAC-SHA256 for platform contracts, SHA-256 for uploaded PDFs) that reveals any modification. You will find more details on the page Trust and security.
StepWhat is computed or verifiedWhat is recorded and stored
Create the document Generating a unique document number that distinguishes the contract from any other. A digital fingerprint of the document (HMAC-SHA256 for platform contracts, SHA-256 for uploaded PDFs), the moment of creation, and the account that created it.
Setting the fields and the parties Tying every field to its owner, and checking that mandatory fields are complete. The field map and positions, the list of signers, and the signature level required from each party.
Sending for signature Generating a signing link unique to each party that works for no one else. An “sent” event in the audit trail: recipient, timestamp and the contract’s new status.
Opening the link and reviewing the contract The link's validity and its binding to the right document and the right party. The opening event with its timestamp and IP address — which is what later proves the contract was genuinely shown before it was signed.
Verifying the signer's identity Sending a verification code OTP and matching it on entry, or checking the official document and the live face match, or verifying the accredited certificate on the token. The verification method used, its result and its time — tied to that specific signer.
Signature position Fixing the signature in its designated place and preventing any change to the contract's text. At token level, a digital signature is embedded under the PAdES inside the file. A signing event for each party with its time, and the field values that party entered.
Sealed after the last signature Fingerprint computed HMAC-SHA256 / SHA-256 fingerprint of the document (the former for platform contracts, the latter for uploaded PDFs), a string that stays the same as long as its content is unchanged, and changes completely if a single character of it changes. The fingerprint, the completion certificate, the full event log, the QR code and the verification reference.
Public verification later on Matching the verification reference or the QR code against the record stored on the platform. The status and validity of the document are shown on The verification page without revealing the contract’s contents and with no account required.

Why does the digital fingerprint matter?

The fingerprint is a string calculated from the document’s content itself. If a single zero is added to the value of the stored contract, a line is moved, or a page is swapped, the fingerprint changes completely and no longer matches the stored one. That turns “is this the contract I signed?” from an argument into a check the verification page performs.

What is inside the signing certificate

Why does the audit trail matter?

A signature on its own is just an image; what gives it weight is everything around it: when the contract was sent, when it was opened, from which address, how the signer was verified, and when they signed. That sequential timeline is what any authority examining the contract will look at. The legal framework is set out in detail on the Compliance.

How we protect your data
Actual timing

How long does the journey take?

Facts, not promises: the part you control is measured in minutes, and the part you don't is how fast the other parties respond. The authentication, though, waits for no one.

Preparing the contract on your side

Minutes: choose the template or upload the file, fill in the data, add the parties, send. A ready-made template is the fastest way in; a custom contract takes as long as drafting and reviewing it.

Waiting on the parties

This is the biggest variable and it does not depend on the platform: when the other party opens their inbox, and when they find time to review the contract. The link reaches them instantly, and the signing itself takes them no more than a few minutes.

Authentication and sealing

Immediate once the last signature lands: the fingerprint is computed, the completion certificate is issued, and the contract becomes publicly verifiable straight away — with no waiting and no manual review.

The usual paper cycle

  • Printing two copies and putting the annexes in order.
  • Sending a courier or a shipping company, then waiting for delivery.
  • signing, then sending the other copy back the other way.
  • Filed in a cabinet, then searched for by hand when needed.
  • No reliable record of who received it, when, or who opened the document.

The cycle at Wthaiq

  • Prepare and send from where you are, with no printing.
  • A signing link reaches every party instantly.
  • Signing from a phone or a computer, at any time.
  • Automatic archiving and search from the dashboard.
  • A full timestamped audit trail for every event in the contract.
Fast to get going

What you need
Before you begin?

Gathering these items before you sit down at the screen turns preparation into a matter of minutes, and prevents the most common cause of stalled contracts: a contract sent, then found to contain a mistake.

The correct legal namesThe company name as it appears in its commercial register, or the individual's name as it appears on their ID — not the name everyone uses in conversation.
Each signer's emailA working email the person opens themselves, not a general department inbox that may be ignored. And their phone number if you are going to require code verification.
The contract's essential detailsValue, payment method, term, effective date, and each party's core obligations.
The file, if it is readyA final PDF or Word version if you are going to import it, along with the annexes that must be attached to the contract.
Choosing the signature levelDecide in advance what suits each party: a verification code, identity confirmation, or an accredited token? That turns on the value of the contract and on who will receive it.
The token to hand if you chose itIf the level required is a token signature, make sure the token and its certificate are within the signer's reach at signing time.

You do not need: Technical expertise — no software to install and no servers to set up; and no account for the other party — they sign straight from the link. And if you would like to read up on the legal concepts before your first contract, start with Resources or Blog.

Legitimate objections

The questions people ask
before your first contract.

These are not marketing questions — they are the objections that actually get raised in meetings, with straight answers.

Are electronic signatures legally recognized in Egypt?

Yes — electronic signatures are governed in Egypt by Electronic Signature Law No. 15 of 2004 and its executive regulations. But recognition is not unconditional for any form of signature: its strength rests on proving the signatory’s identity, the integrity of the document, and the link between the two. That is why the journey is built on explicit verification levels, an audit trail and a document fingerprint — not on a drawn signature alone.

The legal framework and its requirements are set out in detail on the Compliance and the legal framework.

The other party does not trust electronic signatures — how do I convince them?

Do not argue it in theory; give them something to check for themselves. Send them the authenticated copy with the completion certificate, and ask them to open The public verification page and enter the verification reference or scan the QR code. They will see the document's status and validity without creating an account and without the contract's content being revealed. Something that can be verified in one click convinces more than any explanation.

What if a party denies that they were the one who signed?

This is where what is recorded behind the scenes proves its worth. Every contract carries a timestamped event log showing when the link was sent and to whom, when the document was opened and from which IP address, and when the signature was placed. It also shows how the signatory was verified: a verification code, identity confirmation with an official document and a live face match, or an accredited certificate on a token. The higher the verification level you choose, the weaker any later denial becomes.

Can the contract be altered after signing without it being detected?

No. After the last signature, a HMAC-SHA256 / SHA-256 fingerprint of the document (the former for platform contracts, the latter for uploaded PDFs) is computed and stored. Any change to its content (a number, a word, a page) produces a completely different fingerprint that does not match the stored one, so the verification page reveals it immediately. At the token signing level, the digital signature is embedded in the file itself using the standard PAdES.

Does the other party need an account or an app to sign?

No. They receive their own signing link by email, open it on a phone or a computer, review the contract, verify themselves by the method you chose, and sign. No account, no password, no app. That alone removes half the resistance you meet from suppliers and clients.

And what about my data and the content of my contracts?

Transfer takes place over TLS 1.2+, every document has a digital fingerprint (HMAC-SHA256 for platform contracts, SHA-256 for uploaded PDFs) that reveals any modification, and the public verification page shows the document's status and validity without revealing its content. In Egypt, the processing of personal data is governed by the Personal Data Protection Law No. 151 of 2020. Details on the page Trust and security.

My contract needs more than two signers — is that supported?

Yes. You add all the signers, each receives their own link and signs from their device in their own time, and the dashboard shows who has signed and who has not. The contract is not sealed and the completion certificate is not issued until every signature is in — so there is no half-authenticated copy.

What if I already have the document and do not want its wording changed?

Upload it as a PDF exactly as it is. It will not be retyped and its text will not be touched; all you do is drag the signature and data fields onto the page and assign each field to its owner. The document stays as your lawyer drafted it, and gains the whole authentication layer in return: identity verification, the event log, the fingerprint and the verification page.

Can I go back to the contract years later?

Your contracts are stored and archived in the dashboard with their status and effective dates, and you can download the authenticated copy at any time. For contracts that carry a reminder date you receive renewal alerts before that date. And to verify any copy later, all you need is The verification page using the verification reference or the QR code.

After the "how" comes the “why it holds”

Complete the picture

This page explains how the contract journey works; the pages that follow show what the contract rests on and why it holds.

E-signature certificateWhat is inside the certificate and how to read its fields. Compliance and the legal frameworkThe regulatory basis for electronic signatures in Egypt. Trust and securityThe encrypted connection, the audit log, and data protection. Verify a documentCheck any contract's validity with its verification reference or QR code. How we helpPractical applications in shipping, law and HR. FAQShort answers on usage and your account.

Start the journey
on a real contract.

The fastest way to understand the journey is to go through it yourself once: write your contract or upload your file, add a party, and watch the audit trail build up in front of you.

Start your first contract See the plans and pricing