This section documents the end user experience and customization options for each Incode module. It's the reference for frontend engineers integrating Incode SDKs who need to know what users will see, what can be branded or restyled, and what design constraints apply.
Modules documented in this section
Biometric capture: ID Capture, Face Capture, Face Match
Document handling: Document Capture, Upload Digital ID, NFC, Manual Upload ID, OCR Review, Fiscal QR OCR
Data collection and consent: Data Sharing Consent, Geolocation, Phone Number Input, Email Input, Forms and Data Entry
Identity verification: Government Record Verification, CURP, eKYC, eKYB
Signatures: Electronic Signature, Advanced Signature, Qualified Signature
Watchlists: Watchlist and Custom Watchlist, Watchlist for Business
What each module's pages cover
Each module above is documented across four pages:
Screens & States. Every screen the end user encounters during the module flow, including loading states, success states, error states, and permission prompts. Use this to understand what UI your integration will surface and when.
Customization. What can be changed and how. Covers configurable colors, typography, copy, button styles, logos, and any module-specific customization hooks exposed through the SDK or Dashboard.
Specs & Guidelines. Design specifications and constraints: minimum tap targets, safe areas, contrast requirements, accessibility considerations, and Prizma design system alignment. Use this to validate that your customizations stay within supported limits.
V1 vs V2 Comparison. Visual and behavioral differences between the V1 and V2 experiences for modules that support both. Use this when planning a migration or deciding which version to integrate.