Identification ID Back
What the Identification ID Back Is and why it matters
Why capturing the Identification ID Back improves verification accuracy
Including the ID back reduces fraud risk by providing machine-readable data, expiration and issue information, and provenance markers not always visible on the front. It also supports automated data extraction and faster manual review when algorithms need barcode or magnetic-strip data.
Who typically collects or reviews the Identification ID Back
Organizations that rely on accurate identity proofing collect the ID back as part of a multi-data verification process.
- Financial services and lenders performing KYC and AML checks
- Healthcare providers and insurers verifying patient identity for records
- Real estate and leasing organizations confirming tenant identity
The individuals photographed or scanned must ensure the back image is legible and unaltered to avoid processing delays.
Step-by-step: capturing and submitting the ID back
-
01Prepare card: Remove obstructions; place on a flat surface
-
02Frame image: Include all four corners and barcode/MRZ
-
03Check legibility: Confirm text and barcode are readable
-
04Upload: Submit via secure portal or eSubmission flow
Where the Identification ID Back fits in verification workflows
-
Capture: User takes photo or uploads scan of the card back
-
Automated parse: System extracts MRZ/barcode and textual fields
-
Manual review: Agent checks anomalies and security features
-
Finalize record: Data stored with audit trail and matched to profile
Technical considerations for submitting the ID back image
Ensure the chosen submission platform accepts required image formats and secures the transmission.
- Supported Formats: JPEG, PNG, PDF
- Minimum Resolution: 300 DPI recommended
- Integrations: API or direct upload to document systems
Timing considerations and acceptable document currency
Expiration Check:
Expiry must be future-dated for most verifications
Temporary IDs:
May be accepted with supplemental documents
Retention Start:
Retention begins at submission date
Update Frequency:
Re-verify every 1–3 years per policy
Time-sensitive uses:
Benefits or transfers may require same-day verification
Common mistakes when capturing the ID back
- Blurry images prevent barcode or MRZ reading and cause rejection
- Glare or reflections obscure security text and holograms
- Partial crops remove corner-to-corner data crucial for validation
- Uploading front instead of back loses machine-readable elements
Consequences of incorrect or incomplete ID back submissions
Practical tips for accurate Identification ID Back capture
Real-world examples of Identification ID Back use
Optica Ventures (Verification)
Optica integrated back-of-ID capture for investor KYC to improve match rates
- System parsed MRZ and matched database records
- Results shortened verification cycles and reduced manual review overhead, improving onboarding speed while preserving audit logs and compliance controls.
Fertility Centers of Illinois (Healthcare)
The center required back-of-ID images to confirm patient insurance and residency
- Staff validated endorsements and expiration dates
- This reduced claim denials and ensured proper HIPAA handling through secure storage and restricted access controls.
How Identification ID Back differs from similar identity artifacts
| Artifact | Captured Data | Typical Use |
|---|---|---|
| ID Back | barcode/mrz, endorsements | proof of authenticity |
| ID Front | photo, name, dob | visual id match |
| Selfie with ID | live face match | liveness and anti-spoofing |
| Utility Bill | address proof only | residency verification |
eSignature platform pricing and capability snapshot relevant to ID back workflows
| 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) | Varies by plan | Varies by plan | Varies by plan | Varies by plan |
| Audit Trail | Yes | Yes | Yes | Yes | Yes |
| HIPAA Compliant | Yes | Yes | Yes | No | No |
| Envelope Cap | No cap | 100 envelopes/user/yr | Varies by plan | Varies by plan | Varies by plan |
How to update or replace an existing Identification ID Back image
Identify Issue:
Request Resubmission:
Validate New Image:
Replace Record:
Log Change:
Notify Parties:
FAQs and troubleshooting for Identification ID Back submissions
-
My image was rejected; why?
Rejection typically occurs for blur, glare, cropped edges, or unreadable barcodes/MRZ. Retake the photo on a flat surface with even lighting and ensure the entire back is visible.
-
Can I redact other information?
Do not redact machine-readable zones or required endorsements. You may obscure unrelated personal data if your process permits, but preserve elements needed for verification and audit.
-
Are scanned PDFs acceptable?
Yes; high-resolution PDF or image formats are acceptable. Ensure the scan captures contrast in the barcode/MRZ zone and preserves color for security features.
-
Is RON or notarization ever needed?
Not for basic ID capture. Certain affidavits or legal transactions may require notarization or RON; consult transaction-specific guidance or state law.
-
How is the image stored securely?
Store images in encrypted repositories with access controls. Use TLS 1.2/1.3 for transit and AES-256 at rest to meet common security standards.
-
What if the ID is expired?
Expired IDs are usually unacceptable for identity proofing. Request a current, unexpired credential or follow your exception policy with documented justification.