Affiant details
Full legal name, any known aliases, date of birth, and current contact details so reviewers can match records and reach the affiant if follow-up is necessary.
A properly prepared affidavit prevents delays, avoids disputed transfers, and creates a traceable, sworn record that third parties and government agencies can accept. It documents the affiant’s sworn facts, supports legal title or benefit claims, and reduces the risk of rejection or potential liability from misidentification.
The affidavit is used by individuals and organizations needing formal, sworn identity verification when primary documents are missing, inconsistent, or require supplemental proof.
Use the affidavit exactly as required by the receiving party: follow field formats, attach supporting ID copies, and notarize or sign per jurisdictional rules to avoid rejection.
The person asserting identity facts. The affiant signs under oath, provides government-issued ID information, explains discrepancies, and certifies truthfulness. The affidavit typically includes full legal name, aliases, date of birth, and signature under penalty of perjury.
An agent, title officer, or bank representative may prepare or accept the affidavit on behalf of an institution. They verify supporting documentation, confirm notarization requirements, and record receipt in the organization’s file for compliance and audit purposes.
Full legal name, any known aliases, date of birth, and current contact details so reviewers can match records and reach the affiant if follow-up is necessary.
A clear, numbered narrative describing why identity is disputed or missing, the relationship to the relevant record, and any relevant dates or events that explain the inconsistency.
List of IDs provided or unavailable (driver’s license, passport, SSN last four), including issuing authority, number, and reason for omission if the document is not attached.
Copies of available documents such as birth certificate, expired ID, utility bills, or affidavits from witnesses that corroborate identity claims.
Official notarial language, signature, seal, and date. If remote notarization is used, include the notary’s RON statement and session record reference where allowed.
Affiant signature, date, and jurat or acknowledgement that includes the notary’s statement that the affiant swore or affirmed under penalty of perjury.
| Field | Configuration |
|---|---|
| Required fields | Make name, DOB, statement, and signature required. |
| Attachments | Require PDF uploads and label them as exhibits. |
| Signer authentication | Use email + SMS code or stronger ID verification where allowed. |
| Routing | Send completed affidavit to title officer, bank, or designated recipient automatically. |
Choose a platform that supports the authentication and notarization requirements of the receiving party and the relevant state.
Ensure your platform can produce an audit trail (timestamps, IPs), preserve original file fidelity, and capture any RON session metadata if remote notarization is used.
| 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 | Varies | Varies | Varies |
| Bulk Send | Yes | Yes | Yes | Yes | No |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
A customer provides an affidavit explaining a lost driver’s license and supplies alternate ID and a police report
A title company requests an affidavit when a deed lists a slightly different name spelling