Contact

API inquiry

Access to the WQ3 API and embedded signing.

Start free Contact us

What happens after you send your message

The WQ3 team reviews your message and replies by email as soon as possible on business days.

We review it

Your request goes to the right team based on the topic you chose.

We get in touch

We reply by email or phone to understand your needs and agree the next step.

We propose a fit

A quote, a walkthrough session or an integration plan, depending on your request.

Helpful details to include

The kind of documents you sign, roughly how many users, the systems you want to connect, and any legal or security requirements your organisation has.

Define the boundaries of embedded signing

Start with the point where a user moves from your application into signing, and what they should see when finished. Identify who prepares the document, who signs it, and whether those roles overlap. This separates your intended user experience from implementation details that need confirmation.

Ask specific questions about authentication, document handoff, and displaying signing status within your application. Treat these as requirements to discuss, not confirmed API capabilities. Avoid building your implementation plan around assumed endpoints, SDKs, or notification mechanisms.

Map requirements to each signer

Prepare a signer-by-signer policy rather than assuming one signature level for every user. WQ3 has exactly three levels: electronic signature, remote signing, and token signing, with different levels possible for signers on the same document. Ask how those choices can be represented in the proposed integration.

Keep identity verification separate: eKYC is an account-verification add-on, not a fourth signing level. If your process requires a verified account, identify which signers need it and when that requirement must be met. This keeps signature strength and identity verification distinct in the integration discussion.

Plan for evidence after signing

An integration discussion should cover the records needed after signing, not just the signing screen. WQ3 provides an audit trail and completion certificate for completed documents, alongside tamper-evident final files. Identify the evidence your reviewers need, then ask which retrieval methods are available for your integration.

Consider later verification too. WQ3's public check page supports account-free authenticity checks using a QR code and reference, while the SHA-256 fingerprint helps reveal file changes. Discuss where users should find those references within your own record-keeping process.

Set acceptance criteria before implementation

Turn the desired user journey into a short acceptance checklist. Define what counts as completed signing, how your operations team should identify unfinished documents, and which records must remain available for internal review. Then request confirmation of what the proposed API workflow can support and what needs separate handling.

Keep legal review distinct from technical acceptance. WQ3 is aligned with Egyptian E-Signature Law No. 15 of 2004, but legal validity depends on meeting applicable conditions. Ask your legal adviser to assess the intended use while your technical team confirms that the workflow preserves the required evidence.