.png%3Falt%3Dmedia%26token%3D284d0a12-bbfc-473c-96ec-60d80361d5aa)
.png%3Falt%3Dmedia%26token%3D284d0a12-bbfc-473c-96ec-60d80361d5aa)
elKYC Android SDK
Search…
Usage
Introduction
This SDK will help you to build a verification process for your project, the goal is to build easy steps which you can run and get the result to your system or in your application. This is the main part SDK's that contains the verification process launcher and common steps.
The whole process goes step by step. On each step where data is obtained it is forwarded to our server or one that you provided. The process will stop if any step returns a critical error.
It is built as Kotlin DSL.
Configuration
Before launch SDK must be configured
1
val config = elkycConfig {
2
customFlow = steps
3
clientKey = "clientKey"
4
appKey = "appKey"
5
workplace = workplaceConfig
6
}
Copied!
customFlow- sequence of steps that the verification process consist of (required)clientKey- client key (required)appKey- application key (required)workplace- parameters of workplace (optional)
1
workplaceConfig = WorkplaceConfig(
2
host = "https://workplace.com",
3
authPath = "/api/sdk/auth/signIn",
4
mainPath = "/api/sdk/workplace/verification",
5
encryptData = false,
6
rssigSalt = "salt",
7
accessToken = "accessToken",
8
clientSession = "clientSession"
9
)
Copied!
host- HTTPS Host to which the data you want to be sent (optional, by default data won't be sent)authPath- path for the sign in request (optional)mainPath- path that is used for sending the data (optional)encryptData- specifies if the data should be encrypted (optional, by default false)rssigSalt- is used for response signature validation (optional, by default signature is not being validated)accessToken- will be added to each request as Bearer authentication (optional)clientSession- will be added as header x-client-session to each request (optional)
Launch
1
Elkyc.startVerification(
2
activity = requireActivity(),
3
config = config,
4
requestCode = "RESULT_REQUEST_CODE",
5
resultLauncher = resultLauncher,
6
isDebug = true,
7
printLog = true,
8
callback = { data: ConclusionData -> }
9
)
Copied!
activity- your activity that is used to start SDKrequestCode- WIPresultLauncher- WIPisDebug- specifies if build is debuggableprintLog- use it to print log (optional, by default false)callback- block where you will receive a resulting data of document scanning, liveness and matching (optional)
Last modified 4mo ago
Copy link