Establishing secure connection…Loading editor…Preparing document…

Identity Verification Document

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

IDENTITY VERIFICATION AGREEMENT

This Identity Verification Agreement (the Agreement) is entered into as of between Client Name: and Verification Provider: (each a Party and together the Parties).

WHEREAS

WHEREAS, Client requires reliable identity verification services to confirm the identity of individuals for business, regulatory, or contractual purposes; and

WHEREAS, Provider represents that it is duly qualified and has the systems, personnel, and procedures necessary to perform identity verification in compliance with applicable laws and industry standards; and

WHEREAS, the Parties desire to set forth the terms under which Provider will perform identity verification services and Client will compensate Provider.

1. SCOPE OF WORK

Provider will perform identity verification services for the Subject identified below. Services may include document examination, database checks, biometric comparison, remote interview, and any other verification steps described in the Scope of Work field.

Full legal name: Date of birth:

2. VERIFICATION METHODS

Provider shall use one or more of the following methods as applicable (check those to be performed):

Document review (visual/forensic inspection)

Database and watchlist checks

Biometric comparison (facial recognition / fingerprint)

3. PAYMENT TERMS

Client shall pay Provider the fees set forth below in consideration for the services.

Provider will invoice Client in accordance with the Payment Schedule. Unless otherwise agreed in writing, fees are exclusive of taxes and expenses; Client is responsible for taxes and for promptly reimbursing Provider for reasonable out-of-pocket expenses incurred in performance.

4. TERM AND TERMINATION

This Agreement commences on Start Date: and, unless earlier terminated, continues until End Date: .

Either Party may terminate this Agreement for material breach by the other Party that remains uncured for thirty (30) days after written notice of the breach. Termination shall not relieve Client of the obligation to pay for services performed and expenses incurred prior to termination.

5. CONFIDENTIALITY

Each Party (the Receiving Party) shall keep Confidential Information of the other Party (the Disclosing Party) strictly confidential and shall not disclose such information except as required to perform the services and to its employees, contractors, or agents who have a need to know and who are bound by confidentiality obligations at least as protective as those set forth herein.

"Confidential Information" includes all non-public personal data, identity documents, verification reports, business information, and any other information designated confidential or which, under the circumstances, should reasonably be understood to be confidential. Confidential Information does not include information that (a) is or becomes publicly known through no breach of this Agreement, (b) is received from a third party without similar restriction, or (c) is independently developed without use of Disclosing Party's Confidential Information.

Upon termination or at Disclosing Party's request, Receiving Party shall promptly return or destroy Confidential Information and certify such destruction if requested.

6. DATA PROTECTION AND CONSENT

Client warrants that it has obtained all necessary consents from the Subject to permit Provider to process personal data and to conduct the verification methods selected. Provider shall process personal data only as necessary to perform the services and in accordance with applicable data protection laws and the terms of this Agreement.

7. WARRANTIES; LIMITATION OF LIABILITY

Provider warrants that services will be performed with reasonable skill and care. EXCEPT AS EXPRESSLY STATED IN THIS AGREEMENT, PROVIDER DISCLAIMS ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

IN NO EVENT SHALL EITHER PARTY BE LIABLE FOR INDIRECT, CONSEQUENTIAL, OR PUNITIVE DAMAGES. PROVIDER'S AGGREGATE LIABILITY ARISING OUT OF OR RELATED TO THIS AGREEMENT SHALL NOT EXCEED THE FEES PAID BY CLIENT TO PROVIDER WITHIN THE TWELVE (12) MONTHS PRECEDING THE EVENT GIVING RISE TO LIABILITY.

8. GOVERNING LAW

This Agreement shall be governed by and construed in accordance with the laws of without regard to conflict of laws principles.

9. ENTIRE AGREEMENT

This Agreement, including any exhibits or attachments executed by the Parties, constitutes the entire agreement between the Parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, understandings, negotiations and discussions, whether oral or written.

10. MISCELLANEOUS

No amendment or waiver of any provision of this Agreement shall be effective unless made in writing and signed by authorized representatives of both Parties. If any provision of this Agreement is held invalid or unenforceable, the remaining provisions shall remain in full force and effect.

Client:

By:

Date:

Verification Provider:

By:

Date:

Enter text✕

What an Identity Verification Document Is and When it’s Used

An Identity Verification Document is a formal record used to confirm an individual's identity for legal, financial, or administrative purposes. It combines self-declared data with evidence from government-issued credentials (driver's license, passport, state ID), and may include a photo, date of birth, address, and a signature or biometric. Organizations use these records for account opening, employment onboarding (I-9), benefits enrollment, vendor onboarding, and remote notarization. Electronic completion and eSigning are generally permissible under ESIGN and UETA when the process documents intent, attribution, consent, and retention.

Why a Reliable Identity Verification Document Matters

Use an Identity Verification Document to reduce fraud, meet regulatory obligations, and create an auditable record of identity. It supports KYC, employment I-9 compliance, HIPAA-related patient identity checks, and other legal requirements when properly documented.

