Documentation Index
Fetch the complete documentation index at: https://docs.quepass.com/llms.txt
Use this file to discover all available pages before exploring further.
Journey Integration flow
Get Configuration from the server.
Get User / Registered User details.
What SDK Does
| Feature | Description |
|---|
| Registration | Register new users with document and biometrics |
| Authentication | Login with document number and face |
| Transaction | Verify high-security transactions with UID and biometric |
| Search | Search users by face only (kiosk-style) |
| Event Registration | Event registration via QR code |
| Event Check-In | Event check-in via QR scan or biometric or kiosk-style |
| User Profile | Get user/registrant data after verification |
| Search By Img | Manual face capturing |
| Kiosk Mode | Continous Data by capturing face |
| Customer lifecycle | Shows for how long will the customer remain active |
| Customer Status | The customer’s status (Active or Inactive) |
| SDKsCapabilities | Information of SDKs Version. |
| ExpressOnboarding | Registers users using only government ID details. |
| ExpressVerification | Check government ID exist or not. |
Initialization & Configuration
The SDK must be initialized before using any KYC or biometric functionality.
1. Initialization
Required Parameters
- email (string) – Operator email address
- password (string) – Operator password
- channel (string) – Channel identifier issued by Quepass
- baseURL (string) – Root URL of the Quepass backend
Return Parameters
sessionId (string) – Unique identifier for the user sessiontoken (string) – Authentication token for API access
Code Example
@Inject
lateinit var sdkInitializer: SDKInitializer also in you on create initialize it like below
onCreate(){
// ONE TIME initialization
SDK.initialize(sdkInitializer)
}
2. Configuration
Required Parameters
- email (string) – Operator email address
- password (string) – Operator password
- channel (string) – Channel identifier issued by Quepass
- baseURL (string) – Root URL of the Quepass backend
Return Parameters
- s_SessionTimeout (number|string) – session timeout duration
- onboardingFlow (object|array) – configuration for onboarding flow
- verificationFlow (object|array) – configuration for verification flow
- govIntegration (boolean) – government integration enabled or not
- allowedJourneys (array of strings) – list of allowed journeys
Code Example
val sdk = KycSdk.initialize(
baseUrl = "https://your-base-url.com",
email = "email",
password = "password",
channelId = "unique-channel-id"
)
Journey
Journeys are flows launched
| Journey | Constant | Purpose |
|---|
| Onboarding | register | User registration with document and biometrics |
| Authentication | authentication | User login using biometric verification |
| Transaction | transaction | Biometric verification for secure transactions |
| Search | search | Identify or search users using biometrics |
| KioskMode | kioskModeCamera | Continuous face capture for kiosk-style identification |
| EventQRRegistration | registerEventByQR | Event registration using QR code |
| EventBiometricCheckIn | checkinByBiometric | Event check-in using biometric verification |
| CheckinByQR | checkinByQR | Event check-in by scanning QR code |
| SearchByImage | searchByImage | Search users by capturing or uploading an image |
| ExpressOnboarding | expressOnboarding | Registration using only government ID details |
| ExpressVerfication | expressVerification | Verification using government ID parameters |
User Profile
| Method | Purpose |
|---|
| getUserDetails | Retrieve user profile information using UID and consent token |
| getRegistrantDetails | Fetch registrant details for a specific event using UID, event ID, and token |
| getKycCertificate | Retrieve the user’s KYC certificate using UID and token |
| toggleCustomerStatus | Activates or deactivates a customer using UID. |
| setCustomerLifeCycle | Sets customer active/inactive status for a specific date range. |
Ensure that a valid UID and consent token are available before calling these SDK methods, as most identity, event, and biometric operations require authenticated user context to return accurate results.
