@mattrglobal/verifier-sdk-web 2.1.1-unstable.6 → 2.1.1-unstable.66

package/README.md

@@ -18,6 +18,7 @@
   - [Determine supported presentation flows](#determine-supported-presentation-flows)
   - [Define wallet identifiers](#define-wallet-identifiers)
   - [Configure redirectUri](#configure-redirecturi)
+  - [Request credentials using the DC API](#request-credentials-using-the-dc-api)
 - [Request credentials examples](#request-credentials-examples)
   - [Request credentials with automatic flow selection](#request-credentials-with-automatic-flow-selection)
   - [Request credentials with explicit same-device flow](#request-credentials-with-explicit-same-device-flow)
@@ -42,6 +43,7 @@ The Verifier Web SDK is a powerful tool for integrating online credential verifi
 * Supports both same-device and cross-device presentation flows.
 * Secure handling of mDocs requests and responses.
 * Compliant with [ISO/IEC DTS 18013-7](https://www.iso.org/standard/82772.html).
+* Offers [DC API](https://wicg.github.io/digital-credentials/) support as a **tech-preview**.
 
 > In this SDK mDocs are referred to as Mobile Credentials.
 
@@ -192,6 +194,45 @@ You can define an identifier of a specific wallet you want to invoke with this v
 
 When using the same-device presentation flow, the SDK must define what URI to redirect the user to once they complete the verification workflow in their wallet app. This can be any URI (including custom URI schemes), and must match one of the values defined in the [`redirectUris` array](https://learn.mattr.global/api-reference/latest/tag/Verifier-applications#operation/postVerifierApplication!path=0/openid4vpConfiguration/redirectUris&t=request) when creating a verifier application.
 
+## Request credentials using the DC API
+
+> DC API support is currently offered as a **tech preview**. As such, functionality may be limited, may not work in all scenarios, and could change or break without prior notice.
+
+1. Add the `dcApiConfiguration` object to your MATTR VII [verifier application configuration](https://learn.mattr.global/docs/verification/remote-verification-api-reference/verifier-applications#update-a-verifier-application).
+
+2. Use the SDK's `isDigitalCredentialsApiSupported` method to determine if the user's browser supports the Digital Credentials API:
+
+```typescript
+import * as MattrVerifierSDK from "@mattrglobal/verifier-sdk-web";
+
+const isDcApiSupported = MattrVerifierSDK.isDigitalCredentialsApiSupported();
+```
+
+This returns `true` if the browser supports DC API, `false` otherwise.
+
+3. When calling `requestCredentials`, conditionally set the `walletProviderId` based on DC API support:
+
+```typescript
+const options: MattrVerifierSDK.RequestCredentialsOptions = {
+  credentialQuery: [credentialQuery],
+  challenge: MattrVerifierSDK.utils.generateChallenge(),
+  openid4vpConfiguration: {
+    redirectUri: window.location.origin,
+    walletProviderId: isDcApiSupported ? undefined : "your-wallet-provider-id",
+  },
+};
+
+const results = await MattrVerifierSDK.requestCredentials(options);
+```
+
+The Verifier Web SDK uses the DC API **only when all** of the following conditions are met:
+
+- The browser supports DC API (`isDigitalCredentialsApiSupported()` returns `true`).
+- The credential request is for a **single credential** (DC API doesn't support multiple credentials in one request).
+- No `walletProviderId` is provided in the request options.
+
+If any condition is not met, the SDK falls back to the standard OID4VP flow.
+
 # Request credentials examples
 
 ## Request credentials with automatic flow selection

package/dist/lib/verifier-js-no-deps.cjs.js

@@ -7,7 +7,7 @@
  * Do Not Translate or Localize
  *
  * Bundle of @mattrglobal/verifier-sdk-web
- * Generated: 2025-09-28
+ * Generated: 2025-11-23
  * Version: 2.1.0
  * Dependencies:
  */