Appearance
Theme, colors, corners and typography.
Localization
Languages and copy overrides.
Document capture
Detection, capture mode, preview and retakes.
Screen toggles
boolean
default:"true"
An intro screen listing the steps the user is about to go through.Worth keeping. Users who know a selfie is coming are less likely to abandon at the
liveness step. Turn it off only if your own screen already explains the flow.
boolean
default:"true"
A final screen rendered by the SDK after the flow ends, whether it succeeded or failed.Turn this off when you want to render your own outcome screen — the result is returned
to you either way, so nothing is lost.
boolean
default:"false"
Includes technical detail in the error messages shown to the user.
Location permission
This controls whether the SDK asks for location at the start of the flow.
Only enable it if you use
on_gps_mock_location or on_gps_ip_location_mismatch in device policy. It is an extra prompt early in the flow, and some users drop out there.
On iOS,
requiresLocationPermission: true also needs NSLocationWhenInUseUsageDescription in your Info.plist. See iOS installation.Build the config where?
Unlike the transaction configuration, this one is purely cosmetic and behavioural — it decides what the flow looks like, never what gets accepted. It is safe to build it in the app.Platform naming
The same concepts, spelled to each platform’s conventions:
Color keys, localization keys and enum values are identical across platforms, so a design
spec or a copy deck written once applies to both.

