How to Install ProxKey Digital Signature with signNow

TL;DR

This guide explains how to install and use a ProxKey digital signature solution within signNow workflows, covering setup, device compatibility, security controls, compliance, common troubleshooting, and integration options. It shows step-by-step procedures to add a certificate-based signer, configure authentication, send files for eSignature, and manage audit trails so teams can complete and store signed documents securely.

What is ProxKey digital signature

ProxKey digital signature refers to a hardware-backed or certificate-based signing credential used to create legally binding electronic signatures. In plain terms, it is like a secure key on a smartcard or token that proves the signer’s identity when signing documents online. When combined with signNow, ProxKey can be used as a signer authentication method: the signer presents the certificate during an eSign session and signNow records that authentication in the document audit trail for legal and compliance purposes.

Install and Enable ProxKey

These steps describe how to prepare a ProxKey or certificate-based signer and use it inside signNow to collect legally verifiable eSignatures.

• 01
  Obtain Certificate: Request the ProxKey certificate from your issuer and save any PIN or activation details provided.
• 02
  Install Middleware: Install the vendor-supplied driver or middleware on the computer where the token will be used.
• 03
  Register Token: Plug token into device, open OS certificate manager, and confirm the ProxKey certificate is visible.
• 04
  Use in signNow: Initiate signing in signNow, choose certificate authentication, and select the ProxKey credential to sign.

How signing works stepwise

This flow outlines the main actions from preparing a ProxKey to completing an eSignature inside signNow and recording evidence.

• Prepare Document: Upload PDF or form to signNow and add signature fields where required.
• Choose Auth Method: Select certificate-based authentication in the signer settings for stronger identity verification.
• Sign With Token: Plug in ProxKey, enter PIN when prompted, and apply the certificate signature.
• Store Evidence: signNow creates an audit trail and stores a signed copy in secure cloud storage.

Device and platform requirements

Ensure the local device supports ProxKey middleware and that signNow has access to the certificate store to complete certificate-based signing.

• Supported OS: Windows 10+ or macOS
• Browser Support: Chrome, Edge, Safari
• Hardware Needs: USB token or smartcard

For mobile use, check vendor mobile middleware compatibility, since hardware token use on phones may require an intermediary app or Bluetooth support.

Security and compliance features

Encryption: TLS 1.2/1.3 and AES-256

Audit Logging: Comprehensive signed audit trail

Certifications: SOC 2 Type II and ISO 27001

Regulatory Support: ESIGN, UETA compliance

Health Data: HIPAA compliant with BAA

Accessibility: WCAG 2.0 Level AA

Legal and business rationale

Certificate-backed signatures strengthen non-repudiation and are useful in regulated transactions that require higher signer identity assurance. They reduce fraud risks, create durable evidentiary trails for audits, and speed processes that otherwise need physical presence or notarization.

Who typically uses ProxKey signing

Organizations handling sensitive or regulated documents often adopt certificate-based signing to meet identity and audit requirements.

• Legal teams finalizing executed contracts remotely with high identity assurance.
• Healthcare providers collecting HIPAA-sensitive consents and medical forms securely.
• Financial institutions approving regulated client transactions and compliance paperwork.

Enterprises, government agencies, and certain professional services prefer ProxKey-style signatures when a cryptographic certificate adds legal weight and traceability to the eSignature.

Key user roles

IT Administrator

Manages ProxKey middleware deployment, enforces certificate provisioning policies, configures signNow account security settings, and establishes SSO or directory integrations. Responsible for device compatibility testing, token lifecycle management, and ensuring audit log retention meets organizational policy.

Compliance Officer

Defines signature policies, documents retention schedules, validates that ProxKey signing meets ESIGN and UETA requirements, coordinates BAAs for HIPAA workflows, and reviews audit trails for regulatory audits and internal controls.

Core signNow capabilities for ProxKey use

signNow supports certificate-based signer authentication and offers features that complement ProxKey signing workflows for teams across industries.

Templates

Create reusable, preconfigured documents with signature and data fields so teams can quickly send forms that require ProxKey-certified signers without manual field placement each time.

Audit Trail

Every signed document contains a detailed, tamper-evident audit trail recording signer authentication method, certificate metadata, timestamps, and IP addresses for compliance and dispute resolution.

Bulk Send

Send the same document to many recipients and collect signatures at scale; useful when many users must sign identical compliance forms using certificate authentication.

Mobile Apps

signNow mobile apps let users view and manage signed documents, though certificate token use on mobile may require vendor-specific middleware or companion apps.

Advanced features and integrations

For teams implementing ProxKey signing, signNow provides integrations and advanced controls to embed certificate checks into broader business systems.

API Access

Full REST API for automating sends, embedding signing flows, and validating signer certificate metadata programmatically within enterprise applications.

SSO Support

SAML-based single sign-on options help control user access for accounts and complement certificate-based signer authentication.

CRM Integrations

Prebuilt connectors for Salesforce and Microsoft Dynamics 365 enable documents to flow into existing sales and contract processes with certificate-backed signatures.

Document Storage

Connectors for Google Drive, Box, and AWS allow secure storage of signed files and retention according to corporate policy.

Conditional Fields

