<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>LaurelID mobile ID knowledge center</title>
    <link>https://laurelsecure.com/knowledge</link>
    <atom:link href="https://laurelsecure.com/rss.xml" rel="self" type="application/rss+xml" />
    <description>Primary-sourced explainers on mobile driver's licences, ISO/IEC 18013-5, selective disclosure, wallet support, and privacy-preserving age verification.</description>
    <language>en-us</language>
    <lastBuildDate>Mon, 10 Aug 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>What AAMVA&apos;s VICAL and Digital Trust Service Do</title>
      <link>https://laurelsecure.com/knowledge/aamva-vical-and-the-digital-trust-service</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/aamva-vical-and-the-digital-trust-service</guid>
      <description>AAMVA&apos;s mDL Digital Trust Service publishes a signed list of legitimate issuing-authority keys — a VICAL — that relying parties load into their readers before accepting credentials. Without it, a reader can check consistency but not legitimacy.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>standards-and-trust</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-08-10</dc:date>
    </item>
    <item>
      <title>Apple Wallet Mobile IDs: What Businesses Need to Know</title>
      <link>https://laurelsecure.com/knowledge/apple-wallet-mobile-ids-for-businesses</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/apple-wallet-mobile-ids-for-businesses</guid>
      <description>Apple Wallet carries state-issued driver&apos;s licences and IDs in participating US jurisdictions, presented over the ISO/IEC 18013-5 flow. Availability depends on the issuing state, and a wallet carrying an ID says nothing about whether a given verifier accepts it.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>mobile-id-basics</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>Google Wallet Mobile IDs: What Businesses Need to Know</title>
      <link>https://laurelsecure.com/knowledge/google-wallet-mobile-ids-for-businesses</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/google-wallet-mobile-ids-for-businesses</guid>
      <description>Google Wallet carries state-issued IDs built on ISO/IEC 18013-5 and publishes its supported issuing authorities along with their certificate locations. That list describes Google&apos;s support, not any particular verifier&apos;s.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>mobile-id-basics</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>How Mobile ID Verification Works, Step by Step</title>
      <link>https://laurelsecure.com/knowledge/how-mobile-id-verification-works</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/how-mobile-id-verification-works</guid>
      <description>An in-person mobile ID check is a short cryptographic conversation: the phone and reader establish a session, the reader asks for named elements, the phone responds, and the reader validates the issuer&apos;s signature before reading anything.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>mobile-id-basics</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>How Offline Mobile ID Verification Works</title>
      <link>https://laurelsecure.com/knowledge/how-offline-mobile-id-verification-works</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/how-offline-mobile-id-verification-works</guid>
      <description>The ISO/IEC 18013-5 device-retrieval flow is a direct exchange between phone and reader, so a check needs no network. What connectivity affects is trust-material freshness and the delivery of operational records.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>operations</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>What ISO/IEC 18013-5 Means for Businesses</title>
      <link>https://laurelsecure.com/knowledge/iso-iec-18013-5-for-businesses</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/iso-iec-18013-5-for-businesses</guid>
      <description>ISO/IEC 18013-5 is the international standard defining mobile driving licences and how they are presented in person. For a business, it delivers four things: interoperability, cryptographic verification, selective disclosure, and a defined trust model.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>standards-and-trust</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>Mobile Age Verification for Bars and Nightclubs</title>
      <link>https://laurelsecure.com/knowledge/mobile-age-verification-for-bars-and-nightclubs</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/mobile-age-verification-for-bars-and-nightclubs</guid>
      <description>Door checks fail under exactly the conditions bars operate in: low light, noise, time pressure, and inexperienced staff. Mobile ID replaces interpretation with validation for the share of patrons who carry one — and creates no entry log in the process.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>industry</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>Mobile Age Verification for Liquor and Off-Premise Retail</title>
      <link>https://laurelsecure.com/knowledge/mobile-age-verification-for-liquor-retail</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/mobile-age-verification-for-liquor-retail</guid>
      <description>Retail age checks happen mid-transaction with a line forming. Mobile ID makes the check consistent and, more importantly, removes the customer identity record that barcode scanning creates on every transaction.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>industry</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>Mobile Age Verification for Stadiums and Venues</title>
      <link>https://laurelsecure.com/knowledge/mobile-age-verification-for-stadiums-and-venues</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/mobile-age-verification-for-stadiums-and-venues</guid>
      <description>A venue&apos;s age checks happen in short peaks, on the worst network of the week, performed by a large temporary workforce. Local verification with durable queuing is the only design that holds up under those three conditions at once.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>industry</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>Mobile ID Verification Versus ID Barcode Scanning</title>
      <link>https://laurelsecure.com/knowledge/mobile-id-versus-barcode-scanning</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/mobile-id-versus-barcode-scanning</guid>
      <description>Scanning the barcode on a driver&apos;s licence reads the complete data set encoded on the card, then relies on policy to discard it. A mobile ID request can be limited to a single signed age attestation, so the rest never arrives.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>comparisons</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>Mobile ID Verification Versus Physical ID Checking</title>
      <link>https://laurelsecure.com/knowledge/mobile-id-versus-physical-id-scanning</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/mobile-id-versus-physical-id-scanning</guid>
      <description>Visual ID checking depends on human skill that degrades under exactly the conditions where it is used most. Mobile ID verification replaces interpretation with signature validation — for the portion of customers who carry one.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>comparisons</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>How NFC and Bluetooth Work Together in Mobile ID Verification</title>
      <link>https://laurelsecure.com/knowledge/nfc-and-bluetooth-in-mobile-id-verification</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/nfc-and-bluetooth-in-mobile-id-verification</guid>
      <description>NFC handles engagement — the short, deliberate exchange that sets up a session — and BLE carries the credential response. Each transport is used for what it is good at, and the split has real operational consequences.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>operations</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>Privacy-Preserving Age Verification, Explained</title>
      <link>https://laurelsecure.com/knowledge/privacy-preserving-age-verification-explained</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/privacy-preserving-age-verification-explained</guid>
      <description>Almost every age-verification product now describes itself as privacy-preserving. Five specific questions — about the request, retention, identifiers, reporting granularity, and the schema — tell you whether the phrase means anything.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>privacy</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>How Age Can Be Verified Without Sharing a Date of Birth</title>
      <link>https://laurelsecure.com/knowledge/verify-age-without-sharing-date-of-birth</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/verify-age-without-sharing-date-of-birth</guid>
      <description>A mobile ID contains signed boolean elements such as age_over_21 alongside the birth date. A verifier can request the boolean on its own, which means the business learns whether someone qualifies without learning their birthday.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>privacy</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>What Is a Mobile Driver&apos;s License?</title>
      <link>https://laurelsecure.com/knowledge/what-is-a-mobile-drivers-license</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/what-is-a-mobile-drivers-license</guid>
      <description>A mobile driver&apos;s licence (mDL) is a cryptographically signed credential issued to a phone by a state motor vehicle authority. It is not a picture of a card, and the difference is what makes a privacy-preserving age check possible.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>mobile-id-basics</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
    <item>
      <title>What Selective Disclosure Means in Practice</title>
      <link>https://laurelsecure.com/knowledge/what-selective-disclosure-means</link>
      <guid isPermaLink="true">https://laurelsecure.com/knowledge/what-selective-disclosure-means</guid>
      <description>Selective disclosure is the property that lets a mobile ID release individual verifiable fields instead of the whole document. It works because each element is committed to separately, so a subset can still be proven authentic.</description>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <category>privacy</category>
      <dc:creator>Laurel Secure</dc:creator>
      <dc:date>2026-07-30</dc:date>
    </item>
  </channel>
</rss>
