Skip to main content
The SDK provides various options for modifying the verification flow.

​
SSL pinning support

By default, the SDK does not utilize SSL pinning as suggested by AWS services. If you need this option, you can enable SSL pinning. Our SSL pinning implementation follows the AWS recommendations and uses pinning for the Root certificates. They are valid for more than 5 years. However, during this timeframe, major changes can occur and we might be forced to change SSL pinning. Such changes will be notified at least 1 month prior. We strongly encourage you to enable this feature only if you are planning to actively update the SDK. 
    val idenfySettingsV2 = IdenfyBuilderV2()
        .withAuthToken(authToken)
        .withSSLPinning(true)
        ...
        .build()
    ...

​
Localization

By default the SDK provides the following translations:
  • English (en) GB
  • Polish (pl) PL
  • Russian (ru) RU
  • Lithuanian (lt) LT
  • German (de) DE
  • French (fr) FR
  • Italian (it) IT
  • Latvian (lv) LV
  • Romanian (ro) RO
  • Swedish (sv) SV
  • Spanish (es) ES
  • Estonian (et) ET
  • Czech (cs) CS
  • Bulgarian (bg) BG
  • Dutch (nl) NL
  • Ukrainian (uk) UK
  • Portuguese (pt) PT
  • Vietnamese (vi) VI
  • Slovak (sk) SK
  • Indonesian (id) ID
  • Thai (th) TH
  • Hindi (hi) HI
  • Hungarian (hu) HU
  • Danish (da) DA
  • Greek (el) EL
  • Croatian (hr) HR
  • Norwegian (no) NO
  • Serbian (sr) SR
  • Finnish (fi) FI
  • Turkish (tr) TR
  • Chinese (zh) ZH
  • Slovenian (sl) SL
  • Japanese (ja) JA
All keys are located here. You can supply partial translations — if you do not include a translation for a particular key, the SDK will use the default. To see changes, add the particular XML to your app target or copy only specific keys in your strings.xml and changes will take effect.

​
Forcing a specific language

The default language of the SDK is selected by the language configuration of the device. To force a particular locale, several methods can be used:

​
IdenfySettings

    IdenfySettingsV2.IdenfyBuilderV2()
    .withSelectedLocale(IdenfyLocaleEnum.EN)
    ...

​
Along with token generation

Set the locale during token generation.
If no locale is forced, the SDK will fall back to the device’s selected language.

​
Enabling screenshot blocking

When enabled, any screenshots or screen recordings in camera fragments will result in a black screen. 
    IdenfySettingsV2.IdenfyBuilderV2()
    .withBlockScreenshotAndScreenRecording(true)
    ...

​
Skipping parts of the verification flow

The SDK provides a set of tools to omit some views, which you could implement in your own application for a fine-grained approach. For example, you might want to implement document selection and the document’s issuing country selection in the same view instead of having two separate screens.
All customization options listed below can be combined, e.g. you can skip document selection, document onboarding screen, and document issuing country selection at the same time.
Contact tech support to enable any of these features in your account settings, since they are configured from the backend, not the SDK. Contact support via the Dashboard using your account.

​
Skip document issuing country selection screen

Generate a verification token with the provided document issuing country. See the verification token generation documentation. Example JSON request body: 
{
  "clientId": "TEST_CLIENT_ID",
  "country": "lt"
}

​
Skip document selection screen

Generate a verification token with the provided document type. See the verification token generation documentation. Example JSON request body: 
{
  "clientId": "TEST_CLIENT_ID",
  "documents": ["PASSPORT"]
}

​
Skip document onboarding screen

After this feature is enabled, the onboarding screen will be skipped. The user can select a document from the documents list and will be immediately redirected to the camera screen.

​
Blur and glare flow changes

If your account has enabled blur or glare detection, the SDK will include blur and glare checks in the photo validation. An unsuccessful result will be shown immediately after each step. With blur or glare
To enable blur and glare detection, contact tech support via the dashboard.

​
Passive liveness check

If your account has enabled passive liveness check, the SDK will include a liveness check in photo validation. An unsuccessful result will be shown immediately after each step. Android Passive liveness
To enable passive liveness check, contact tech support via the dashboard.

​
Identity verification results screen changes

If you have implemented manual verification flow (step 11), it might be wise to disable the Manual results view, DENIED, and APPROVED views for better UX. Since you will most likely display a loading screen or indicate to the user that an ongoing manual verification check is in progress after they complete the verification flow, the SDK finishes during the loading screen without showing the actual status. This empowers you to customize it in your preferred way. Immediate redirect To disable those views, the immediate redirect feature can be applied. After enabling immediate redirect:

​
APPROVED screen will not be visible

If verification was approved, the user will not see a success screen. The SDK will close while displaying a loading screen, allowing you to show a success screen yourself.

​
DENIED screen will not be visible

The denied screen will not be visible. The SDK will close while displaying a loading screen, allowing you to display an error screen yourself.

​
Manual verification screen will not be visible

The manual verification screen (shown above) will be skipped.
To enable immediate redirect, contact technical support via the Jira customer portal.
If you would like to replace the results view with your own custom view and control the flow yourself, see the UI Customization guide.