Face Verification
Address Verification
Document Verification
Age Verification
VideoIdent
Fast ID
eIDV
Consent Verification
NFC Verification
Business Verification
Due Diligence
Investor Verification
E-Signature
QES
AML Screening
Transaction Monitoring
Adverse Media
Business AML Screening
PEP & RCA
Sanctions
Watchlist
Behavioural Biometrics
Device Fingerprinting
1:1 Authentication
MFA
Fraud Hub
Onboarding
Ongoing Monitoring
KYC
KYB
KYI
Age Assurance
Identity Verification
Workforce IAM
Candidate Verification
Compliance
Fraud prevention
Trust & safety
Global expansion
Product Managers
Compliance Officers
Fraud Analysts
Developers
Deepfake
Bonus Abuse / Promotion Abuse
Account Takeover
Synthetic Identity Fraud
Document Fraud
Impersonation Fraud
Multi-Accounting
Fraud Networks
Chargeback Fraud
Money Mule Activity
Party Fraud
Regulatory & Compliance Risks
Fintech
Crypto
iGaming
Forex
Social Network
Marketplace
Banking
Gig Economy
Blind Spot Audit
Deepfake Detector
Liveness Spoofs
Document Originality
Document Deepfake
Global Trust Platform
Journey Builder
Case Management
Shufti AI
Fraud Analytics
Vendor Comparison
Brand Personalisation
IDV Modes
AI Compliance Co-Pilot
OCR
Secure Capture
Deployment Options
Identity Methods
API Documentation
Mobile SDKs
Service Status
Help Center
Contact Us
Technical Support
Supported Documents
Content library
Blogs
News
Reports
Insights
Knowledgebase
ROI calculator
About
Career
Press Release
Certifications
Partnership
Awards
Events & Webinar
Interactive Demo
Podcast Studio
Spotlight Studio
QUALIFIED ELECTRONIC SIGNATURES
QES Signing for Regulated Digital Agreements
Verify the signer, issue a qualified certificate, and apply a legally binding signature in one flow. Backed by an EU Trusted List QTSP. Supports across all 27 EU member states.
Qualified Signatures Backed by Verified Identity
Why Enterprises Choose Shufti for Qualified Signing
Cryptographic Consent & Signature Signing
A qualified electronic signature is only as strong as the consent layer behind it. If signing is not cryptographically linked to a verified identity, it holds no legal weight under eIDAS. Shufti captures user consent through OTP-based signing and Strong Customer Authentication, cryptographically stamping the verified identity to the signature event and creating a legally binding, non-repudiable record.
ETSI-Aligned Identity Proofing
Most identity verification providers don't meet the ETSI TS 119 461 standard, meaning their checks can get rejected in EU-regulated workflows before a signature is even issued. Shufti's verification engine covers document checks, MRZ analysis, and biometric face matching with liveness detection at over 99% accuracy, built to the exact standard regulators require for qualified signature flows.
End-to-End QES Flow
Stitching together separate vendors for verification, consent, and signature issuance creates gaps in compliance, accountability, and the user experience. Shufti handles the full journey including identity proofing, consent via OTP or Strong Customer Authentication, and qualified certificate issuance through certified QTSP partners, so your users move from onboarding to signing in one audit-ready flow.
From Verification to Qualified Signature
QES End-User Signing Flow
01
STEP 01
Identity Verification
The user provides consent, verifies their email via OTP, and selects the preferred verification method.
02
STEP 02
Verification Journey
The user completes the selected verification flow, including Face + Standard Document Verification, Face + NFC Verification, Existing eID Verification, or Video KYC Verification.
03
STEP 03
Signing Consent
After successful verification, the user proceeds to document signing, provides signing consent, and completes phone verification through OTP-based Strong Customer Authentication.
04
STEP 04
Complete Identity
The verified identity is validated against the required assurance level and prepared for compliant QES certificate issuance.
Single API, Seamless Integration
Build fully customisable verification flows with seamless backend integration.
- Gain full control by customising verification flows end-to-end.
- Integrate seamlessly with your backend for quick implementation.
- Design flexible verification journeys tailored to your users.
Launch a native verification experience in your mobile app within minutes.
- Launch native verification within minutes on iOS or Android.
- Use ready-made UI with camera, capture, and real-time feedback.
- Customise flows to fit seamlessly into your mobile app.
Run Shufti within your own identical-capability infrastructure for maximum data control and privacy.
- Keep all sensitive information in-house to meet strict governance and data residency requirements.
- Keep sensitive information fully private and secure in-house.
- Deploy in highly regulated sectors without compromising compliance.
Quickly launch identity verification through a secure, customisable web link, no code required. Learn more.
- Start verifying users instantly with a no-code setup.
- Deliver a consistent identity experience via a link or embedded iframe.
- Deploy quickly via a secure link or embedded iframe.
With KYC Journey Builder, create personalised verification journeys without writing a single line of code.
- Customise your journey effortlessly with drag-and-drop functionality.
- Instantly see how your verification flow looks for your users.
- Easily connect with Hosted Verification for a consistent, branded experience.
QUALIFIED SIGNATURES ACROSS REGULATED INDUSTRIES
Built for Industries That Cannot Afford Paper Delays
Marketplaces Seller Upgrades Verified, Disputes Prevented
Upgrade buyers to sellers and enable payouts without repeating KYC across the journey, even as risk increases.
Frequently Asked Questions
What is a qualified electronic signature (QES)?
A qualified electronic signature is the highest assurance level under the EU eIDAS Regulation. It carries the same legal effect as a handwritten signature across all 27 EU member states. QES requires identity verification by a QTSP, a qualified certificate, and a signature created on a QSCD.
How does QES differ from an advanced electronic signature (AES)?
AES is linked to the signatory and detects changes, but does not require a qualified certificate or QSCD. QES adds both. Only QES has automatic legal equivalence to a handwritten signature under eIDAS.
Which countries recognise QES?
A QES issued by a QTSP in any EU member state is valid across all 27 EU member states plus Iceland, Liechtenstein, and Norway. Many non-EU jurisdictions also recognise QES through bilateral agreements.
Does the signatory need software or a hardware token?
No. Shufti’s QES flow uses remote QSCD managed server-side. The signatory completes identity verification and authorises the signature through a web or mobile interface.
How long does the QES process take?
The full flow typically completes in under 90 seconds for returning users and under 3 minutes for first-time signatories, depending on the identification method and jurisdiction.
What happens under eIDAS 2.0 and the EUDI Wallet?
eIDAS 2.0 requires every EU member state to offer a European Digital Identity Wallet by December 2026. Shufti’s QES infrastructure is designed to accept EUDI Wallet credentials for certificate issuance.
Can QES be used for multi-party agreements?
Yes. Shufti supports sequential multi-signatory workflows where each party completes their own identity verification and applies a separate qualified electronic signature with individual timestamps and evidence chains.
Ready to Add Qualified Signing to Your Verification Flow?
Verify the signer, issue a qualified certificate, and apply a legally binding signature in one flow. Talk to our team to see how Shufti fits your onboarding and signing journey.
Sandbox in 24 hours · No contract required · 14-day parallel run on switch