The Advanced Electronic Signature module shows the user documents to sign, collects their consent, and captures a certificate-backed electronic signature. That digital certificate verifies their identity, making the signed document legally binding and compliant.
Integrations
:white_check_mark: Web | :white_check_mark: iOS | :white_check_mark: Android
How It Works
When the Advanced Electronic Signature module runs, the end user is presented with the documents requiring their signature. The module walks the user through a structured consent flow before the signature is finalized.
By default, the module:
- Displays the documents to be signed, with an option to view each document before proceeding.
- Presents a legal consent screen with required checkboxes, collecting explicit informed consent from the user.
- Finalizes the signature using a digital certificate, ensuring cryptographic integrity and non-repudiation.
- Confirms successful signing with a success state at the end of the flow.
An Advanced Electronic Signature (AES) differs from a basic electronic signature in that it is backed by a digital certificate and requires verified identity before signing. This gives the signed document stronger legal weight and makes it suitable for compliance-driven use cases.
The module can also be configured to:
- Allow the user to upload the document they want signed.
- Allow the user to download or save the signed document after completion.
- Skip specific verification requirements, such as identity score validation, ID verification, face recognition, or one-time password (OTP).
Use Advanced Electronic Signature
For instructions on implementing and configuring Advanced Electronic Signature on each supported platform, use the following pages:
- Advanced Electronic Signature (Dashboard)
- Advanced Electronic Signature (iOS)
- Advanced Electronic Signature (Android)
- Advanced Electronic Signature (Web SDK)