Why a Reliable Identity Verification Document Matters

Who Typically Prepares and Signs These Documents

Common organizations and roles that complete Identity Verification Documents include banks, insurers, employers, healthcare providers, and government agencies handling identity-dependent transactions.

  • Banks and credit unions for account opening, KYC, and regulatory due diligence.
  • Human resources teams for new-hire I-9s, background checks, and onboarding workflows.
  • Healthcare clinics and payers to verify patients and link records under HIPAA workflows.

These users rely on accurate identity records to reduce risk, meet legal requirements, and enable secure digital transactions with auditable trails.

Step-by-step: Completing an Identity Verification Document

Follow these sequential steps to complete an Identity Verification Document accurately, whether you use an online eSign workflow or a paper form.

  • 01
    Prepare documents: Collect government ID, proof of address, and any supporting records.
  • 02
    Enter information: Fill legal name, DOB, address exactly as on ID.
  • 03
    Verify identity: Use photo match, ID credential analysis, or knowledge-based checks.
  • 04
    Sign and retain: Sign, date, and store both signed copy and verification audit trail.

How eSubmission and Routing Typically Work

Typical e-submission flow for an Identity Verification Document combines upload, field placement, signer authentication, and audit logging.

  • Upload document: Upload PDF or DOCX and prepare form fields for signer input.
  • Assign signers: Add signer emails and set signing order if role-based approval is required.
  • Authenticate signer: Use email OTP, SMS code, or advanced methods like KBA or ID credential analysis.
  • Complete audit: Capture timestamp, IP, and certificate of completion for legal defensibility.

Key workflow settings to configure before sending

Configure these workflow settings when preparing an electronic Identity Verification Document for distribution and signing.

Field Configuration
Authentication Method Email OTP, SMS code, KBA, or ID credential analysis
Required Fields Full name, DOB, ID type/number, address, signature
Conditional Fields Show extra ID uploads if initial checks fail
Retention Policy Store signed record per regulatory retention rules

Platform and integration considerations

Ensure platform compatibility and integration options when deploying electronic Identity Verification Documents.

  • File formats: PDF, DOCX, and HTML supported
  • Integrations: Salesforce, NetSuite, Google Workspace integrations available
  • Authentication: Support for SMS OTP and KBA

Core features of a compliant Identity Verification Document

Core components of a compliant Identity Verification Document ensure identity capture, evidence of verification, signer intent, and secure recordkeeping for audit and regulatory review.

Identity Capture

Collect full legal name, DOB, address, and government ID images. High-quality scans or photos improve credential-analysis accuracy and reduce manual review time.

ID Validation

Use automated credential analysis to check document authenticity, expiration, and issuing jurisdiction, and flag inconsistent information for manual review.

Photo Match

Compare a selfie or live photo against the ID image using automated or manual review to corroborate signer presence at signing time.

Audit Trail

Record timestamps, IP addresses, authentication events, and document history. An immutable trail supports enforceability under ESIGN and UETA.

Biometric Options

Optional biometric checks and liveness tests increase assurance but may require explicit consent and privacy notices under state law.

Notarization Support

Include in-person or remote online notarization (RON) workflows where required; retain audio-video recordings and notary journal entries for compliance.

Security and compliance controls to observe

Encryption in Transit: TLS 1.2 and TLS 1.3 required
Encryption at Rest: AES-256 encryption for stored documents
Certifications: SOC 2 Type II and ISO 27001
HIPAA: BAA required for protected health information
21 CFR Part 11: Supports FDA electronic records and signatures
Audit Trails: Tamper-evident logs with timestamps and IP

Penalties and risks of errors or missing information

1099 Filing Penalties: $60–$330 per form; $660+ intentional disregard
W-2 Late Filing: Penalties mirror IRC §6721 amounts
I-9 Violations: $281–$2,789 per violation (8 CFR §274a.2)
Incorrect Identity: Transaction risk, account freezes, or compliance audit
Invalid eSignature: Missing consent or poor audit trail risks unenforceability
Privacy Breach: HIPAA fines or state penalties for PHI exposure

Common preparation mistakes to avoid

  • Relying on low-assurance authentication (email-only) can allow account takeover and fails higher-risk KYC requirements.
  • Entering names or DOB with typographical errors frequently triggers rejections or backup withholding due to TIN mismatches.
  • Using expired or partially obscured ID images causes automated verification to fail and increases manual review time.
  • Failing to obtain consumer consent for electronic records in consumer-facing transactions can invalidate e-signature under ESIGN.

Pricing and feature comparison for common eSignature providers

Compare baseline pricing and select feature differences across providers; signNow is listed first for direct comparison without implying a recommendation.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Business Premium) Yes Yes Yes Limited
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA) Yes (BAA) Yes (BAA) No No
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

FAQs: Common questions about Identity Verification Documents

Answers to frequent questions about completing, signing, and storing Identity Verification Documents in electronic or paper workflows.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users