IDGod Michigan scan details update
No comments yet. Be the first to comment!
Please login to comment on this thread.
Thread Info
Thread Author
CH
cheechnsong
Member since Aug 2025
7
Posts
5
Threads
22
Karma
Secure Payment Methods
Learn about the safest payment methods for online transactions. Bitcoin, gift cards, and more.
Learn More
VVL Vendors
Related Discussions
California 2025 template - what to look for
0 replies
Best states for novelty IDs in 2025 - Complete ranking
0 replies
California vs Texas ID - Complete Feature Comparison 2025
0 replies
Best Vendor for California IDs in 2025?
0 replies
Florida ID - Budget ID Solutions Review
0 replies
Michigan vs Wisconsin - Which is Better for Midwest Users?
0 replies
Forum Moderators
🛡️
AdminFIDV
Administrator
⭐
Sterlingwalkeri
Moderator
⭐
Butter
Moderator
⭐
supermod
Moderator
Community Stats
Total Members:
726
Online Now:
0
Total Threads:
1,930
Total Posts:
6,963
Community Guidelines
New to our community? Read our guidelines for safe and respectful interactions.
Learn More
Posting a barcode scan update for IDGod Michigan cards because most threads I found reference 2024 test results and things appear to have changed. I received my most recent IDGod MI order three weeks ago and ran systematic scan testing as part of my unboxing process.
Test setup
Three apps: SCUID, ID Analyzer, and a state-linked DMV app with a built-in scan function. Each app tested from the same card under the same lighting conditions — indirect natural light at a desk. Three scan attempts per app, card held at the same angle for each attempt.
SCUID results
All three attempts decoded on first try with no repositioning needed. AAMVA field output was complete — all required fields present and populated accurately matching the card face. Magnetic stripe read on first swipe on both stripe readers I tested. No issues here.
ID Analyzer results
Two of three attempts decoded first-try; one required a slight card angle adjustment before reading. The app flagged a formatting inconsistency in the address field on all three successful reads — same field, same flag each time. This is consistent with what older forum posts describe for IDGod MI encoding, so this specific issue has not been resolved in current production.
DMV app results
Decoded successfully on all three attempts. No flags or errors of any kind.
How this compares to 2024 reports
Earlier threads described consistent first-attempt failures on SCUID specifically. My recent card does not reproduce this — SCUID decodes reliably. Either IDGod improved their MI encoding for SCUID compatibility, or my batch happened to perform better. The ID Analyzer address field flag persists unchanged.
If you're testing with ID Analyzer, expect the address field formatting flag — it appears to be a structural encoding decision on IDGod's end that hasn't been corrected. It does not trigger on SCUID or the DMV app, which suggests it's a parsing difference between apps rather than a fundamental encoding error. For overall scan performance, current IDGod MI production is meaningfully better than the 2024-era reports suggest.