Add logic-driven fields and formulas to ensure only the correct fields appear to certificate-authenticated signers when required.

Kiosk Mode

On-premise signing stations can collect signatures using hardware tokens for in-person certificate signing workflows.

Typical workflow configuration

This table lists common signNow settings used when adding ProxKey certificate-based signing to a document workflow.

Setting Name	Configuration
Signer Authentication	Certificate
Reminder Frequency	48 hours
Signature Order	Sequential
Audit Retention	7 years
Storage Location	Encrypted cloud

Pricing and feature snapshot (data current as of 2026)

This concise comparison shows starting prices and a few key feature contrasts across signNow and common competitors to help evaluate certificate-based signing support.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo annual	$8/user/mo annual	$13/user/mo annual	$19/user/mo annual	$15/user/mo annual
Free Trial	7-day free trial	Free trial avail.	Free trial avail.	Free trial avail.	Free trial avail.
Bulk Send	Yes, Business Premium includes	Available on select plans	Available on select plans	Available	Available
Audit Trail	Full audit trail included	Full audit trail included	Full audit trail included	Full audit trail included	Full audit trail included
HIPAA Compliant	Yes, BAA required	Yes, BAA required	Yes, BAA required	Contact sales	Contact sales
Envelope Cap	No envelope cap	100 envelopes/year	Not specified	Not specified	Not specified

Feature availability at a glance

Quick binary and concise answers for common capabilities relevant to ProxKey and certificate-based signing across signNow and two leading alternatives.

Feature	signNow	DocuSign	Adobe Sign
Certificate Signing Support
Bulk Send Capability	yes (premium)
SSO / SAML	yes (site license)
Full REST API

Real-world implementation examples

Two customer stories illustrate how certificate-backed signing and signNow integrate into existing operations.

Optica Ventures

The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers.

• Implemented signNow templates and certificate authentication to streamline investor agreements.
• Reduced manual follow-ups and increased remotely completed deals.

Resulting in faster closings and better customer experience.

Xerox

airSlate SignNow provides us with the flexibility needed to get the right signatures on the right documents, in the right formats.

• Integrated signNow with NetSuite to populate contract fields automatically.
• Achieved consistent signer identity verification using certificate metadata.

Leading to fewer exceptions and smoother enterprise billing workflows.

Best practices for ProxKey and signNow

Follow these recommended controls when deploying ProxKey certificate signing with signNow to maintain security and operational reliability.

Standardize certificate issuance procedures

Use a centralized certificate authority and documented issuance steps so tokens are provisioned consistently and revoked promptly when lost or replaced.

Test token workflows before production

Validate middleware, browser interactions, and signNow certificate selection on representative machines to avoid signer friction during live transactions.

Retain and secure audit logs

Configure signNow audit retention in line with policy and ensure logs are exported to secure storage for regulatory or legal review.

Train signers on token use

Provide clear instructions, PIN management guidance, and troubleshooting steps so signers can use ProxKey tokens without delays or errors.

Manage completed signatures and evidence

Steps to verify and archive signed documents and certificate evidence after signing finishes in signNow.

01

Locate Signed File:

Open completed documents in signNow.

02

Download Audit Trail:

Export the certificate metadata and event log.

03

Validate Certificate:

Check issuer and validity dates.

04

Archive Document:

Store signed PDF in encrypted storage.

05

Set Retention:

Apply legal retention policy.

06

Enable Backups:

Schedule regular encrypted backups.

FAQs and troubleshooting

Common questions and solutions encountered when using ProxKey tokens with signNow, aimed at administrators and end users.

• My ProxKey token is not detected by the browser
  Ensure the vendor middleware and drivers are installed and running; restart the browser after installation. Confirm the certificate appears in the OS certificate store. If using macOS, ensure the token provider app has the necessary system permissions and that the browser supports PKCS#11 or the vendor’s extension.
• signNow does not offer direct token driver support
  Use standard OS certificate stores and middleware so signNow can access the certificate; configure your token middleware to expose certificates to the browser, or use an API-based signing workflow to validate certificate metadata server-side.
• Certificate PIN prompts repeatedly appear
  Check token PIN policies and middleware timeout settings. If required, adjust token middleware to reduce excessive PIN prompts and confirm the token firmware is up to date to avoid repeated prompts during a single signing session.
• Signature validation shows warning after signing
  Validate the certificate chain and CRL/OCSP responses; ensure the signing certificate was not revoked and that time-stamping was applied. Re-sign with updated token if the certificate expired or was revoked.
• How to collect signatures from remote users
  Send the document via signNow with certificate-based authentication selected; include clear instructions for recipients on installing middleware and using the ProxKey token so they can complete signing remotely without support calls.
• What if a signer loses their ProxKey token
  Revoke the associated certificate promptly through the issuing CA, update signNow signer records, and require re-authentication with a new credential before approving further documents.

Processing times and retention guidance

Typical timelines for setup, signature completion, and recommended retention periods for certificate-backed eSignatures.

Token Provisioning Time:

2–7 business days

Middleware Installation:

30–60 minutes

Signer Completion Window:

1–7 days commonly

Audit Trail Retention:

Retain 7 years minimum

Certificate Renewal Window:

Renew 30 days before expiry