Starts with the redirectUri and is used to continue the Authorization
Code Flow issuance process. For example:
"myapp://example/credential-offer?code=xxx&clientId=myWallet&..."
For verifiers, creates a proof request.
Persist unpacked backup
This call will delete/overwrite the previously stored entries
For a wallet, handles the interaction once the wallet connects to a share endpoint URL (for example, scans the QR code of an offered credential or request for proof).
For wallets, starts the OID4VCI Authorization Code Flow.
Start scanning for ISO 18013-5 NFC engagement
system overlay messages to be displayed (iOS only)
encoded NFC engagement to be used for CreateProofRequest.isoMdlEngagement
Explicitly stop scan started via nfcReadIsoMdlEngagement
For wallets, initiates device engagement for offline flows.
Reference the verificationEngagement entry of your configuration
for your options for engagement.
Close unpacked backup
This call will restore the old entries prior calling unpackBackup
Uninitialize the core instance
Any following calls on this instance will fail. A new core instance has to be initialized after.
If true, also delete all data from the DB, otherwise data will be persisted for the next core instance
Start import procedure
This call will open the provided backup file, other subsequent function calls like getCredentials will return data from the imported package After this successful call, either finalizeImport (to persist the changes) or rollbackImport (to revert to old data) must be called
User password matching selected during creation of the backup file
Path to the stored backup file
For wallet-initiated flows, continues the OpenID4VCI issuance process after completing authorization.