Core capabilities to integrate

The Holder SDK provides three main capability areas that map to the credential lifecycle. This page introduces each one and links to the deeper capability overviews and tutorials.

Core capabilities to integrate

The SDK provides three main capability areas that map to the credential lifecycle.

Credential claiming

Your app receives credential offers (via QR code scan, deep link, or silent push) and claims them using the OID4VCI protocol.

What you implement:

• Handle incoming credential offer URIs (QR scanner, deep link handler, or push notification).
• Trigger the SDK's claiming flow with the offer URI.
• Display claiming progress and result to the user.
• Store credentials securely (handled by the SDK).

Key decisions:

• Which offer channels to support (QR, deep link, push).
• How to surface the claiming experience in your app's navigation.
• Whether to show credential details before accepting.
• Whether your app uses an open model (any compatible wallet can claim) or a restricted model (only your app can claim via custom URI schemes or App Links/Universal Links). This affects whether users can scan QR codes with the device's native camera or must use your in-app scanner.
• Whether the issuer requires wallet attestation. If enabled, the Holder SDK proves your app's authenticity before claiming credentials. The SDK handles the attestation proofs for you once SDK Tethering is configured, so no additional wallet backend integration is required.

See claiming credential offers and the credential claiming overview for details. Use the quickstart to get started.

In-person (proximity) presentation

Your app presents credentials to nearby verifiers over Bluetooth Low Energy, following ISO/IEC 18013-5.

What you implement:

• Display a QR code for the verifier to scan (engagement phase).
• Handle the BLE connection and data exchange (managed by SDK).
• Show the user what data is being requested and collect consent.
• Display presentation result.

Key decisions:

• How to integrate the presentation trigger into your app's UI.
• Consent screen design (what data elements to show, how to explain them).
• How to handle offline scenarios (no network connectivity).
• Whether to prepare for NFC engagement (currently in development). For iOS apps, consider applying for the Apple NFC entitlement early to enable NFC-based engagement when available.

See the proximity presentation overview and tutorial.

Remote presentation

Your app responds to remote verification requests from web or mobile verifiers using ISO/IEC 18013-7 and OID4VP.

What you implement:

• Handle incoming presentation requests (redirect, QR, or Digital Credentials API).
• Show the user what data is being requested and collect consent.
• Submit the presentation response via the SDK.
• Handle same-device and cross-device scenarios.

Key decisions:

• Which invocation methods to support (redirects, QR scanning, Digital Credentials API).
• Same-device vs cross-device flow handling.
• How to return the user to the requesting app/website after presentation.

See the remote presentation overview and tutorial.

Next steps

Next, see how these capabilities fit together in the integration architecture.