Notifications
Clear all
Topic starter
25/06/2026 12:51 am
TL;DR: Dealer management systems increasingly depend on embedded eSignature, but many platforms still struggle with flexibility, branding, integration, and support, according to OneSpan and IDC. The real issue is not signature volume alone but whether the signing layer fits high-volume, partner-branded workflows without creating operational friction.
NHIMG editorial — based on content published by OneSpan: eSignature for dealer management systems and the limitations of the status quo
By the numbers:
Questions worth separating out
Q: How should teams choose eSignature for embedded dealer workflows?
A: Teams should evaluate whether the signing service was built for embedded operation, multi-tenant routing, and branded customer journeys.
Q: Why do multiple eSignature tools create operational risk?
A: Multiple tools fragment support, evidence, branding, and integration logic across the same transaction model.
Q: What should practitioners measure in an embedded signing platform?
A: Measure completion friction, integration maintenance effort, evidence availability, and the number of manual interventions needed per signing flow.
Practitioner guidance
- Map the signing workflow to platform control points Identify where the eSignature step sits in the dealer management journey, including approvals, authentication, evidence capture, and exception handling.
- Test embedded use cases before standardising a provider Run representative high-volume scenarios with branded customer journeys, multi-tenant routing, and renewal events.
- Require evidence and audit outputs in the default flow Confirm that transaction evidence, authentication history, and completion records are available without manual retrieval.
What's in the full article
OneSpan's full article covers the operational detail this post intentionally leaves for the source:
- The comparison of embedded pricing, branding, and support expectations across dealer platform use cases.
- The practical differences between standalone signing flows and OEM or ISV embedded deployments.
- The product-level discussion of compliance, audit trails, and authentication options in high-volume signing.
- The partner-program context behind the vendor's platform positioning and support model.
👉 Read OneSpan's analysis of eSignature for dealer management systems →
Dealer management eSignature: what embedded use cases still miss?
Explore further
25/06/2026 9:54 am
Embedded eSignature is a governance problem, not just a procurement choice. Dealer management systems use signing as part of a broader transaction and approval workflow, so the question is whether the control plane fits the platform's operational model. When it does not, teams inherit friction in support, audit, and customer experience. The practitioner conclusion is to evaluate signing as part of lifecycle and workflow governance, not as a point product.
A few things that frame the scale:
- 71% of NHIs are not rotated within recommended time frames, increasing the risk of compromise over time, according to Ultimate Guide to NHIs.
- Only 20% have formal processes for offboarding and revoking API keys, and even fewer have procedures for rotating them.
A question worth separating out:
Q: What is the difference between standalone and embedded eSignature use?
A: Standalone eSignature is designed around a direct signing experience, while embedded eSignature is designed to sit inside another platform's workflow and branding. The difference matters because embedded use needs APIs, tenant controls, and support for the host application’s customer journey. A mismatch usually shows up as friction, not just feature gaps.
👉 Read our full editorial: eSignature in dealer management systems: why embedded use cases fail
