Google Launches Digital Credentials API Origin Trial for Chrome Developers

Google’s move to expose a Digital Credentials API in Chrome 128 reflects a broader push to embed verifiable identity into the web stack, a shift that could reshape how online services handle age‑gating, fraud prevention, and regulatory compliance. According to the Chrome for Developers blog, the origin trial lets a “relying party” (RP) website request specific credential data—such as a driver’s license or national ID—from a user’s digital wallet, with the browser acting as a secure conduit between the site and the operating system’s credential store. The API is deliberately protocol‑agnostic, allowing developers to define the exchange format that best fits their use case, while the underlying OS handles credential discovery, user authentication, and cryptographic verification of the issuer’s signature [Chrome for Developers].

The timing of the trial aligns with a rapid expansion of device‑bound digital IDs in the United States. Several states—including Arizona, California, Colorado, Georgia and Maryland—have already begun issuing mobile driver’s licenses that can be stored in Google Wallet, according to the same blog post. Those credentials are built on standards that support enhanced security, selective disclosure and cross‑border interoperability, features that the API is designed to surface to web applications. For example, an RP could request proof that a user is over 18 without exposing the full birthdate, leveraging the “selective disclosure” capability highlighted by the Chrome team [Chrome for Developers].

From a regulatory perspective, the rollout dovetails with emerging legal frameworks such as the European Union’s eIDAS 2.0, which aims to standardize electronic identification across member states. VentureBeat notes that Google is already positioning Android as a platform for electronic IDs, suggesting that the browser‑level API is part of a coordinated strategy to make digital credentials a first‑class web primitive [VentureBeat]. By integrating the request flow into Chrome, Google hopes to reduce reliance on ad‑hoc URL schemes that developers have used to invoke wallet apps, thereby tightening security and mitigating abuse vectors that have plagued earlier implementations.

The trial also signals a potential new revenue stream for Google’s broader ecosystem. As more RPs adopt the API for age verification, identity checks, or driving‑privilege validation, the demand for compatible wallet solutions—most notably Google Wallet—could rise sharply. While the Chrome blog does not disclose any monetization plans, the ability to surface verifiable credentials directly in the browser creates a frictionless user experience that could accelerate adoption of digital IDs in sectors ranging from e‑commerce to car‑sharing. TechCrunch has reported that Google Wallet is expanding support for digital IDs across additional states, reinforcing the notion that the API is a strategic enabler for a larger credential‑as‑a‑service offering [TechCrunch].

Analysts will be watching the origin trial’s uptake metrics closely. Because the API is still in an experimental phase, developers must opt‑in via an origin trial token, and Chrome will collect usage data to inform a possible stable release. If the trial demonstrates robust security outcomes and developer interest, the API could become a standard component of the web platform, much like the Payment Request API did for online checkout. Until then, the trial remains a litmus test for whether the web community is ready to shift from fragmented, proprietary identity solutions to a unified, standards‑based model for digital credentials.