E-Signature
Viafirma Documents
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Viafirma S.L. · www.viafirma.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.
Viafirma Documents at a glance
- Vendor
- Viafirma S.L.
- Headquarters
- Not stated on the vendor’s pages as of 20 Oct 2026
- Data hosting
- Not stated on the vendor’s pages as of 20 Oct 2026
- Free plan
- Not stated on the vendor’s pages as of 20 Oct 2026
- Panel verdict
- The AI panel rates Viafirma Documents 2.5/5, the mean of 6 judges. Viafirma Documents scores highest on evidence and retention at 7: each signature carries a sealed, downloadable audit, qualified timestamps from the provider acting as its own qualified trust service provider, XAdES long-term formats up to LTA, administrator-configurable retention, and transfer of finished documents to the customer's own repositories. how scores are made
- As of
- Vendor pages captured 20 Oct 2026; evaluated by the panel 21 Oct 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Viafirma Documents scores highest on evidence and retention at 7: each signature carries a sealed, downloadable audit, qualified timestamps from the provider acting as its own qualified trust service provider, XAdES long-term formats up to LTA, administrator-configurable retention, and transfer of finished documents to the customer's own repositories. Signing workflow scores 6 on policy-driven templates, approval steps and bulk CSV sending by email, SMS or WhatsApp. Signature levels score 5 to 6 — simple, advanced and qualified are labelled, backed by the 2019 AENOR audit under ENAC and validation by Spain's Ministry of Industry — though which plan or country offers which level is not shown. The judges differ most pointedly on sovereignty, scored 2 to 3: the data protection officer's 2 reflects no public information on storage locations or subprocessors, against offices listed in Colombia, the Dominican Republic and Mexico. Identity verification holds at 5 with Spain-shaped methods; integration and API scores 5 to 6 on a REST API with no public information on a sandbox or SDKs. No prices appear beyond a free trial and a free personalized demo.
Speaks for it
- Sealed audit trail for each signature, downloadable for offline access, with qualified timestamps from Viafirma as its own qualified trust service provider
- Evidence signed in XAdES long-term formats up to LTA, with administrator-configurable retention and the option to keep documents in your own environment
- All three eIDAS levels — simple, advanced and qualified — labelled, with a 2019 AENOR audit under ENAC and validation by Spain's Ministry of Industry
- Bulk CSV sending with per-recipient template customization and delivery by email, SMS or WhatsApp
- Documented REST API with Basic and OAuth v2 authentication, per-signer callback notifications, and automatic transfer of finished documents to FTP or SharePoint
Held against it
- We found no public information on which plan or country offers which signature level, or on qualified electronic seals
- Identification is Spain-shaped, with no public information on who performs video identification or on retention and deletion of identification data
- We found no public information on where documents, audit trails and identification data are stored, on a subprocessor list or on ownership, beside offices listed in Colombia, the Dominican Republic and Mexico
- We found no public information on signing order, automatic reminders, expiry or delegation within a request
- We found no public information on an API sandbox, SDKs, rate limits or API versioning
Best for
- You need qualified e-signatures under eIDAS with a sealed audit and long-term XAdES evidence, such as employment contracts or tenancy agreements
- You run high-volume signature cycles, such as annual HR contracts, from CSV lists with per-recipient customization and email, SMS or WhatsApp delivery
- You want finished documents and audit files kept in your own repositories via automatic FTP or SharePoint transfer, with retention you set as administrator
- Your signers are in Spain and can identify through Cl@ve or the electronic DNI
Avoid if
- Your signers are mostly outside Spain and you need per-country identification methods and accepted documents documented before purchase
- Your procurement requires published data-residency commitments and a subprocessor list, and the listed offices in Colombia, the Dominican Republic and Mexico appear with no data-processing statement
- You must budget from public prices before engaging sales, and only a free trial and a free personalized demo appear on the captured pages
The scores
| Criterion | Panel median |
|---|---|
| eIDAS levels & trust services | 3 of 5 |
| Signer identification | 2.5 of 5 |
| Signing workflow & signer experience | 3 of 5 |
| Evidence, validation & retention | 3.5 of 5 |
| Integrations & API | 2.5 of 5 |
| European sovereignty | 1.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 — No signature level named; the platform calls its signature "legally binding" without saying which kind it is.
3 — Simple signatures by default with "advanced" or "qualified" mentioned as available, but no trust service provider named and no statement on which plan or country offers which level.
5 — SES, AdES and QES offered and labelled in the product, the qualified trust service provider named, and which documents need which level explained for at least Germany or the EU.
8 — Every level documented with the plans and countries it is available in, the QTSP's 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 printed 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
Viafirma names itself as a Qualified Trust Service Provider, accredited through AENOR under ENAC and validated by the Spanish Ministry of Industry, and labels simple, advanced and qualified signatures in the product, with the legal effect and cross-border recognition of the qualified level explained at EU level. We found no public information on the EU Trust List entry link, on which plans or countries offer which level, or on qualified electronic seals, which is the mapping I need before deciding per jurisdiction. 2 3 9
The HR Operations Lead
Simple, advanced and qualified signature are all offered and labelled, the FAQ explains the qualified signature's legal effect and cross-border recognition, and the provider is itself a qualified trust service provider with an AENOR audit under ENAC and validation by Spain's Ministry of Industry published. But we found no public information on which plan or country delivers which level, on qualified electronic seals, on ZertES, or on a linked EU Trust List entry. 2 3 9
The Revenue Operations Lead
All three eIDAS levels are named and labelled — simple, advanced, qualified — and Viafirma names itself as a Qualified Trust Service Provider for qualified timestamping, backed by an AENOR audit under ENAC accreditation and validation by Spain's Ministry of Industry. What a buyer still can't see is the mapping: which plan carries which level, and which document types call for qualified signing, is not explained on the captured pages. 2 3 9
The Integration Engineer
Simple, advanced and qualified signatures are all named and labelled, the legal effect of the qualified level and its cross-border recognition are explained, and Viafirma presents itself as a qualified trust service provider whose conformity was audited by AENOR under ENAC accreditation and validated by the Spanish ministry. We found no public information on which plans or countries offer which level, on qualified seals for company documents, or on a link to the EU Trust List, so level availability per plan stays invisible to a buyer. 2 3 9
The Data Protection Officer
All three eIDAS levels are labelled and the provider acts as its own qualified trust service provider, with the 2019 AENOR audit, ENAC accreditation and Spanish Ministry validation published alongside qualified timestamping and the QES equivalence rule. I found no public information on which plan or country offers which level, on the provider's entry on the EU Trust List, on qualified electronic seals, or on which level is printed in the signed document and audit trail. 2 3 9
The Skeptic
Simple, advanced and qualified signatures are named with their legal effects spelled out, and the provider says it is itself a qualified trust service provider for timestamping, with an AENOR audit under ENAC and validation by Spain's Ministry of Industry from 2019. We found no public information tying a signature level to a plan or country, on qualified seals, on the EU Trust List entry, or on ZertES coverage. 2 3 9
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 — Email link only; no statement on how signers are authenticated.
3 — Email plus SMS or access code, with "ID verification" mentioned as an add-on but no methods, provider or countries named.
5 — Identification methods for AdES and QES listed by name (for example video ident, eID, bank ident), the identification provider named, and the countries or ID documents they accept stated.
8 — Methods documented per level and country, 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 failure rate or completion guidance, EUDI wallet and national eID supported, ID data minimisation and retention committed, and the signer-facing privacy notice published.
The Legal Counsel
Methods are named — email and SMS one-time codes, static access codes, biometric video identification, and for Spain the electronic DNI and Cl@ve with DNI, NIE and NIF documents accepted — and identity-validation integrations are named as CIFIN, LISIM and Experian. We found no public information on which method applies to which signature level and country, on retention or deletion of identification data, or on an automated-versus-agent distinction for video identification. 4 5
The HR Operations Lead
Methods are named — biometric video identification against the legal ID card, redirection to Spain's Cl@ve or DNIe, the electronic DNI, and OTP by SMS or email — with accepted documents listed (DNI, NIE, NIF) and a check of the signer's certificate against a pre-supplied identity number. The picture is Spain-shaped: for other markets we found no public information on accepted ID documents, the video ident provider is not named, and we found no public information on retention or deletion of ID data; some services also require contacting the vendor to enable. 4 5
The Revenue Operations Lead
Methods are listed by name — biometric video identification, Cl@ve and the electronic DNI for Spain, OTP by SMS or email, static access and completion codes, and a certificate-versus-ID-number check — with the accepted Spanish ID documents (DNI, NIE, NIF) stated. I found no public information naming the video identification provider (the named providers are financial-scoring integrations such as Experian), on per-level identification requirements per country, or on what happens to ID data after signing. 4 5
The Integration Engineer
Methods are listed by name — email link, SMS or WhatsApp link, OTP by SMS or email, static codes, biometric video identification and Spanish eID via Cl@ve or DNIe — with ID documents DNI, NIE and NIF named and third-party identity validation integrations CIFIN, LISIM and EXPERIAN mentioned. We found no public information mapping methods to signature levels and countries beyond Spain, on who performs the video identification, or on retention or deletion of identification data, and some services are stated to require contacting the vendor to enable. 4 5
The Data Protection Officer
Methods are named — email and SMS or WhatsApp delivery, OTP, static access and completion codes, biometric video identification, Cl@ve and DNIe for Spain, and certificate data checked against a pre-supplied ID number — with Spanish ID documents listed and methods tied to the signature modality chosen. I found no public information on who performs the video identification, on retention or deletion of identification data afterwards, or on the identification providers' place in the subprocessor chain, and several services require contacting sales to enable. 4 5
The Skeptic
Video ident, Cl@ve, DNIe, OTP by SMS or email and certificate checks are named as identification and authentication mechanisms, with Spanish ID documents listed and a redirect to each country's authentication page described. We found no public information on who performs the video identification, on methods for countries other than Spain, or on retention and deletion of ID data. 4 5
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 — Single-recipient signing of an uploaded PDF; no templates, order or reminders.
3 — Multiple signers and basic templates, but no signing order, no bulk send, and signers must create an account.
5 — Templates with field placement, sequential and parallel signing order, automatic reminders and expiry, signing without an account on mobile, and a status overview for the sender.
8 — Roles and conditional fields, bulk sending, delegation and substitute signers, team and approval workflows, 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 carry configurable policies with evidence fields positioned via Acroforms, dynamic variables filled from forms or external systems, approvals required before completion, and bulk sending by CSV with per-recipient customization and email, SMS or WhatsApp delivery, on multiple devices. We found no public information on sequential or parallel signing order, automatic reminders, delegation to substitute signers, signer languages or accessibility for signers. 6 7 10
The HR Operations Lead
Bulk sending from a CSV with per-recipient template customisation and email, SMS or WhatsApp delivery matches my annual contract volume, and templates carry field placement, dynamic variables, approvals and multi-signer evidence on a multi-device product. We found no public information on signing order, automatic reminders, delegation within a request, signer languages or accessibility, and nothing on whether a new hire can sign on a phone without creating an account. 1 6 7
The Revenue Operations Lead
The bulk engine is real — CSV upload with a sample file, per-recipient template customization, and delivery by email, SMS or WhatsApp — and templates carry admin-defined policies of evidence, approvals and signature methods, which is exactly the 'sales can't break the template' model I want, with approvals blocking completion until approved. But I found no public information on automatic reminders, expiry, or sequential versus parallel signing order, and nothing on signer branding, languages or accessibility. 6 7 1
The Integration Engineer
The captured documentation shows templates with field placement and dynamic variables, bulk sending by CSV with per-recipient customization and email, SMS or WhatsApp delivery, approval steps by button, code or certificate, conditional validation rules, and evidence assigned per signer in multi-signer requests. We found no public information on signing order, automatic reminders, delegation within a flow, signer languages or accessibility, so bulk and templating are strong while sequencing and chase mechanics stay unevidenced. 6 7
The Data Protection Officer
Templates with policy-defined evidence and field placement, approval steps, multi-signer evidence assignment, and bulk CSV sending with email, SMS and WhatsApp notification are documented, and signers act on links sent to their own email or phone. I found no public information on signing order, automatic reminders and expiry, signer languages, or accessibility for signers. 4 6 7
The Skeptic
Templates with policy-driven evidence and field placement, CSV bulk sending with email, SMS and WhatsApp delivery, approvals by button, code or certificate, and multi-signer evidence assignment are all documented; signers reach documents by link with no account creation mentioned. We found no public information on sequential signing order, automatic reminders, delegation within a request, or signer accessibility. 4 6 7 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 — A signed PDF and nothing else; no audit trail, no statement on storage or deletion.
3 — An audit trail or completion certificate exists, but its contents, the timestamp source and the retention period are unstated.
5 — Audit trail with signer events, IP addresses and authentication method embedded in or attached to the signed PDF, timestamps applied, documents downloadable, and the retention period stated.
8 — PAdES signatures with long-term validation, qualified timestamps from a named provider, a validation tool or report, configurable retention and 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
Each signature carries a sealed audit with event history, signatory data, certificate validity, a permanent audit link and an offline audit PDF download, qualified timestamping is provided by Viafirma as a Qualified Trust Service Provider, XAdES-LT and XAdES-LTA formats are supported, and an administrator can set retention periods with storage delegated to the customer's own repositories. We found no public information on PAdES long-term validation wording, IP addresses recorded in the trail, or validation with an independent tool such as the EU validator. 1 2 7 9 10
The HR Operations Lead
The validation report covers signature status, signatory data, certificate validity or repudiation, event history and a downloadable sealed audit, backed by qualified timestamping from the vendor as trust service provider and XAdES-LT/LTA long-term formats. Retention time is administrator-configurable, with the option to keep signed documents in my own environment or transfer them automatically to my document manager. We found no public information on automatic deletion, independent validation tools, or post-termination access commitments. 2 7 9 10
The Revenue Operations Lead
Evidence is taken seriously: a validation report with signature status, signatory data, certificate validity, public key and full event history, a sealed audit downloadable offline, qualified timestamps from Viafirma as QTSP, XAdES-LT and XAdES-LTA formats, and administrator-configurable retention with the option to push signed documents to your own repository via FTP or SharePoint. Missing for the long haul: IP address and authentication method in the audit trail, a stated retention period, automatic deletion, and any post-termination commitment. 9 2 7 10
The Integration Engineer
The validation service reports signature status, signatory data, certificate validity or repudiation, event history and a downloadable audit that is sealed and available offline, backed by post-signature integrity checks, qualified timestamping from Viafirma as trust service provider, and XAdES long-term formats up to LTA documented for the evidence signature. Retention time is administrator-configurable, and signed documents can be transferred automatically to the client's own document manager with the audit file also delivered by email on completion; we found no public information on PAdES long-term validation for PDFs, default retention periods, or post-termination access commitments. 2 7 9 10
The Data Protection Officer
The validation report lists signer data, certificate validity and event history, the audit is sealed and downloadable for offline access, timestamps are qualified from the provider itself, evidence is signed in XAdES long-term formats, retention is administrator-configurable, and finished documents can be transferred to the customer's own repositories. I found no public information on IP addresses or authentication method in the audit trail, on a default retention period, on PAdES long-term validation for PDFs, or on validation with independent tools. 2 7 9 10
The Skeptic
Qualified timestamps come from the provider's own trust service, XAdES-T, LT and LTA formats are supported, and the validation report covers signature status, certificate validity, document integrity and a sealed audit that can be downloaded for offline access. Retention time is administrator-configurable and documents can be kept in the customer's own environment, but we found no public information on a default retention period, PAdES long-term validation by name, independent validation tools, or post-termination access. 2 7 9 10
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 — No API and no integrations; everything happens in the vendor's web app.
3 — A few named integrations or a Zapier connector, and an API mentioned without public documentation.
5 — A documented REST API with webhooks and a sandbox, plus connectors for Microsoft 365 or Google Workspace and at least one CRM or HR system named.
8 — 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
A documented REST API with callback notifications on every signer event, OAuth v2 or Basic authorization, an external code for traceability, forms pre-filled from external systems, and automatic transfers to SharePoint or FTP claims most of the product's functionalities, complemented by CRM and ERP integration options including SAP and a status page. We found no public information on a sandbox, SDKs, published rate limits or API versioning. 1 9 10
The HR Operations Lead
There is a documented REST API with Basic and OAuth v2, a callback URL that fires as each signer completes, form fields fillable from an external CRM, and automatic transfer of finished documents to SharePoint or FTP. We found no public information on a sandbox, SDKs, rate limits, API versioning or embedded signing, and no named HR system connector — SAP and generic CRM/ERP are mentioned without scope. 1 9 10
The Revenue Operations Lead
The REST API is publicly documented with OAuth 2, a callback URL that posts on each signer completion and at final status, an external code for CRM traceability, form data injection from external systems, and automatic document transfer to SharePoint or FTP — that is the mechanism for signing from inside the CRM. I found no public information on a sandbox, SDKs, rate limits or API versioning, and connectors are generic transfers rather than named CRM or HR integrations with scope. 10 9 1
The Integration Engineer
A public quick-integration guide documents a REST API with Basic and OAuth v2 authentication, a callback URL that posts on each signer completion and final status, an external-code attribute for traceability, form filling from external systems, and automatic transfer of finished documents to the client's document manager via FTP or SharePoint, with CRM, SAP and web or desktop applications named as integration targets. We found no public information on a sandbox, API versioning, rate limits, SDKs, or embedded signing inside the customer's own portal, and no statement that every signature level is reachable through the API; a service status page exists but we found no incident history. 1 9 10
The Data Protection Officer
A documented REST API covers most product functionality with Basic and OAuth v2 authentication, per-signer callback notifications, form prefill from external systems, and automatic transfer of finished documents to FTP or SharePoint, alongside generic CRM, ERP and SAP integration. I found no public information on a sandbox, embedded signing, SDKs, API versioning or rate limits. 1 9 10
The Skeptic
The REST API is documented with event callbacks to a URL of your choice, OAuth v2 and Basic auth options, form and acrofield filling from external systems, traceability codes and document transfers to FTP or SharePoint, alongside a service status page. We found no public information on a sandbox, SDKs, rate limits, API versioning, or embedded signing inside the customer's own application. 1 9 10
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 — Non-EU contracting entity, no statement on where documents and signer data are stored, and subprocessors unnamed.
3 — An EU entity contracts, but documents or signer data are processed outside the EU by default without an explained safeguard, or the subprocessor list is absent.
5 — EU contracting entity and EU data storage stated, with a DPA, but the hosting, identification or trust service chain is non-EU-controlled without a stated safeguard.
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 data controller is named as VIAVANSI CORPORACIÓN, S.L., a Spanish entity, and the qualified trust services operate under Spanish AENOR and ENAC accreditation, but the captured pages show company presence in Colombia, the Dominican Republic and Mexico alongside Europe. We found no public information on a subprocessor list with locations, on where documents, audit trails and identification data are stored and processed, or on ISO 27001 certification. 1 2 9
The HR Operations Lead
The contracting and data controller is VIAVANSI CORPORACIÓN, S.L., a Spanish entity, with GDPR compliance claimed, but we found no public information on where signed documents, audit trails and ID data are stored or processed, and no subprocessor list. The vendor's stated presence spans Europe, Colombia, the Dominican Republic and Mexico, and for employment files carrying personal data that silence is a real gap. 1 9
The Revenue Operations Lead
The data controller is VIAVANSI CORPORACIÓN, S.L., a Spanish company, and Viafirma presents itself as a Spanish-validated qualified trust service provider, which is a genuinely European chain. Beyond that the captured pages go quiet: I found no public information on where documents, audit trails or identification data are stored or processed, no subprocessor list, no ownership disclosure, and offices in Colombia, the Dominican Republic and Mexico are listed without any data-processing statement. 9 1 2
The Integration Engineer
The data controller is named as VIAVANSI CORPORACIÓN, S.L., which suggests a Spanish contracting entity, GDPR compliance is claimed, and the trust service was audited by AENOR under Spain's ENAC accreditation. We found no public information on where documents, audit trails and identification data are stored, on ownership, or on subprocessors and their locations, and the vendor also lists offices in Colombia, the Dominican Republic and Mexico. 2 9 10
The Data Protection Officer
The data controller is named as VIAVANSI CORPORACIÓN, S.L. — a Spanish company form — and the AENOR audit under ENAC and the Kit Digital subsidy point to Spain, but transparency ends there. I found no public information on where documents, audit trails and identification data are stored, on ownership, on a subprocessor list, or on what the presence in Colombia, the Dominican Republic and Mexico means for processing; customer-requested identity checks with Experian, CIFIN and LISIM hint at an identification chain for which I found no public disclosure. 2 4 9
The Skeptic
The data controller is VIAVANSI CORPORACIÓN, S.L., a Spanish company, and the trust service chain stays with that Spanish provider, but we found no public information on where documents, audit trails and ID data are stored, on ownership, or on subprocessors. Presence is claimed in Europe, Colombia, the Dominican Republic and Mexico with no data-residency commitment attached. 1 2 9
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 — Plan prices published, but envelope limits, QES and identification fees are unstated — the cost of a qualified signature is unknowable.
5 — Plans with envelope or document limits priced, but at least one commonly incurred cost (per-QES fee, video ident, API access, overage) is missing or "on request".
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 offer a free trial, a personalized demo and mention of the Spanish Kit Digital subsidy, but we found no public information on plan prices, envelope or document limits, the per-signature cost of advanced or qualified signatures, identification fees, or contract term and notice period. A buyer cannot compute any cost from the captured pages alone. 1 9
The HR Operations Lead
The captured pages show a free trial, a free personalised demo and a Kit Digital subsidy mention, but we found no public prices: no plan prices, no envelope limits, and no per-signature cost for advanced or qualified signature or for video identification. I cannot know what a qualified employment contract will cost before sending it, so budgeting is impossible from public pages alone. 1 9
The Revenue Operations Lead
Nothing is priced in public — the captured pages mention only a free trial and a "Request a free, personalized demo". No plan prices, envelope or document limits, per-signature QES fees, identification fees or API pricing appear, so every cost is a sales conversation before a buyer can compute anything. 1 9
The Integration Engineer
A free trial, a free personalized demo and Kit Digital subsidy support are the only cost-related items we found on the captured pages; no plan prices, envelope limits, per-signature fees for advanced or qualified signatures, identification fees or API pricing appear. The cost of any signing volume is therefore a sales conversation rather than computable from public information. 1 9
The Data Protection Officer
No price of any kind is public — only a free trial and a free personalized demo — and enabling identification services requires contacting sales. A buyer cannot compute the cost of any volume at any signature level, and I found no public information on plan prices, envelope or document limits, or the fees for qualified signatures or video identification. 1 4 9
The Skeptic
The only commercial information we found is a free trial and a free personalized demo on request. We found no public information on plan prices, envelope or document limits, per-signature fees for advanced or qualified signatures, identification fees, API pricing, overage or contract terms, so the cost of any signing volume cannot be computed from public pages. 1 9
European sovereignty — proven facts
0 of 4 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 |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Questions about Viafirma Documents
Is Viafirma Documents European?
Not determined: the vendor’s pages as captured do not say where Viafirma Documents is based.
Where does Viafirma Documents store data?
Not stated on the vendor’s pages as of 20 Oct 2026.
Does Viafirma Documents have a free plan?
Not stated on the vendor’s pages as of 20 Oct 2026.
What are the best alternatives to Viafirma Documents?
As of 21 Oct 2026, the panel rates Scrive (3/5), Penneo (2.5/5) and Youtrust (Yousign) (2.5/5) highest among the other 18 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 Scrive (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Viafirma Documents alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 20 Oct 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.
- We found no public information on pricing on the pages we read (viafirma.com, viafirma.com/en/viafirma-qualified-trust-service-provider, viafirma.com/en/faqs/electronic-signature-eidas-regulation-european-union, viafirma.com/en/documentation/how-is-the-identity-of-the-signer-authenticated, viafirma.com/en/electronic-identification-using-the-eidas-system, viafirma.com/en/documentation/bulk-shipments-via-csv and 5 more). If the vendor publishes it somewhere else, send us the page. Know more? Tell us
- 7 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
- 2 support 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
- 1 compliance fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 legal fact could not be confirmed on the vendor’s page as captured and was 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.viafirma.com Checked 20 Oct 2026 Details →
- 2 EIDAS levels & trust services — found from sitemap www.viafirma.com Checked 20 Oct 2026 Details →
- 3 EIDAS levels & trust services — found from sitemap www.viafirma.com Checked 20 Oct 2026 Details →
- 4 Signer identification — found from sitemap www.viafirma.com Checked 20 Oct 2026 Details →
- 5 Signer identification — found from sitemap www.viafirma.com Checked 20 Oct 2026 Details →
- 6 Signing workflow & signer experience — found from sitemap www.viafirma.com Checked 20 Oct 2026 Details →
- 7 Signing workflow & signer experience — found from sitemap www.viafirma.com Checked 20 Oct 2026 Details →
- 8 Evidence, validation & retention — found from sitemap www.viafirma.com Checked 20 Oct 2026 Details →
- 9 Evidence, validation & retention — found from sitemap www.viafirma.com Checked 20 Oct 2026 Details →
- 10 Integrations & API — found from sitemap www.viafirma.com Checked 20 Oct 2026 Details →
- 11 Integrations & API — found from sitemap www.viafirma.com Checked 20 Oct 2026 Details →