Qualified Signature
Qualified Signature is a key step in onboarding and agreement workflows. It presents users with a document to review and a set of legally required consent statements to confirm before completing the signing process.
Where it fits in the flow
Qualified Signature is typically positioned after face capture, ID capture and OTP verification, after identity and document checks have been completed, depending on the configured workflow.
User Flow
The Qualified Signature experience guides users through Terms and conditions, review and sign, and creating the signature.
Full Flow Map
Happy Path (Light & Dark)
The ideal user journey occurs when the user accepts the terms and conditions, reviews the document, accepts the terms and conditions again, creates the signature, and reaches the success screen without interruptions.
The happy path represents the smoothest version of the experience: the user accepts the terms and conditions, opens and reviews the contract, accepts the terms and conditions, creates the signature, and the system processes and confirms it. The user reaches the success screen on the first attempt without encountering any errors.
Light and dark mode previews are included to allow teams to validate visual consistency, accessibility, and contrast across themes and platforms.
Light mode
Dark mode
Best Practices
Best Practices for Designing and Implementing the Qualified Signature Experience
✅ Do
- Display the full contract or document with a clear link to open and read it before signing.
- Require each consent checkbox to be checked individually before the "Finish signing" button becomes active.
- Keep consent statements concise, specific, and easy to understand.
- Provide clear visual feedback during processing to prevent duplicate submissions.
❌ Don't
- Don't allow the "Finish signing" button to be tapped unless all checkboxes are checked.
- Don't allow duplicate submissions by leaving the button active while the signature is being processed.
Updated about 1 month ago