Signer Identity
Full legal name, date of birth, and contact information captured exactly as shown on the supporting ID for unambiguous identification.
Provides a concise, auditable record of identity verification that supports contract enforceability and regulatory compliance.
Organizations, individual signers, and agents use an Acknowledgement of Identity ID whenever identity confirmation must be recorded.
The form is adaptable to many workflows — from consumer onboarding to internal approvals — and should match the receiving party’s verification policies.
| Field | Configuration |
|---|---|
| Authentication Method | Email link + SMS code or KBA when required |
| Signature Type | Typed, drawn, or uploaded image depending on risk |
| Audit Trail | Enable full IP, timestamp, and action logs |
| Storage Format | Store signed copy as PDF/A for long-term preservation |
Choose platforms and integrations that support the authentication and retention your workflow requires.
Full legal name, date of birth, and contact information captured exactly as shown on the supporting ID for unambiguous identification.
Type of ID, issuing jurisdiction, ID number, and expiration date recorded to tie the acknowledgement to a specific credential.
Record whether verification was in-person, via remote online notarization, credential analysis, knowledge-based authentication, or documentary review.
A clear declarative line where the signer affirms the identity confirmation and acknowledges the purpose of the verification.
Signing date, location, and witness or notary information included where required by law or policy.
System-generated IP, timestamp, and event log that supports attribution and non-repudiation for later review.
Provide acknowledgement within the timeframe set by the requesting party
Recipients often require return within 3–7 business days
RON recordings retained per state rules, commonly 5–10 years
Verification and sign-back often complete same day for digital workflows
Store signed copy accessible for audit when requested
Receiving party issues acknowledgement request with required fields and deadline.
Verifier confirms ID via chosen method and records the result on the form.
Signer signs the acknowledgement and returns it to the issuing party.
Store the signed acknowledgement in the designated records repository.
| 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 | Varies by vendor | Varies by vendor | Varies by vendor | Varies by vendor |
| Bulk Send | Yes (Business Premium) | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No envelope cap | 100 envelopes/user/year | Varies by plan | Varies by plan | Varies by plan |
A clinic collects a signed identity acknowledgement during telehealth registration
A title company requests identity acknowledgement before releasing closing documents
An individual who is the subject of the identity verification and who signs the acknowledgement to confirm their own identity. The text should note the signer’s capacity if signing for an organization.
An authorized verifier, witness, or notary who confirms the presented credentials. Their entry should include name, commission information (if applicable), and signature or stamp per state rules.