BlinkIdVerifyConsentUxConfig

Consent configuration of the scanning screen.

BlinkID Verify Cloud requires explicit end-user consent for every transaction. This configuration decides how the scanning session obtains it:

• RequireConsent - the SDK shows the built-in consent screen and builds an ExternalConsentObject when the end user accepts. The integrator must supply RequireConsent.userId. ExternalConsentObject.givenOn is set by the SDK at acceptance time and is not configurable here.

• ProvideExternalConsent - the integrator collected consent on their own UI and hands over a complete ExternalConsentObject, so no consent screen is shown.

• NoConsentNeeded - no consent screen and no consent object in the generated request payload. Use it only with self-hosted deployments, which do not require consent.

Whichever variant is used, the resolved consent object is passed into native getResult when the capture result is retrieved, and is also available on the capture session result's consent field.

The SDK does not persist consent. To reuse consent across sessions, persist the consent object of a previous capture result and pass it back through ProvideExternalConsent.

Inheritors