# OneSpan Sign — E-Signature

OneSpan Sign by OneSpan, Inc. holds a panel rating of 2.5/5 from 6 AI judges (category median 2.5/5), as of 2026-11-11. Provenance: provenance unknown; sovereignty: not determined.

- Vendor: OneSpan, Inc. (https://www.onespan.com)
- Category: [E-Signature](https://whats-best.ai/software/e-signature.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/e-signature/onespan-sign
- Alternatives: https://whats-best.ai/software/e-signature/onespan-sign/alternatives ([markdown](https://whats-best.ai/software/e-signature/onespan-sign/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-11 · oldest source captured 2026-11-10

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: OneSpan, Inc.
- Headquarters: Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting: Not stated on the vendor’s pages as of 10 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 10 Nov 2026

## The panel's verdict

OneSpan Sign, an e-signature product, leads on signing workflow and evidence and retention at 6 to 6, with integration and API at 5 to 7 holding the table's only 7. Judges cite bulk sending from templates via CSV at approximately 3000 transactions per hour, an editable signing order with sequential notification, and a single evidence pack per transaction — audit trail and signer session recordings — downloadable as PDF by API, with retention configurable per transaction state, a 120-day default and a 7-day warning before purge. Integration brings REST endpoints, Java,.NET and APEX SDKs and a Dynamics CRM connector for 2013 to 2016; gaps cited: webhooks, a sandbox and embedded signing in a customer's own application. Sovereignty is the floor at 1 to 1: the only location fact is a Boston, USA address; jurisdiction, data residency, hosting options and a data processing agreement are recorded as unknown. The widest spread, signature levels at 4 to 6, turns on the same gap: all three eIDAS levels are named with no plan mapping or trust-list entry. Pricing transparency runs 0 to 1, uncounted.

**Speaks for it:**
- Bulk sending from eligible templates via CSV, documented at approximately 3000 transactions per hour
- Editable signing order in which the next signer is notified only after the previous signer completes
- A single evidence pack per transaction, containing the full audit trail, signer session recordings and identity validation data, retrievable repeatedly as a PDF via the API after completion
- Data retention configurable per transaction state, with a 120-day default and a warning at least 7 days before permanent deletion
- Documented REST API with concrete endpoints and status codes, Java,.NET and APEX SDKs, and connectors for Microsoft Dynamics CRM versions 2013 to 2016 and SharePoint

**Held against it:**
- Sovereignty scores 1 to 1: a Boston, USA postal address is the only published location fact, with jurisdiction, data residency, hosting options and a data processing agreement recorded as unknown
- No public information on webhooks, a sandbox, published rate limits or embedded signing outside the CRM connector
- No public plan mapping for the three eIDAS signature levels and no linked EU Trust List entry
- No public information on what happens to identity-verification data after checks, or on long-term validation, qualified timestamps or validation reports for stored evidence
- No public prices for the named Professional and Business plans, and no per-signature or identification fees

**Best for:**
- You send large volumes of similar documents from templates and need documented bulk sending with per-signer authentication by access code, SMS or SSO.
- You must export a complete evidence pack and manage retention rules through an API for archiving into your own systems.
- Your team works in Microsoft Dynamics CRM versions 2013 to 2016 or SharePoint and wants signing from inside those tools.

**Avoid if:**
- You must first establish where documents, audit trails and signer data are stored, and which entity processes them, before contracting.
- Your signed contracts need to remain independently validatable years later through long-term validation or qualified timestamps.
- You need a documented plan-to-signature-level mapping or a linked EU Trust List entry before purchase.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v2). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Legal Counsel | The HR Operations Lead | The Revenue Operations Lead | The Integration Engineer | The Data Protection Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| eIDAS levels & trust services | 2.5/5 | 2.5/5 | 3/5 | 2/5 | 2.5/5 | 2.5/5 |
| Signer identification | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 |
| Signing workflow & signer experience | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| Evidence, validation & retention | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 | 3/5 |
| Integrations & API | 3.5/5 | 3/5 | 3/5 | 2.5/5 | 3/5 | 3/5 |
| European sovereignty | 0.5/5 | 0.5/5 | 0.5/5 | 0.5/5 | 0.5/5 | 0.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2.5/5** | **2.5/5** | **3/5** | **2.5/5** | **2/5** | **2.5/5** |

### The judges

- **The Legal Counsel** (v1.0): Decides which contracts may be signed electronically and at which level. Wants SES, AdES and QES named per plan and country, the qualified trust service provider linked to the EU Trust List, and an audit trail with timestamps that still validates when the contract is disputed in eight years.
- **The HR Operations Lead** (v1.0): Sends two hundred employment contracts a year, many of them fixed-term and so under written form. Wants QES that a new hire can complete on a phone in ten minutes, identification that accepts the IDs applicants actually hold, bulk sending from templates, and a price per qualified signature known before the contract is signed.
- **The Revenue Operations Lead** (v1.0): Measures how long a quote takes to come back signed and where it stalls. Wants signing from inside the CRM, templates sales cannot break, reminders and signing order that run themselves, and a signer experience that needs no account, no app and no explanation.
- **The Integration Engineer** (v1.0): Embeds signing into the company's own portal and archives the result in the DMS. Wants a versioned API with webhooks and a sandbox, every signature level reachable through the API rather than only in the web app, and signed documents exported with their evidence intact.
- **The Data Protection Officer** (v1.0): Knows every signer who holds an ID card up to a camera hands biometric and identity data to a provider they never chose. Asks who performs the identification, where documents and ID data are stored, how long the audit trail keeps IP addresses, and who the subprocessors in the trust service chain are.
- **The Skeptic** (v1.0): Knows "legally binding" usually means a simple signature. Reads for the level the default plan actually signs at, the QTSP the provider does not operate itself, the per-QES and ident fees on top of the plan, the envelope limit, and "eIDAS-compliant" from a provider that names no trust service at all.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: not determined.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Not determined | — | — |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- Eidas regulation: eIDAS · 2016-07-01 · EU Regulation No. 910/2014 [S2]
- Identification levels: low · substantial · high [S2]
- Qes legal equivalence: QES equivalent to handwritten signature; no additional evidence required under eIDAS Article 25 [S2]
- Qualified tsp trust mark: Qualified trust service providers identifiable by standard EU trust mark [S2]
- Trust services scope: electronic signatures · certificates for electronic signatures · electronic seals · time-stamps · website authentication · electronic registered delivery services [S2]

**Data**
- Advanced settings: yes [S9]
- API management: yes [S9]
- Archived basis: status changed to Archived [S9]
- Completed basis: status changed to Completed [S9]
- Default interval: 120 [S9]
- Earliest date wins: earliest deletion date takes effect [S9]
- Incomplete basis: status changed to Draft/Declined/Expired [S9]
- Incomplete states: Draft · Declined · Expired [S9]
- Lifetime precedence: shortest rule wins [S9]
- Plan permission business: Business · all [S9]
- Plan permission professional: Professional · Total Transaction Lifetime · Incomplete Transactions [S9]
- Purge overnight: overnight [S9]
- Purge warning: 7 [S9]
- Reset to default: yes [S9]
- Retention states: Draft · Opted out · Declined · Expired · Completed · Archived [S9]
- Roles permissions access: Admin · Manager · Owner [S9]
- Self service default: Support Team · yes [S9]
- Total lifetime basis: transaction creation date · Total Transaction Lifetime [S9]
- Transactions permanently deleted: transactions after retention period · permanent [S9]
- Trash behavior: state entry date, not trash date [S9]

**Hosting**
- Languages: English · French · Japanese [S1]

**Integrations**
- Dynamics versions: 2013 · 2015 · 2016 [S10]
- Get evidence endpoint: GET · /api/transaction/{transaction_id}/document/AuditTrailDocument/pdf · pdf [S8]
- Get evidence requires completed transaction: yes [S8]
- Get evidence returns evidence pack: full transaction audit trail · signer session recordings · identity validation data · additional evidence material [S8]
- Get evidence status codes: 200 · 400 · 401 · 403 · 500 [S8]
- Integration platform: Out-of-the-box Integration Platform connecting eSignatures to business applications [S10]
- Rest create package endpoint: POST · create package with ordered roles · /api/packages [S7]
- Rest update roles endpoint: PUT · update role workflow order · /api/packages/{packageId}/roles [S7]
- Sdks supported: Java · .NET · REST API · APEX [S7]

**Legal**
- Address: 1 Marina Park Drive, 02210 Boston, USA [S1]
- Address: 1 Marina Park Drive, 02210 Boston, USA [S2]
- Copyright: 2026 · OneSpan [S1]

**Pricing**
- Bulk send max file size: 8 [S6]

**Product**
- 2016 onpremises only: on-premises only [S11]
- Account document upload host URL: Account settings include a Document Upload Host URL pointing to the IIS-hosted Dashboard and Reports site [S11]
- Account management: yes [S10]
- Authentication solutions: Secure Transaction Signing · Mobile App Security · Workforce Authentication [S1]
- Bulk send account enabled prerequisite: yes [S6]
- Bulk send API trigger: yes [S6]
- Bulk send auth types: NONE · CHALLENGE · SSO · SMS [S6]
- Bulk send challenge validation: yes · 1 [S6]
- Bulk send CSV required fields: AUTH_TYPE · AUTH_PROMPT · AUTH_CHALLENGE · SIGNER_VERIFICATION · FieldId columns · {PlaceholderRoleName} · FIRST_NAME · LAST_NAME · EMAIL [S6]
- Bulk send encoding non ascii: UTF-8 [S6]
- Bulk send field population: FieldId columns automatically populate document fields; unlimited number of fields supported [S6]
- Bulk send multiple placeholders: yes [S6]
- Bulk send processing capacity: 3000 [S6]
- Bulk send purpose: Bulk Send creates and distributes multiple transactions from an eligible template using a CSV file with signer information [S6]
- Bulk send recommended batch: 1000 [S6]
- Bulk send scheduling: FIFO · 15 [S6]
- Bulk send signer verification support: PCC · DIGIPASS · yes [S6]
- Bulk send signing method ID: personalCertificateSigning · yes [S6]
- Bulk send SMS phone format: E.164 [S6]
- Bulk send SMS validation: 1 · yes [S6]
- Bulk send template requirements: at least one document other than the Consent Agreement · at least one placeholder Role · at least one Signature Field [S6]
- Bulk send validation header first: yes [S6]
- Client cert verification: SSL client certificate verification options including Never, CA certificate file, re-verify on renegotiation, and auto-trust certificates (not recommended) [S3]
- Connector features 2015: Creating a Package · Adding Signers · Managing Documents [S10]
- Connector features 2016: create document packages · obtain secure e-signatures [S10]
- Conventions view: Administrators · OneSpan Sign Template Creators · yes [S10]
- CRM connector purpose: Connector for MS Dynamics CRM enabling secure e-signatures on transactions created in the CRM [S10]
- Cybersecurity modules: FIDO Hardware Authenticators · Classic Hardware Authenticators · Mobile App Security · Mobile Authentication · Cloud Authentication · Authentication Servers [S1]
- Cybersecurity scope: identity protection · mobile app security · access safeguarding · advanced authentication · threat intelligence · fraud protection [S1]
- Dashboard reports update: Dashboard & Reports updated by backing up web.config, stopping IIS site, replacing files from a 7z package, and restoring web.config settings [S11]
- Digital agreements modules: Notary · Multi-channel Notification · Smart Forms [S1]
- Digital agreements scope: secure eSignatures · identity verification · smart digital forms [S1]
- Doc published: SEAL article published Jan 14, 2026 [S3]
- Document country lists: Supported countries and ID documents lists provided by verification providers, may change without notice; OneSpan does not test a document and country until requested [S4]
- External signer verification: OneSpan Sign can verify signer identity via credentials with an external organization (e.g., Validated ID, Asseco, DIGIPASS) [S5]
- Identity verification exists: OneSpan Identity Verification documentation exists with subcategories: Supported countries and ID documents, Web Service Guide, Release Notes [S4]
- Intended audience: Audience: developers with knowledge of an External Verification Provider; no detailed protocol knowledge needed [S5]
- Itsme example: itsme (Belgium) cited as example qualified trust service provider [S2]
- Java SDK integration: A Java SDK integrates OneSpan Sign Application Backend with an external organization's Verification Server [S5]
- Language setting: yes [S10]
- Maintain customizations option: yes [S11]
- Managed solution import: New connector solution imported via Settings > Solutions > Import in Dynamics CRM [S11]
- Notification event log: eSignLive.comEventLog [S11]
- Notification service interval config: yes [S11]
- Notification service processing check: Before upgrade, all EslNotifications must be processed by the Windows service (Processed column non-null) [S11]
- Notification service reinstall commands: eSignLive.comESLNotificationService.exe -install · eSignLive.comESLNotificationService.exe -uninstall [S11]
- Notifications view: yes [S10]
- Onespan sign eidas support: OneSpan Sign supports all types of signatures under the eIDAS regulation [S2]
- Overview: Advanced authentication and fraud prevention plus secure agreement preparation, signing, and management workflows [S1]
- Packages management: Administrators · OneSpan Sign Package Creators · OneSpan Sign Template Creators · yes [S10]
- Plugin commands: yes [S10]
- Push notification service deployment guide: yes [S11]
- Push notification service port reuse: yes [S11]
- Qes qualified certificate: QES must be supported by a qualified certificate issued by a qualified trust service provider [S2]
- Qes requirements: OneSpan QES requires a personal digital certificate in addition to standard requirements [S2]
- SDK topics: Sequence Diagram · Sample Integration Code [S5]
- Seal communicator: OneSpan Authentication Server supports SEAL communicators configured via Communicators > SEAL tab, with enable/disable checkboxes [S3]
- Seal dpx storage: SEAL stores copies of uploaded DIGIPASS export file (DPX) data at a configurable location [S3]
- Seal license: SEAL depends on license [S3]
- Sent transaction draft required: yes · sent transaction must be set to DRAFT before updating signer workflow [S7]
- Sequential signing notification: next signer notified only after previous signer completes · yes [S7]
- Sharepoint integration available: yes [S11]
- Sign platform capabilities: preparing · distributing · reviewing · signing · downloading documents [S10]
- Signature types: electronic · advanced · qualified [S2]
- Signer workflow ordering: yes · define signing order for multiple signers and document signing order [S7]
- Signing order editable: signingOrder · yes [S7]
- Signing order index default: integer · roles.index · 0 · yes · no [S7]
- Signing order meaning: signing order 1 means the signer signs first [S7]
- SMS otp authentication example: Advanced E-Signatures with authentication and SMS one-time passcode described in customer case [S2]
- Solutions verticals: Financial Services · Insurance Policies and Claims · OEMs & ISVs · Human Resources [S1]
- SSL settings: SEAL connection can be secured with SSL; SSL cipher suite security levels Very High, High, Medium, Low [S3]
- Swisscom integration blog: Swisscom can be integrated with OneSpan Sign as a Trust Service Provider [S2]
- Templates management: Administrators · OneSpan Sign Template Creators · yes [S10]
- Upgrade data validation: After 2.1 upgrade, all Account and Opportunity drop-down values must be Related Entity fields or Related Record fields [S11]
- Upgrade downtime requirement: No CRM users may be using Dynamics CRM during connector upgrade [S11]
- Upgrade service msi: Upgrade to 2.1 completed by installing eSignLive.com.Crm.UpgradeService.Setup.msi and running OneSpan Sign Connector Upgrade Service [S11]
- Version: Documentation for OneSpan Authentication Server version 3.29, with 3.28–3.24 also listed [S3]
- Versions covered: 2013 · 2015 · 2016 · 2.1 · 1.1 [S11]

**Support**
- Resources: Partner Program · eSignature Legality Guide · Documentation Portal · OneSpan Community [S1]

## Questions

### Is OneSpan Sign European?

Not determined: the vendor’s pages as captured do not say where OneSpan Sign is based.

### Where does OneSpan Sign store data?

Not stated on the vendor’s pages as of 10 Nov 2026.

### Does OneSpan Sign have a free plan?

Not stated on the vendor’s pages as of 10 Nov 2026.

### What are the best alternatives to OneSpan Sign?

As of 19 Nov 2026, the panel rates [sproof sign (3.5/5)](https://whats-best.ai/software/e-signature/sproof-sign), [Signicat Sign (3/5)](https://whats-best.ai/software/e-signature/signicat-sign) and [Youtrust (Yousign) (3/5)](https://whats-best.ai/software/e-signature/youtrust) highest among the other 31 E-Signature products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [sproof sign](https://whats-best.ai/software/e-signature/sproof-sign) (EU-Made, Austria). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [OneSpan Sign alternatives](https://whats-best.ai/software/e-signature/onespan-sign/alternatives).

## What this page leaves out

- 5 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.

## Sources

- [S1] Vendor page: https://www.onespan.com (checked 2026-11-10)
- [S2] EIDAS levels & trust services — found from sitemap: https://www.onespan.com/topics/eidas (checked 2026-11-10)
- [S3] EIDAS levels & trust services — found from sitemap: https://docs.onespan.com/sec/docs/oas-cfgut-csh-seal-3-29 (checked 2026-11-10)
- [S4] Signer identification — found from sitemap: https://docs.onespan.com/docs/onespan-identity-verification (checked 2026-11-10)
- [S5] Signer identification — found from sitemap: https://docs.onespan.com/docs/external-signer-verification (checked 2026-11-10)
- [S6] Signing workflow & signer experience — found from sitemap: https://docs.onespan.com/docs/bulk-sending (checked 2026-11-10)
- [S7] Signing workflow & signer experience — found from sitemap: https://docs.onespan.com/docs/creating-a-signer-workflow (checked 2026-11-10)
- [S8] Evidence, validation & retention — found from sitemap: https://docs.onespan.com/docs/get-evidence (checked 2026-11-10)
- [S9] Evidence, validation & retention — found from sitemap: https://docs.onespan.com/docs/data-retention (checked 2026-11-10)
- [S10] Integrations & API — found from sitemap: https://docs.onespan.com/docs/using-onespan-sign-embedded-integration-for-crm (checked 2026-11-10)
- [S11] Integrations & API — found from sitemap: https://docs.onespan.com/docs/upgrading-onespan-sign-embedded-integration-for-crm (checked 2026-11-10)

---

Cite as: whats-best.ai, "OneSpan Sign — E-Signature", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/e-signature/onespan-sign

Corrections: https://whats-best.ai/correct/1752?target=page
