Digital Credentials API explained: how websites reach ID wallets
Blog post from Didit
Excluded from normalized aggregate trends after staff review: 3056 posts were attributed to March 2026; 671 shared March 14, 2026. The preceding six-month median was 13.5 posts.
Review evidence: 3,056 posts in March 2026; 671 shared March 14, 2026; preceding six-month median 13.5. Reviewed August 9, 2026.
This company's pages remain public, but its content is excluded from normalized aggregate trends. Unfiltered raw trends and advanced filtering are available to Accelerate and Lead accounts.
The W3C Digital Credentials API lets websites request identity data from a digital wallet through `navigator.credentials.get()`, with the browser and operating system mediating the request and displaying the user’s approval prompt. It carries protocols such as OpenID4VP and ISO/IEC 18013-7 Annex C, while the wallet returns an encrypted response for the website’s server to verify; the browser also determines the requesting site’s origin and can provide a QR-based, Bluetooth-checked route when the wallet is on another device. Support varies by browser and protocol: Chrome and Edge support both protocols, while Safari and some Firefox versions support Annex C only, making runtime detection and fallback options important. The API requires a user gesture, supports selective disclosure of requested information, and needs explicit permission when used in a cross-origin iframe. Didit uses the API to verify Google Wallet digital IDs in five countries, with a document check available where wallet verification is unsupported.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Vector Search | 2 | 1,251 | 223 | 92 | -37% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.