This section is for frontend engineers, designers, and product teams integrating Incode modules into an onboarding or verification flow. It covers what users see, how modules behave, and what you can customize to match your brand.
The section has two main areas:
Prizma Design System. Incode's design system: components, tokens, and the Prizma Dashboard. Start here if you need foundational design decisions, token references, or component specs.
Module Customization. Per-module documentation covering screens and states, customization options, specs and guidelines, and V1 vs V2 comparisons. Start here if you're integrating a specific module and need to know what it looks like, what you can change, and what design constraints apply.
Accessibility
Accessibility is built into every module. Each module's Specs & Guidelines page covers accessibility notes specific to that module, including contrast, screen reader behavior, keyboard navigation, and motion guidelines.
For the cross-cutting accessibility principles that apply across all modules, see the Accessibility Overview.
How to use this section
When you're integrating a module:
- Open the module under Module Customization.
- Review Screens & States to understand what the user will see.
- Review Customization to understand your branding options.
- Check Specs & Guidelines for design constraints and accessibility notes.
- If the module has both a V1 and V2 experience, check V1 vs V2 Comparison to decide which to integrate.
If you need help locating a module or want to confirm something about a flow, reach out to your Incode representative.