The two software layers of signature capture
Every signature pad deployment has two software layers. The lower layer is the device SDK: the software interface that lets your application talk to the pad, capture pen data, and control the display. The upper layer is the signing application itself: the program where the document is shown and the signature is collected, which may be a custom-built teller system, a standard office application, or a web page. Understanding which layer does what keeps integration projects on schedule, because the two layers are tested and deployed differently. Our signature pad SDK page is the starting point for the lower layer; this article covers both.
The customizable SDK: the DS1020 example
The official product description for the DS1020 states that its SDK is customizable to realize application of the DS1020 in different situations. In practice, that means the SDK is not a fixed demo program but an integration kit your developers adapt to the workflow: capturing the signature image together with the underlying pen data, embedding the signing step into an existing teller or admissions application, controlling what appears on the pad display, and handling events such as pen-down, pen-up, and press-key input.
The DS1020 itself is a 10.1-inch counter pad with a 1280 by 800 IPS display, 5080 LPI pen resolution, a 233PPS report rate, and a user-defined 512-to-4096 pressure range, using the battery-free PEN57 pen with 4096-level pressure and 233PPS. It connects over USB-A with a single cable for power, and supports Windows 7 or later. When scoping an SDK project, confirm the operating system baseline first: the DS line supports Windows 7 or later across the range, while the DS101S, DS1610, and DS1640 additionally support macOS. If your environment includes other platforms or private deployment requirements, the DS1040 product description notes support for many operating systems, CPUs, and private deployments, plus synchronization and integration with various ERP software systems.
Signing where users already work: Word, Excel, PDF, and browsers
Not every deployment needs a custom application. The official product description for the DS530 states that, owning strong compatibility, the DS530 helps users sign the files in Word, Excel, PDF, and other formats and on the web pages of major browsers. The DS530S carries the same compatibility statement and adds the high-precision fingerprint recognition module for quick and accurate fingerprint collection. For IT teams, this is the fast path: the pad works inside the office applications and browser-based systems staff already use, with the 2048-level pressure-sensitive, battery-free EMR pen capturing the signature and the 233PPS report rate ensuring instant capture of every pen movement without any lagging.
This compatibility layer suits deployments where the signing step is added to existing document workflows rather than rebuilt: branch offices signing standard forms, HR departments collecting acknowledgments, or service desks working inside a web-based CRM. When the workflow needs deeper control, such as driving the pad display from a teller application or binding the signature to a transaction record, that is where the SDK layer takes over.
A generic integration checklist
Integration projects differ, but experienced IT teams follow a similar sequence. First, define the signing use case precisely: which documents, which counters or field roles, and what identity checks surround the signature. Second, select the hardware against that definition, using the published specifications: panel size, pressure levels, fingerprint option, interface, and OS support. The comparison table below collects the software-relevant attributes of the DS line in one place.
Third, decide which software layer you need: application compatibility for standard office and browser workflows, the customizable SDK for embedding signing into proprietary systems, or both. Fourth, build a pilot on the actual target machines, because driver behavior, display scaling, and USB port power can vary between the lab and the branch. Fifth, validate the captured data end to end: the signature image, the underlying pen data, and the way both are stored with the document. Sixth, plan rollout in waves, with staff training on the signing step itself; the 4 programmable press keys on the DS101S exist precisely to make the counter workflow fast and intuitive. Throughout, keep the compliance principles from our signature capture guide in view: consent, identity binding, record integrity, retention, and legal review in each market.
Device features your integration will rely on
| Model | OS support | Interface | Pressure / report rate | Fingerprint | Integration notes |
|---|---|---|---|---|---|
| DS1020 | Windows 7 or later | USB-A, single-cable power | 512 to 4096 user-defined, 233PPS | Not listed | SDK is customizable per official description |
| DS101S | Windows 7 or later; macOS supported | USB-A | 512 to 4096 user-defined, 233PPS | Optional, 192 x 192 | 4 programmable press keys |
| DS1030 | Windows 7 or later | USB-A | 512 to 4096 user-defined, 233PPS | Optional, 192 x 192 | 5MP portrait plus 5MP document camera; optional ID card reader |
| DS1031 | Windows 7 or later | USB-A | 512 to 4096 user-defined, 233PPS | Optional, 192 x 192 | 2MP camera for facial photo capture |
| DS1040 | Many operating systems and CPUs; private deployments | Type-C, USB-A x 2 | 8192 levels, 233PPS | Not listed | ARM 4 CPU; ERP synchronization and integration |
| DS1610 | Windows 7 or later; macOS 10.11 or later | HDMI | 8192 levels, 233PPS | No | 15.6 inch 1920 x 1080; black and white housings |
| DS1640 | Windows 7 or later; macOS 10.11 or later | HDMI | 8192 levels, 233PPS | Yes | 15.6 inch 1920 x 1080; black and white housings |
| DS530 | Windows 7 or later | USB-C | 2048 levels, 233PPS | No | Signs Word, Excel, PDF, and browser web pages per official description |
| DS530S | Windows 7 or later | USB-C | 2048 levels, 233PPS | 192 x 192 | Same application compatibility plus fingerprint module |
| DS510 / DS510S | Windows 7 or later | USB-C | 2048 levels, 233PPS | No / 192 x 192 | 5 inch mobile pads for door-to-door business |
Working with the B2B team
Signature projects are rarely off-the-shelf purchases: volumes, customization, SDK access, and support terms are agreed per project. Pilot units are the normal way to start: run the SDK path or the application compatibility path on your own machines, confirm that the captured data meets your record-keeping rules, and then scale to the full fleet with staff training on the signing step. The B2B line is built for this, with product customization and SDK work as part of the offering, and the OEM and ODM program covering deeper hardware customization. For deployments that combine signature capture with identity checks, see our signature pads with fingerprint page; for the full hardware range, see signature pads.
What does "SDK is customizable" mean for the DS1020?
Per the official product description, the DS1020 SDK is customizable to realize application of the DS1020 in different situations. It is an integration kit your developers adapt: capturing signature data, embedding the signing step into existing applications, and controlling the pad display, rather than a fixed end-user program.
Can users sign Word, Excel, and PDF files directly?
Yes, on the compatible models. The official DS530 description states that it helps users sign the files in Word, Excel, PDF, and other formats and on the web pages of major browsers. The DS530S offers the same compatibility with an added fingerprint module.
Which operating systems do the signature pads support?
Windows 7 or later across the DS line. The DS101S, DS1610, and DS1640 additionally support macOS. The DS1040 supports many operating systems, CPUs, and private deployments, and synchronizes with various ERP software systems according to its product description.
How should we plan an SDK integration project?
Define the signing use case, select hardware against published specifications, decide whether you need application compatibility, the SDK, or both, then pilot on the actual target machines, validate captured data end to end, and roll out in waves with staff training. Keep consent, identity binding, record integrity, and retention requirements in view throughout.
Can the hardware itself be customized for our project?
Yes. Product customization is part of the B2B offering, and deeper hardware work goes through the OEM and ODM program. The company profile states that Huion began by providing professional OEM and ODM solutions to apply EMR technology in different industries. Contact us with your volumes and requirements.