Implementation Guide
Authentication
A unique access token should be created upon each SDK entry. In order to generate an access token, please refer to Valify's Authentication Documentation.
Security Warning: For improved security, consider implementing the access token fetching logic outside the Activity. This helps keep sensitive credentials secure and reduces potential exposure within the Activity/Fragment code.
Importing
Import the module’s function in your file using the following line
import 'package:vidvocr_flutter_plugin/vidvocr_flutter_plugin.dart';Configurations
The plugin builder is separated into two components.
Required Configurations
Initialize the required parameters as follows while adding the required configurations
final String baseURL = ' '; //put your acctual base url here
final String bundleKey = ' '; //put your actual bundle key here
final String accessToken = ' '; //put your actual access token here
Optional Configurations
Initialize the required parameters as follows while adding the desired configurations
Configurations Breakdown
This section shows the breakdown of all optional builder configurations.
The following line is where the user interface language is set.
If this flag is set to true, the SDK performs additional data validations on the document. These validations are returned in the SDK response as flags, and you must implement your own handling logic based on these flags [Handling Document Verification Plus Flags in Code] , the SDK does not auto-reject or block the transaction.
View Document Verification Plus Breakdown here: [Understanding Document verification plus flag]
If this flag is set to true, the SDK detects potential physical or digital manipulation in the National ID. These validations are returned in the SDK response as flags, and you must implement your own handling logic based on these flags [Handling Advanced Confidence Flags in Code] , the SDK does not auto-reject or block the transaction.
View Advanced Confidence Breakdown here: [Understanding Advanced Confidence flag]
If the following line is set to true, the captured image will be displayed for the user.
If the following line is set to true, the SDK will automatically enable manual capture if it detects that the user is unable to autocapture card.
If the following line is set to true, a screen is added to the user flow that displays the images captured and the OCR result to the user.
If the following line is set to true, the SDK purely performs image capturing and only returns these images in the SDK response.
The following line is optional and can be used to receive event logs from the SDK experience to be used for user behavior analysis.
The following line is optional and can be used to set your company's branding color to the SDK's user interface.
If the following line is set to
true, the Valify logo will be hidden from the SDK user interface.
The following line can be used to display a custom logo instead of the default Valify logo. The value should be a base64-encoded image string.
The following line is optional and can be used to set any headers that may be required for purposes specific to your application. Any headers set will be sent along with each API call made by the SDK.
Parameter Declaration
Declare the SDK parameters with the configuration variables previously created
Start the SDK
Use the following code snippet to run the plugin
Sample Integration Example
Check out our GitHub repository for a simple integration app demonstrating how to use our SDK. The repository includes step-by-step instructions and sample code to help you get started quickly.
Last updated