DC Mobile SDK Product Guide 

Purpose Of This Guide 

This guide aims to help understand how to position, evaluate, and adopt the Digital Credential Mobile SDK in a product roadmap.

It focuses on product outcomes and implementation strategy, not API details.

Product Positioning 

Digital Credential Mobile SDK is best positioned as an identity enablement layer for mobile apps that need trusted digital credential onboarding, authentication, and data sharing.

It is especially relevant when a product needs to:

  • establish high-confidence user identity,
  • manage credentials over time on-device,
  • enable consent-based attribute exchange,
  • support interoperable in-person verification flows.

Typical industries:

  • Financial services
  • Government and public services
  • Mobility and transportation
  • Healthcare and regulated service ecosystems
  • Enterprise access and trust platforms

Core Product Capabilities 

1. Identity Enrollment 

  • Guided enrollment with configurable journey components.
  • Evidence capture support (documents, face/liveness, binding steps).
  • Resumable flow design to improve completion rates.

2. Credential Wallet Operations 

  • Local credential container abstraction.
  • Credential lifecycle actions (issue, update, rotate, remove).
  • Visibility into credential status for app-level decisioning.

3. Authentication And Request Handling 

  • Request-driven interaction model for online identity actions.
  • User-approved authentication and data release flows.
  • Structured notification pipeline for asynchronous user actions.

4. In-Person Sharing 

  • Standards-aligned in-person sharing architecture.
  • Session-based request/response model with user consent at runtime.
  • Support for offline and online verifier scenarMobile.

5. Trust, Security, And Continuity 

  • Cryptographic and key-lifecycle foundations.
  • Support for periodic update and long-term credential viability.
  • Controls for robust identity operations over time.