E-Signatures
Collect legally binding electronic signatures with complete audit trails. Support for both simple e-signatures and Qualified Electronic Signatures (QES) for maximum legal validity in the EU.
Dropie's e-signature system is designed for legal defensibility. Every signature includes comprehensive forensic evidence including device fingerprinting, IP tracking, and timestamp verification.
Key Benefits
- Legally binding in US, EU, and most countries worldwide
- Complete audit trails for every signature
- eIDAS-compliant Qualified Electronic Signatures (QES)
- No software installation required for signers
- Multi-party signing with sequential or parallel workflows
Signature Types
Simple Electronic Signature
Standard e-signature with device verification and audit trail. Legally valid for most contracts and agreements.
Legal basis: Valid under ESIGN Act (US), eIDAS (EU), and similar laws
Best for: Standard contracts, Internal agreements, Most business documents
Qualified Electronic Signature (QES)
Highest level of legal validity in the EU. Uses government-issued eID cards via Autogram integration.
Legal basis: Article 25 of eIDAS Regulation
Best for: High-value contracts, Legal proceedings, Government submissions, Cross-border EU transactions
Key Features
Multi-Party Signing
Support for multiple signers on a single document. Configure sequential (one after another) or parallel (all at once) signing order.
Forensic Evidence Collection
Comprehensive evidence package including device info, IP address, browser data, and signature timing.
2FA Verification
Require email verification before signing. SMS 2FA available on Business tier and above.
Workflow Integration
Automatically request signatures as part of workflows. No manual follow-up needed.
No Account Required
Signers don't need to create a Dropie account. They receive a secure link to sign.
Mobile Signing
Fully responsive interface. Sign documents on any device with touch support.
The Signing Experience
What signers experience when they receive a signature request
For External Signers
Receive Email
Signer receives an email with a secure link and explanation of what they're signing.
Verify Identity
If 2FA is enabled, signer verifies their email address (or phone for SMS 2FA).
Review Document
Signer can scroll through and read the entire document. Required fields are highlighted.
Sign
Signer can draw their signature with mouse/finger or type their name. Add initials if required.
Confirm
After signing all required fields, signer confirms and submits.
Receive Copy
Signer receives a copy of the signed document via email.
Tutorials
Tutorial: Sending Your First Signature Request
Step-by-step guide to collecting your first e-signature
Upload the Document
- •Log into your Dropie dashboard
- •Click 'Signatures' in the left sidebar
- •Click 'New Signature Request'
- •Upload the PDF document that needs to be signed
- •Give the request a name for your reference
Add Signature Fields
- •The document editor opens with your PDF displayed
- •Click 'Add Signature Field' from the toolbar
- •Click and drag on the document to place the signature area
- •Position it where you want the signature to appear
- •Resize the field if needed by dragging the corners
- •Add additional fields if multiple signatures are needed
Assign Signers
- •For each signature field, assign a signer
- •Enter the signer's email address
- •Enter the signer's full name
- •If multiple signers, assign each field to the appropriate person
- •Different colored highlights indicate different signers
Configure Signing Options
- •Set the signing order:
- •- Sequential: Signers sign one after another in specified order
- •- Parallel: All signers can sign at the same time
- •Set an expiration date (optional but recommended)
- •Enable reminders (optional but recommended)
- •Configure 2FA requirements if needed
Customize the Email
- •Review the default email template
- •Customize the subject line if desired
- •Add a personal message explaining what they're signing
- •Preview how the email will appear to signers
Send the Request
- •Review all settings in the summary panel
- •Verify signer email addresses are correct
- •Click 'Send for Signature'
- •Signers receive the email immediately (or per your schedule)
- •Track progress in the Signatures dashboard
Tutorial: Setting Up Multi-Party Signatures
Configure documents that require multiple people to sign
Plan Your Signing Flow
- •Identify all parties who need to sign
- •Determine the signing order:
- •- Sequential: One after another (most common)
- •- Parallel: Everyone at the same time
- •- Mixed: Some parallel, some sequential
- •Example: Customer signs first → Manager counter-signs → Legal approves
Upload and Prepare Document
- •Upload your multi-party document
- •Identify where each person should sign
- •Consider adding initials on each page
- •Plan placement for signatures, dates, and any checkboxes
Add Fields for Each Signer
- •Add signature field for first signer
- •Assign to signer (enter their email and name)
- •Add any additional fields for them (date, initials)
- •Repeat for each additional signer
- •Use colors to visually distinguish each signer's fields
Set the Signing Order
- •Go to 'Signing Order' settings
- •For Sequential signing:
- •- Drag signers into the desired order
- •- First signer receives request immediately
- •- Each subsequent signer receives request after previous completes
- •For Parallel signing:
- •- Select 'Parallel' mode
- •- All signers receive requests simultaneously
Configure Per-Signer Settings
- •For each signer, you can customize:
- •- Custom email message
- •- Required 2FA method
- •- Reminder schedule
- •Click on a signer to access their individual settings
Test with Sequential Flow
- •Send the request
- •Monitor progress in the dashboard
- •Watch as each signer completes in order
- •Review the final document with all signatures
- •Download the completed, signed document
Tutorial: Collecting Qualified Electronic Signatures (QES)
Use eID cards for maximum legal validity in the EU
Understand QES Requirements
- •QES provides the highest level of signature validity in the EU
- •Under eIDAS Article 25, QES equals a handwritten signature
- •Signers need:
- •- Autogram desktop application installed
- •- Supported eID card (Slovak eID, Czech eObčanka, or PKCS#11 compatible)
- •- Card reader connected to their computer
Prepare the Signer
- •Before sending the request, ensure the signer has:
- •1. Downloaded and installed Autogram from https://sluzby.slovensko.digital/autogram/
- •2. A compatible eID card with valid certificates
- •3. A USB card reader
- •4. PIN codes for their eID card
- •Send preparation instructions to the signer if needed
Create the Signature Request
- •Upload your document as normal
- •Add signature fields where needed
- •When configuring the signer, select 'Require QES'
- •Choose the signature level:
- •- Baseline-B: Basic QES (1-3 years validity)
- •- Baseline-T: With timestamp (5+ years)
- •- Baseline-LT: Long-term validation (10+ years)
- •- Baseline-LTA: Long-term archive (20+ years)
- •For important documents, Baseline-LT or LTA is recommended
Send with QES Instructions
- •Customize the email to include QES instructions
- •Remind the signer to have Autogram running
- •Include the link to download Autogram if needed
- •Send the request
Signer Completes QES Process
Verify the QES Signature
- •Once complete, the document contains embedded QES
- •The signature includes:
- •- Qualified certificate from trusted authority
- •- Timestamp (if Baseline-T or higher)
- •- Long-term validation data (if Baseline-LT or higher)
- •You can verify the signature in any PDF reader
- •Dropie also shows verification status in the dashboard
Tutorial: Automated Signatures in Workflows
Collect signatures automatically as part of document workflows
Set Up the Workflow
- •Create or open a workflow in the workflow builder
- •Ensure you have a form trigger that collects signer information
- •Add a 'Generate Document' step to create the contract/agreement
- •The generated document will be sent for signature
Add Signature Request Step
- •Click '+' after the Generate Document step
- •Select 'Request Signature' step type
- •Choose the document from previous step
- •Configure signer from form data:
- •- Signer email: {{form.email}}
- •- Signer name: {{form.full_name}}
Configure Signature Fields in Template
- •Your document template should already have signature placeholders
- •When setting up the template, define signature field positions
- •These are pre-positioned for automatic signature requests
- •The workflow uses these predefined positions
Add Multiple Signers (If Needed)
- •For multi-party workflows, add additional signers
- •Example: Customer from form, company rep as fixed email
- •Configure signing order (sequential or parallel)
- •Map each signer to appropriate signature fields
Configure Post-Signature Actions
- •Add steps that execute after signature completes
- •Common actions:
- •- Send signed copy to all parties
- •- Store in client portal
- •- Notify team of completion
- •- Update client record
- •- Trigger payment collection
Test the Flow
- •Run a test submission through the workflow
- •Verify the document generates correctly
- •Complete the test signature
- •Verify post-signature actions execute
- •Activate the workflow when testing is complete
How-To Guides
How to Resend a Signature Request
- 1.Navigate to Signatures in the sidebar
- 2.Find the pending signature request
- 3.Click on the request to open details
- 4.Click 'Resend' button next to the signer who hasn't signed
- 5.Optionally modify the message
- 6.Click 'Send' to resend the request
Tip: Include a personal note when resending - it significantly increases completion rates
How to Cancel a Signature Request
- 1.Navigate to Signatures in the sidebar
- 2.Find the pending signature request
- 3.Click on the request to open details
- 4.Click 'Cancel Request' button
- 5.Confirm the cancellation
- 6.All pending signers are notified the request is cancelled
You cannot cancel after all parties have signed. Signatures that are complete remain valid.
How to Download a Signed Document
- 1.Navigate to Signatures in the sidebar
- 2.Find the completed signature request (status: Complete)
- 3.Click on the request to open details
- 4.Click 'Download Signed Document'
- 5.Choose format:
- 6.- PDF: Document with visual signatures
- 7.- Certificate: Separate signature certificate/audit trail
For QES signatures, the PDF contains the embedded cryptographic signature. Verify in Adobe Acrobat or similar PDF reader.
How to Set Up Automatic Reminders
- 1.When creating a signature request, go to 'Options'
- 2.Enable 'Automatic Reminders'
- 3.Configure reminder schedule:
- 4.- First reminder: Days after initial request (e.g., 2 days)
- 5.- Second reminder: Days after first reminder (e.g., 3 days)
- 6.- Final reminder: Days before expiration (e.g., 1 day)
- 7.Customize reminder messages if desired
- 8.Save and send the request
Tip: Gentle, professional reminders significantly improve completion rates without annoying signers
How to Verify a Signature's Authenticity
- 1.Open the completed signature request in Dropie
- 2.Click 'View Audit Trail' or 'Verification Details'
- 3.Review the forensic evidence:
- 4.- Timestamp of signature
- 5.- IP address and location
- 6.- Device and browser information
- 7.- 2FA verification (if used)
- 8.- Document hash before and after
- 9.For QES: Open the PDF in Adobe Acrobat
- 10.Click on the signature to see certificate details
- 11.Verify the certificate chain and validity
How to Require 2FA for Signing
- 1.When creating a signature request, go to signer settings
- 2.Enable 'Require 2FA' for the signer
- 3.Choose 2FA method:
- 4.- Email verification (available on all tiers)
- 5.- SMS verification (Business tier and above)
- 6.The signer must verify their identity before signing
- 7.Verification is logged in the audit trail
Use case: Use for high-value contracts or when signer identity is critical
How to Access the Signature Audit Trail
- 1.Navigate to Signatures in the sidebar
- 2.Find and click on the signature request
- 3.Click 'Audit Trail' or 'Evidence' tab
- 4.View complete timeline of events:
- 5.- Request created
- 6.- Email sent to signer
- 7.- Document opened by signer
- 8.- Pages viewed and time spent
- 9.- Signature applied
- 10.- 2FA verification (if used)
- 11.Export audit trail as PDF if needed
How to Send Bulk Signature Requests
- 1.Prepare your CSV file with signer information:
- 2.- Name, email, and any custom data columns
- 3.Navigate to Signatures in the sidebar
- 4.Click 'Bulk Request' or use a workflow with bulk processing
- 5.Upload your document template
- 6.Upload your CSV file
- 7.Map CSV columns to signer fields
- 8.Preview a few requests before sending all
- 9.Click 'Send All' to dispatch requests
- 10.Monitor progress in the dashboard
Audit Trail & Evidence
Every signature includes comprehensive forensic evidence for legal defensibility.
Consent Tracking
- Explicit consent checkbox timestamp
- Consent text version
- IP address at consent
Document Interactions
- Document opened timestamp
- Pages viewed and scroll depth
- Time spent reviewing each page
- Signature field focus events
Device Information
- Browser name and version
- Operating system and platform
- Screen resolution and color depth
- Timezone and language settings
- Canvas and WebGL fingerprint (SHA-256)
- Hardware specifications
Network & Location
- IP address with geolocation
- City and country
- Optional precise geolocation (with consent)
Authentication
- 2FA method used (email/SMS)
- Verification code sent timestamp
- Verification completed timestamp
- Number of verification attempts
Signature Details
- Signature drawing strokes (for drawn signatures)
- Drawing duration
- Typed text (for typed signatures)
- Completion timestamp
Document Integrity
- SHA-256 document hash before signing
- SHA-256 document hash after signing
- Signature position data
- Tamper detection verification
Security
- All evidence encrypted with AES-256 at rest
- Access requires 'manage_signatures' permission
- Every access to forensic evidence is logged
- Mandatory reason required when viewing evidence
- Default retention: 7 years
Qualified Electronic Signatures (QES)
For maximum legal validity in the EU, Dropie supports Qualified Electronic Signatures via Autogram integration.
What is QES?
A Qualified Electronic Signature (QES) is the digital equivalent of a handwritten signature under EU law. It uses cryptographic certificates issued by qualified trust service providers and requires strong identity verification (typically via government-issued eID cards).
Requirements for QES Signing
Signer Requirements
- Autogram desktop application installed on computer
- Supported eID card (Slovak eID, Czech eObčanka, or PKCS#11 compatible)
- USB card reader connected
- Valid certificates on the eID card
- PIN codes for the eID
Document Requirements
- PDF format document
- Document must not already be signed with conflicting signature
- Signature field must be properly positioned
XAdES Signature Levels
Baseline-B
Basic QES signature without timestamp
Use for short-term agreements only
Baseline-T
QES with trusted timestamp
Good for standard business contracts
Baseline-LT
Long-term validation data embedded
Recommended for important contracts
Baseline-LTA
Long-term archive with archive timestamp
Required for legal archives and government
Legal Status: Under eIDAS Article 25, QES has the legal equivalent effect of a handwritten signature across all EU member states. It cannot be denied legal effect solely because it's electronic.
Security Features
Device Verification
Validate signer's device with fingerprinting and consistency checking. Detects suspicious signing patterns.
2FA Authentication
Email verification required by default. SMS verification available on Business+ tiers. QES uses eID card + PIN.
Document Integrity
SHA-256 hash verification ensures document hasn't been tampered with before or after signing.
Encrypted Storage
All signatures, documents, and evidence encrypted at rest with AES-256. TLS 1.2+ for transmission.
Access Controls
Permission-based access to signed documents and audit trails. All access is logged.
Secure Links
Signing links are unique, unguessable tokens. Can be set to expire after use or time limit.
Best Practices
Use Clear Signature Placement
Position signature fields where signers expect to sign - typically at the bottom of the document or at the end of key sections. Make signature areas clearly visible with adequate size.
Provide Context in Email
Write clear, specific email messages explaining what the document is and why the signature is needed. Vague requests lead to lower completion rates.
Set Reasonable Deadlines
Configure expiration for signature requests (7-14 days is typical). Too short causes pressure; too long lets it get forgotten. Enable reminders.
Enable Reminders
Configure automatic reminders for pending signatures. A gentle reminder at 2-3 days and again 1 day before expiration significantly improves completion rates.
Use QES for High-Value Agreements
For contracts with significant legal or financial implications, require Qualified Electronic Signatures for maximum legal defensibility.
Require 2FA for Sensitive Documents
Enable 2FA verification for contracts involving large sums, confidential information, or when signer identity is critical.
Test Multi-Signer Flows
Before sending multi-party signature requests, test the entire flow with internal team members to catch any issues.
Legal Compliance
ESIGN Act
Electronic Signatures in Global and National Commerce Act
Compliant
eIDAS Regulation
Electronic Identification, Authentication and Trust Services
Compliant (including QES)
UETA
Uniform Electronic Transactions Act
Compliant
Dropie signatures include comprehensive audit trails that provide strong legal defensibility in court proceedings. For the highest level of legal validity in EU jurisdictions, use Qualified Electronic Signatures (QES).
Troubleshooting
Signer says they didn't receive the email
- Check the email address is correct
- Ask signer to check spam/junk folder
- Resend the signature request
- Ask signer to whitelist Dropie emails
- Verify your domain's email deliverability
Signer can't complete their signature
- Check if all required fields are filled
- Verify they're using a supported browser (Chrome, Firefox, Safari, Edge)
- Try a different browser
- Clear browser cache and try again
- Check internet connection stability
QES signing fails
- Verify Autogram is installed and running
- Check eID card is properly inserted in reader
- Verify the card reader is connected and recognized
- Ensure eID certificates haven't expired
- Try restarting Autogram application
- Check if correct PIN is being entered
Document shows 'Signature invalid' in PDF reader
- Download the latest version of the signed document
- Use Adobe Acrobat Reader for best QES verification
- Check if your PDF reader is up to date
- For QES: ensure the reader has updated certificate lists
Workflow signature step keeps failing
- Check the signer email mapping is correct
- Verify the document template has signature fields defined
- Check that previous workflow steps completed successfully
- Review workflow execution logs for specific errors
Frequently Asked Questions
Are e-signatures legally binding?
Yes. Electronic signatures are legally binding in the US (ESIGN Act), EU (eIDAS), and most countries worldwide. Dropie's comprehensive audit trails provide strong evidence for legal defensibility. For maximum legal validity in the EU, use Qualified Electronic Signatures (QES).
Do signers need to create an account?
No. External signers receive a secure link via email and can sign without creating a Dropie account. They simply verify their email address (and complete 2FA if required) and sign.
Can I sign documents on my phone?
Yes. Dropie's signing interface is fully responsive and works on phones and tablets. Signers can draw their signature with their finger. Note: QES requires a desktop computer with card reader and is not available on mobile.
How long are signed documents stored?
Signed documents and audit trails are stored for 7 years by default, meeting most regulatory requirements. Custom retention periods may be available on Enterprise plans.
What's the difference between sequential and parallel signing?
Sequential: Signers sign one after another in a specific order. Each person waits for the previous to complete. Parallel: All signers receive requests simultaneously and can sign in any order. The document is complete when all have signed.
Can I cancel a signature request after sending?
Yes, you can cancel pending signature requests at any time. All pending signers are notified of the cancellation. However, signatures that have already been completed remain valid and cannot be revoked.
What happens if a signer declines to sign?
If a signer actively declines, you're notified immediately. For sequential signing, the process stops. You can choose to send to a different person or cancel the request entirely.
Can I require signers to initial each page?
Yes. When setting up the document, add 'Initials' fields on each page you want initialed. Assign them to the appropriate signer. They must initial all required pages before the signature can be completed.