Identity Verification Authentication Form
What the Identity Verification Authentication Form Is
Why a Formal Identity Verification Record Matters
Use the Identity Verification Authentication Form to reduce ambiguity about who completed authentication steps, to document consent for electronic processing, and to create a reproducible audit trail that supports compliance with ESIGN and UETA. It centralizes identity evidence for regulatory review.
Who Typically Completes or Reviews This Form
Typical users include identity clerks, compliance officers, HR staff, lenders, and notaries who need a verifiable identity record.
- Financial institutions: verify customer identity for account opening and Know-Your-Customer (KYC) obligations.
- Healthcare providers: confirm patient identity before releasing records or completing HIPAA-authorized electronic forms.
- Real estate and legal services: authenticate signers for deeds, leases, powers of attorney, and contracts.
Organizations of all sizes use the form to reduce fraud risk and to document compliance-ready identity actions.
Key Roles That Use the Form
Compliance Officer
A Compliance Officer oversees identity verification policies, selects authentication methods, and reviews audit trails. They ensure the form captures legally necessary elements for ESIGN/UETA compliance, coordinate retention schedules, and respond to regulator requests. Accurate entries reduce liability and support timely audits.
Notary Public
A Notary Public documents identity verification and, where allowed, performs remote online notarization. They retain the audio-video record and journal entries as required by state law. Their acknowledgment or jurat adds formal authentication for deeds, powers of attorney, and other notarized documents.
Step-by-Step: Completing the Identity Verification Authentication Form
-
01Prepare: Collect IDs, consent evidence, and contact details before starting.
-
02Enter Data: Complete name, DOB, address, and ID numbers in MM/DD/YYYY where applicable.
-
03Authenticate: Select method (SMS code, KBA, biometric) and record result.
-
04Finalize: Sign, timestamp, and retain a copy for records and audit.
Typical Workflow From Upload to Audit Trail
-
Upload: Start by uploading the blank form and any attachments.
-
Place Fields: Add name, ID, signature, date, and consent fields in the document.
-
Authenticate: Choose authentication level and send signer verification challenge.
-
Archive: Store signed PDF and audit trail under retention policy.
Configuring an Online Identity Verification Workflow
| Workflow Setting or Field Name | Configuration options and expected values for each workflow field |
|---|---|
| Signer Authentication Method Selection for Identity Verification | Set default method and allowed alternatives; choose KBA, SMS, email, or biometric |
| Field Validation and Formatting Rules | Define required formats (MM/DD/YYYY), character limits, and auto-detection for IDs |
| Routing and Escalation Conditions Based on Risk | Configure conditional routing to compliance team for failed verifications or high-risk matches |
| Audit Trail and Retention Controls | Enable timestamping, session IDs, and long-term export to secure storage |
Platform and Integration Requirements
Platform and integration requirements help determine how the Identity Verification Authentication Form is shared, authenticated, and stored within your systems.
- Formats: PDF, DOCX, HTML supported
- Integrations: Salesforce, NetSuite, Google Workspace, Microsoft 365
- API: REST API and webhooks available
Common Preparation Challenges to Anticipate
- Incomplete or inconsistent name fields create mismatches with government IDs and may trigger manual review or rework, delaying processing and increasing operational cost.
- Using weak signer authentication (email-only) increases fraud risk for high-value transactions; stronger methods such as MFA or knowledge-based verification are recommended by policy.
- Relying on scanned signature images without a supporting audit trail can make it difficult to prove attribution under ESIGN or during regulatory audits.
- Failing to retain identity proofing records or RON session recordings may violate state notary laws and hinder legal defense in disputes.
Penalties and Legal Risks of Incorrect or Missing Information
Timing Considerations and Regulatory Deadlines
Tax Reporting and Information Requests:
Provide forms upon payer request; retain supporting records per IRS rules
I-9 Retention and Storage Requirements:
Keep for three years after hire or one year after termination, whichever is later
HIPAA Records Retention for Identity Documentation:
Retain patient identity proofing for six years per 45 CFR §164.530(j)
RON Recording and Storage Requirement:
Retain audio-video recordings and journals per state notary law, typically five to ten years
General Business Document Retention Policy:
Keep signed forms for term plus minimum three years; longer for tax and real estate
eSignature Pricing and Feature Snapshot
| 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 | Yes, 7-day free trial, no credit card required | Varies by vendor and plan | Varies by vendor and plan | Varies by vendor and plan | Varies by vendor and plan |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No envelope cap on paid plans | Limit 100 envelopes per user per year | Limits vary by plan and account | Plan-dependent envelope limits; contact sales | Plan-dependent limits and API quotas apply |
Frequently Asked Questions and Troubleshooting
-
What information is required?
Provide full legal name, date of birth (MM/DD/YYYY), current address, government ID type and number, issuing authority and expiration, and contact details. Also record the authentication method used and capture the signer's consent to electronic processing in an auditable field.
-
Can this be notarized remotely?
Remote online notarization is possible where state law permits RON. The notary must use approved identity proofing, audio-video recording, and retain required journals. Verify your state's RON rules and retention obligations before relying on remote notarization.
-
What authentication methods are acceptable?
Acceptable methods include email or SMS one-time codes, knowledge-based authentication, biometrics, and cryptographic digital signatures. Higher-risk transactions may require multi-factor authentication or RON with credential analysis. Choose methods appropriate to transaction risk and regulatory requirements.
-
How long must records be kept?
Retention depends on document type and regulation: IRS records three to six years, HIPAA six years, and employment I-9 forms three years after hire or one year after termination, whichever is later. State rules may extend these periods.
-
What happens if data is incorrect?
Incorrect or mismatched identity data can trigger manual verification, transaction delays, additional requests for ID, or regulatory reporting. For tax or legal filings, inaccuracies may lead to penalties, rejected filings, or the need to re-execute documents under corrected information.
-
Is electronic consent required?
Yes for consumer-facing transactions: ESIGN requires a clear disclosure of the right to receive records on paper, a demonstration the consumer can access the electronic format, and a record of affirmative consent. Document the disclosure and consent in the form.