OneSpan Sign
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by OneSpan, Inc. · www.onespan.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
OneSpan Sign 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
- Panel verdict
- The AI panel rates OneSpan Sign 2.5/5, the mean of 6 judges. 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. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
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.
The scores
| Criterion | Panel median |
|---|---|
| eIDAS levels & trust services | 2.5 of 5 |
| Signer identification | 2.5 of 5 |
| Signing workflow & signer experience | 3 of 5 |
| Evidence, validation & retention | 3 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 0.5 of 5 |
eIDAS levels & trust services
Show reasoningHide reasoning
How this is scored
Which signature levels the platform offers — simple, advanced, qualified, and qualified seals — through which qualified trust service provider on the EU Trust List, for which countries and legal regimes (eIDAS, ZertES), and on which plans.
0 — Not an electronic signature service: a PDF annotation or form tool that places a drawn or typed signature image without any eIDAS signature behind it.
3 — Electronic signatures at the simple level (SES) described as compliant with eIDAS; advanced and qualified levels and the trust service provider are basic or not described.
5 — Simple and advanced or qualified signatures (SES with AdES or QES) offered and named as eIDAS levels, with the plans or add-ons that include them and which documents need which level explained for Germany or the EU.
8 — SES, AdES and QES all documented with the plans and countries they are available in, the qualified trust service provider named with its entry on the EU Trust List linked, QES under eIDAS (and ZertES where relevant) stated, qualified electronic seals for company documents, and the signature level shown in the signed document and audit trail.
10 — Levels are an explicit product decision: the provider is or contracts a named QTSP with its conformity assessment published, level selection per document type or template, remote QES without a separate account, EUDI wallet support stated with a date, and the legal effect per level documented for the main EU markets.
The Legal Counsel
The vendor states its signing product supports all signature types under eIDAS — simple, advanced and qualified are each named, the qualified signature requires a personal certificate from a qualified trust service provider, and Swisscom and itsme appear as trust service providers that can be integrated. What the captured pages do not show is the plan mapping, a link from the trust service provider to the EU Trust List, qualified seals for company documents, or the signature level appearing in the signed document and audit trail — so my eight-year dispute test rests on naming, not documented proof. 2
The HR Operations Lead
OneSpan Sign is documented as supporting all three eIDAS signature categories, with the qualified signature requiring a personal digital certificate from a qualified trust service provider, itsme in Belgium given as an example provider and Swisscom offered as an integrable trust service provider. We found no public information tying the levels to specific plans or countries, and no link to an entry on the EU Trust List for the provider behind the qualified signatures. 2
The Revenue Operations Lead
OneSpan Sign is stated to support all three eIDAS signature levels, with the qualified level spelled out as requiring a personal digital certificate from a qualified trust service provider, naming itsme in Belgium and a Swisscom integration as examples. What the captured pages do not show is which plans include which level, which countries each level works in, or a linked EU Trust List entry, so I cannot tell a sales team what a qualified-signature deal buys into. 2
The Integration Engineer
The eIDAS topic page states that OneSpan Sign supports all signature types under the regulation, names the simple, advanced and qualified categories, and describes qualified signatures as requiring a personal certificate from a qualified trust service provider, citing itsme and Swisscom as providers. We found no public information on which plans include which level, on country availability, or on a Trust List entry, so I cannot yet confirm from these pages that every level is reachable in an automated flow; the bulk-sending configuration does at least expose a certificate-based signing method identifier. 2 6
The Data Protection Officer
All three eIDAS categories are named and the qualified signature is explained down to its certificate chain, with itsme cited as an example qualified trust service provider and Swisscom offered as an integrable provider. However, the captured pages give no plan or country for each level, no trust-list entry, and no qualified seals for company documents, so a buyer cannot see which level they are buying. 2 6
The Skeptic
OneSpan Sign states it supports all three eIDAS signature levels and that its qualified signature requires a personal digital certificate from a trust service provider, naming Swisscom as one that can be integrated; no plan or add-on is tied to any level, and we found no public information on a linked EU Trust List entry, qualified seals, or ZertES. The trust provider named is a third party OneSpan integrates with, not one it operates or contracts as its own. 2
Signer identification
Show reasoningHide reasoning
How this is scored
How the signer is identified for each level: email and SMS codes, video ident, eID card (Online-Ausweis), bank ident or EUDI wallet — who performs it, in which countries it works, and what happens to the ID data afterwards.
0 — No signer authentication offered: by the vendor's own description anyone holding the link can sign.
3 — Signers authenticated by an email link with an access code or SMS code; identification for advanced and qualified signatures is basic or not described.
5 — Email, SMS or access-code authentication, plus identification methods for AdES or QES listed by name (for example video ident, eID card, bank ident), with the countries or ID documents they accept stated.
8 — Methods documented per level and country with the identification provider named, automated and agent-based ident distinguished, reuse of an identification for later signatures explained, retention and deletion of ID data stated, and the ident provider listed as subprocessor.
10 — Identification is transparent end to end: every method with its countries, assurance level and completion guidance, EUDI wallet and national eID supported, ID data minimisation and retention committed, and the signer-facing privacy notice published.
The Legal Counsel
Signers can be authenticated by SMS code, knowledge-based challenge or SSO per the bulk-send documentation, the documentation names external verification providers — Validated ID, Asseco, DIGIPASS — integrated through a Java SDK, and an identity verification product publishes supported countries and ID documents. I found no per-level, per-country mapping with a named identification provider, and no statement on retention or deletion of ID data, which I need before relying on a qualified signature. 4 5 6 2
The HR Operations Lead
SMS one-time passcodes and access challenges are documented, external verification providers are named — Validated ID, Asseco and DIGIPASS — and dedicated documentation of supported countries and ID documents exists, which matters to me since my applicants hold varied IDs. Those country lists are supplied by the verification providers and OneSpan tests a document and country only when requested, and we found no public information on what happens to the ID data afterwards. 2 4 5 6
The Revenue Operations Lead
Signer authentication is concretely documented — access-code challenge pairs, SMS codes in E.164 format and SSO in the bulk-send setup — and identity verification is a documented product with a supported-countries and ID-documents section, plus external verification through named providers such as Validated ID, Asseco and DIGIPASS. We found no public information on retention or deletion of identification data, the assurance level per method, or the identification provider listed as a subprocessor. 2 4 5 6
The Integration Engineer
Bulk sending documents authentication by access code, SMS and single sign-on, and identity verification runs through named external providers such as Validated ID, Asseco and DIGIPASS, with a dedicated supported-countries-and-ID-documents area whose lists come from those providers. We found no public information on retention or deletion of identification data, or on whether one identification can be reused for later signatures. 4 5 6
The Data Protection Officer
SMS, challenge-question and SSO authentication are documented, and higher-assurance identification runs through named external organizations such as Validated ID, Asseco and DIGIPASS, with a supported-countries and ID-documents section sourced from those providers' own lists, which OneSpan does not test itself. The who is visible; the afterwards is not — we found no public information on retention or deletion of identity data, reuse of an identification, or the ident providers' status as listed subprocessors. 4 5 6 2
The Skeptic
Signers can be held to SMS, access-code or SSO checks, identity-verification documentation with supported countries and ID documents exists, and Validated ID, Asseco and DIGIPASS are named as external verification routes. We found no public information on who performs identification per country and level, on retention or deletion of ID data, or on an identification provider listed as subprocessor. 4 5 6
Signing workflow & signer experience
Show reasoningHide reasoning
How this is scored
Getting a document out and back signed: templates and form fields, signing order and roles, bulk sending, reminders and delegation, signing without an account or app, mobile signing, and accessibility for signers.
0 — Not a signing workflow: the product signs a document locally for the user and sends nothing out to other signers.
3 — Documents sent to one or more signers by email with fields placed on the PDF; templates, signing order and reminders are basic or not described.
5 — Templates with field placement, several signers with a signing order, automatic reminders, signing in the browser on mobile without an account, and a status overview for the sender.
8 — Roles and conditional fields, parallel and sequential order, bulk sending, delegation and substitute signers, team and approval workflows, a branded signer experience, signer languages listed, and signer accessibility addressed.
10 — The workflow is complete and documented: web forms and self-service signing links, mixed signature levels within one process, in-person and remote signing, a published accessibility conformance statement, and team administration with shared templates and audit of sender actions.
The Legal Counsel
Templates with placeholder roles, editable signer and document ordering, and a bulk-send engine documented down to queue timing and hourly capacity show a serious production workflow. The captured pages do not show delegation or substitute signers, conditional fields, signer-facing languages listed, or any accessibility statement, which keeps this below the level I would call complete. 6 7 10
The HR Operations Lead
Bulk sending from templates via CSV with placeholder roles, automatic field population and roughly 3000 transactions per hour is documented in real depth, and signing order with sequential notification is editable — exactly what two hundred contracts a year needs. We found no public information on automatic reminders, delegation, mobile signing without an account or app, or signer accessibility. 6 7 10
The Revenue Operations Lead
The core loop is there and documented: templates with placeholder roles and signature fields, an editable signing order where the next signer is notified automatically once the previous one completes, and a bulk send that turns one template plus a CSV into a queue processing roughly 3000 transactions per hour, with sender-side views for templates, packages and status notifications. We found no public information on automatic reminders, delegation or substitute signers, or on signers signing in a browser on mobile without an account. 6 7 10
The Integration Engineer
Signing order for multiple signers and per-document ordering are well documented and editable after creation, with the next signer notified only after the previous one completes, and bulk sending from eligible templates via CSV is documented down to queue behaviour and hourly throughput. We found no public information on automatic reminders, delegation, conditional fields, signer languages or accessibility, which keeps the workflow short of what I would call complete for a portal deployment. 6 7 10
The Data Protection Officer
Templates with signature fields and placeholder roles, an editable signing order with sequential notification, bulk sending from CSV with per-signer authentication, and a notifications view showing package status are all documented. We found no public information on automatic reminders, mobile or account-free signing, delegation, or signer accessibility. 6 7 10
The Skeptic
Templates with automatic field population, an editable signing order with sequential notification of the next signer, roles-based account administration and bulk send of approximately 3000 transactions per hour from a CSV are documented. We found no public information on reminders, delegation or substitute signers, mobile or no-account signing, signer languages, or accessibility for signers. 6 7 9 10
Evidence, validation & retention
Show reasoningHide reasoning
How this is scored
What proves a signature years later: the audit trail and certificate of completion, qualified timestamps, long-term validation (PAdES-LTV), validation reports, and how long signed documents and evidence are kept — and whether they can leave the platform.
0 — No evidence produced: by the vendor's own description the result is a flattened PDF with a signature image and no audit trail or certificate.
3 — An audit trail or completion certificate with the signed PDF; its contents, timestamps and the retention period are basic or not described.
5 — An audit trail or certificate of completion recording signer events, time and authentication method, attached to or embedded in the signed PDF, timestamps applied, and signed documents downloadable.
8 — PAdES signatures with long-term validation, qualified timestamps from a named provider, a validation tool or report, retention period stated and configurable with automatic deletion, and bulk export of documents with their evidence.
10 — Evidence outlives the subscription: LTV and archive timestamps documented, validation verifiable with independent tools such as the EU DSS validator, export to a DMS or archive with evidence intact, and post-termination access and deletion committed in the terms.
The Legal Counsel
An evidence pack retrievable by API — full transaction audit trail, signer session recordings and identity validation data — plus retention rules configurable per transaction state with automatic overnight purge and plan-dependent permissions is genuinely good practice. But I found no long-term validation, no qualified timestamps from a named provider and no validation report, so whether this evidence still validates when a contract is disputed in eight years is undetermined by the pages I read. 8 9
The HR Operations Lead
A single evidence pack containing the full audit trail, signer session recordings and identity validation data is retrievable as a PDF after completion, and retention is configurable per transaction state with a 120-day default and plan-dependent settings, plus a warning seven days before permanent deletion. We found no public information on long-term validation, qualified timestamps or an independent validation report, which I would want for fixed-term contracts that must hold up years later. 8 9
The Revenue Operations Lead
Evidence is real and retrievable — a single evidence pack per transaction containing the full audit trail, signer session recordings and identity validation data, downloadable as a PDF via the API after completion — and retention is unusually concrete: a 120-day default, configurable per state (Draft, Declined, Expired, Completed, Archived), overnight purge with at least 7 days' warning, and plan-tiered control over the settings. We found no public information on long-term validation, qualified timestamps from a named provider, or a validation tool or report. 8 9
The Integration Engineer
This is the part I care about most: a documented API endpoint returns a single evidence pack as a PDF containing the full transaction audit trail, signer session recordings and identity validation data, callable repeatedly once the transaction is completed, which is exactly the export-with-evidence shape I need for archiving into the document management system. Retention is configurable per transaction state with stated defaults, purge warnings and plan-dependent permissions; we found no public information on long-term validation, qualified timestamps, or validation reports from independent tools. 8 9
The Data Protection Officer
A completed transaction yields an evidence pack combining the full audit trail, signer session recordings and identity validation data, retrievable repeatedly as PDF via the API, and retention is configurable per transaction state with a 120-day default, permanent overnight purge and a 7-day warning. We found no public information on long-term validation, qualified timestamps or validation reports, and a 120-day default before permanent deletion — which Professional-plan users cannot fully change — is thin protection for evidence that must survive a dispute. 8 9 10
The Skeptic
A completed transaction yields a single evidence pack by API containing the full audit trail, signer session recordings and identity validation data, and retention is configurable per transaction state with permanent deletion, a seven-day purge warning and Business-versus-Professional differences. We found no public information on long-term validation (PAdES-LTV), qualified timestamps from a named provider, or a validation tool or report. 8 9
Integrations & API
Show reasoningHide reasoning
How this is scored
Signing from inside the systems where contracts are made: a documented API with webhooks and a sandbox, embedded signing, and connectors for Microsoft 365, CRM, HR, DMS and ERP systems.
0 — A closed web app by the vendor's own description: no API and no integrations offered.
3 — A few named integrations or a Zapier or Make connector; a documented API is basic or not described.
5 — A documented REST API with webhooks, plus named integrations with Microsoft 365 or Google Workspace and at least one CRM, HR or storage system.
8 — A sandbox, embedded signing in the customer's own application, API access to every signature level, versioned API with rate limits published, SDKs, and connectors for named DMS, ERP or HR systems with their scope.
10 — Integration is a product: white-label and embedded flows documented, API parity with the web app, a status page with incident history, deprecation policy, and a marketplace of integrations with stated maintainers.
The Legal Counsel
The REST API is real and documented — package creation, role ordering, bulk send and evidence retrieval with status codes — supported by four SDKs and connectors for Microsoft Dynamics CRM across three versions and SharePoint, with an on-premises deployment path for the CRM integration. The captures show no sandbox, no webhooks, no published rate limits and no embedded signing in the customer's own application. 7 8 6 10 11
The HR Operations Lead
A documented REST API with concrete endpoints and status codes, Java,.NET and APEX SDKs, connectors for Microsoft Dynamics CRM in several versions, and SharePoint integration are all published. We found no public information on webhooks, a sandbox, or embedded signing in a customer's own application. 7 8 9 10 11
The Revenue Operations Lead
Signing from inside the CRM is documented rather than promised: a Microsoft Dynamics CRM connector for versions 2013, 2015 and 2016 covers creating packages, adding signers, managing documents, templates and status notifications, with a SharePoint integration alongside, and the REST API shows real endpoints for package creation, role workflow updates, evidence retrieval and retention rules plus Java,.NET and APEX SDKs, with bulk send triggerable from the API. We found no public information on a sandbox, published rate limits, or embedded signing in our own application. 7 8 9 10 11
The Integration Engineer
There is a genuinely documented REST surface — creating packages with ordered roles, updating the role workflow, triggering bulk sends, setting data-retention rules and fetching the evidence pack, with documented status codes — plus Java,.NET and APEX SDKs, a Microsoft Dynamics CRM connector covering the 2013 to 2016 versions, a SharePoint integration, an out-of-the-box integration platform and an on-premises deployment option for the connector. However, we found no public information on webhooks, a sandbox, API versioning or published rate limits, and no documented embedded signing for the customer's own application rather than inside Dynamics. 6 7 8 9 10 11
The Data Protection Officer
The REST API is documented down to concrete endpoints for package creation, role ordering and evidence retrieval, backed by Java,.NET and APEX SDKs, with connectors for Microsoft Dynamics CRM and SharePoint and an on-premises deployment path; data-retention rules are even manageable through the API. We found no public information on webhooks, a sandbox, rate limits or API versioning. 7 8 10 11
The Skeptic
A REST API with documented package, role, evidence and retention endpoints, Java,.NET and APEX SDKs, an out-of-the-box integration platform and connectors for Microsoft Dynamics CRM (2013 through 2016) and SharePoint are documented. We found no public information on a sandbox, webhooks, published rate limits, or embedded signing outside the CRM connector. 7 10 11
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity, the trust service provider and their owners are, where documents, audit trails and ID data are stored and processed, and who the subprocessors are. Independently sourced by the sovereignty pipeline.
0 — Proven non-EU on every dimension the evidence covers: non-EU contracting entity and non-EU storage of documents and signer data, with no EU option stated.
3 — One European element proven: an EU contracting entity or EU representative, EU data storage stated, an EU qualified trust service provider, or a published DPA, with the rest of the chain unstated.
5 — EU contracting entity or EU representative and EU storage of documents stated as standard or selectable, with a DPA offered; the hosting, identification or trust service chain is unstated or partly non-EU.
8 — EU entity, documents, audit trails and ID data stored in named EU data centres, an EU qualified trust service provider, subprocessor list with locations published, and certifications (ISO 27001, ETSI conformity) published.
10 — Sovereign end to end and evidenced: European ownership, EU entity and EU QTSP, every processing location and subprocessor European, customer-selectable data residency, and certifications with their scope published.
The Legal Counsel
The only proven fact on the chain of custody is a legal address in Boston, USA; the captured pages state no storage location for documents and audit trails, no subprocessor list and no EU contracting or hosting option. For a European legal practice deciding which contracts may be signed here, that is not enough to clear any sovereignty bar. 1 2
The HR Operations Lead
The only published fact on the vendor's own chain is a postal address in Boston, USA; we found no public information on the contracting entity's jurisdiction, data residency, hosting options or a data processing agreement. itsme and Swisscom appear as third-party trust service providers that can be integrated, which does not establish where my contracts and signer data would sit. 1 2
The Revenue Operations Lead
The captured pages give a Boston, USA address for the company and name no European entity or EU representative. We found no public information on where documents, audit trails and identification data are stored or processed, on a published data processing agreement, or on subprocessors and their locations. 1 2
The Integration Engineer
The only location fact the captured pages provide is the vendor's postal address in Boston, USA; we found no public information on where documents, audit trails and identification data are stored or processed, on a data processing agreement, on the trust service chain, or on subprocessors. The on-premises deployment option shown for the CRM connector is the sole hosting flexibility visible in the evidence. 1 2 11
The Data Protection Officer
The only sovereignty fact the captured pages prove is a Boston, Massachusetts postal address under the OneSpan name, with Swisscom appearing only as an integrable trust service provider and Belgium's itsme only as a regulatory example. We found no public information on where documents, audit trails or identity data are stored, on subprocessors and their locations, or on a data processing agreement and certifications. 1 2
The Skeptic
The only entity fact on the captured pages is a Boston, USA address for OneSpan; we found no public information on where documents, audit trails and signer data are stored, on hosting options, or on a published DPA. The European trust providers mentioned, Swisscom and itsme, appear as integration examples in an eIDAS explainer, not as parts of OneSpan's own processing chain. 1 2
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the cost of their signing volume from public pages alone — plan prices, envelope or document limits, the per-signature price of AdES and QES, identification fees, API pricing and overage.
0 — No public prices at all; every plan is a sales conversation.
3 — A public "from" price or one priced plan, per user or flat.
5 — Plan prices public for the main plans with the billing period stated and the envelope or document limits and main features per plan listed.
8 — Every plan and limit priced publicly, AdES and QES priced per signature, identification fees and overage stated, API pricing published, and contract term and notice period given.
10 — Complete cost computability: the cost of a given monthly volume per signature level derivable from public pages, volume tiers published, and every add-on and price-change term on a public page.
The Legal Counsel
The pages name Professional and Business plans — because their data-retention permissions differ — and document bulk-send limits and file sizes, but I found no public price figure: no plan prices, no per-signature price for advanced or qualified signatures, no identification fees. A buyer cannot compute the cost of their signing volume from what was captured. 9 6
The HR Operations Lead not rated — no public information
We found no public pricing information on the pages we read: plan names such as Business and Professional appear in the documentation, but no plan price, per-signature fee, identification fee or billing terms are published there, so I cannot know the cost of a qualified signature before the contract goes out. 1 9
The Revenue Operations Lead
The captured pages name Professional and Business plans and state a bulk-send file limit of 8 MB, but we found no public pricing information for any plan, signature level, identification method or API use. From these pages I cannot begin to compute what a quarter's signing volume would cost. 6 9
The Integration Engineer
The captured pages name Professional and Business plans — with data-retention permissions differing between them — and gate bulk sending behind account enablement, but show no price figures, per-plan limits, per-signature costs for advanced or qualified signatures, or API pricing. A buyer cannot compute the cost of any signing volume from the pages captured. 6 9
The Data Protection Officer
The data-retention documentation distinguishes a Professional plan from a Business plan by which retention settings users may change, and that is the only plan information on the captured pages. We found no public prices, envelope or document limits, per-signature fees or billing terms for either plan, so a buyer cannot compute any cost from these pages. 1 9
The Skeptic
Professional and Business plans are named and limits such as an 8 MB CSV maximum and approximately 3000 transactions per hour are stated, but we found no public information on any plan price, per-signature fee for advanced or qualified signatures, identification fee, overage, or contract term. A buyer cannot compute any cost from these pages. 6 9
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about OneSpan Sign
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), Signicat Sign (3/5) and Youtrust (Yousign) (3/5) 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 (EU-Made, Austria). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: OneSpan Sign alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 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. Know more? Tell us
- 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. Know more? Tell us
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.onespan.com Checked 10 Nov 2026 Details →
- 2 EIDAS levels & trust services — found from sitemap www.onespan.com Checked 10 Nov 2026 Details →
- 3 EIDAS levels & trust services — found from sitemap docs.onespan.com Checked 10 Nov 2026 Details →
- 4 Signer identification — found from sitemap docs.onespan.com Checked 10 Nov 2026 Details →
- 5 Signer identification — found from sitemap docs.onespan.com Checked 10 Nov 2026 Details →
- 6 Signing workflow & signer experience — found from sitemap docs.onespan.com Checked 10 Nov 2026 Details →
- 7 Signing workflow & signer experience — found from sitemap docs.onespan.com Checked 10 Nov 2026 Details →
- 8 Evidence, validation & retention — found from sitemap docs.onespan.com Checked 10 Nov 2026 Details →
- 9 Evidence, validation & retention — found from sitemap docs.onespan.com Checked 10 Nov 2026 Details →
- 10 Integrations & API — found from sitemap docs.onespan.com Checked 10 Nov 2026 Details →
- 11 Integrations & API — found from sitemap docs.onespan.com Checked 10 Nov 2026 Details →