Customization

This section outlines the elements you can customize within the ID Capture module to match your brand while preserving Incode’s core UX. It clarifies which areas are flexible, such as text, illustrations, and brand colors and which elements remain fixed to ensure consistency, accessibility, and optimal capture performance across platforms.


Tutorial Screen

The Tutorial Screen prepares the user for the ID Capture step. It introduces the action, provides the necessary context, and sets expectations before the camera is activated.


Customizable Elements

AreaWhat can be customizedNotes
TextTitle, subtitle, body textFully localizable; tone can be adapted
IllustrationColors or full replacementMust remain clear and represent a face
Brand ColorsHeader, highlight elements, buttonUses brand tokens
ButtonsLabel, color, radiusMust follow platform guidelines
Footer“Verified by Incode” lineOptional but recommended

Fixed Elements

ElementWhy it is fixed
Layout structureEnsures consistency across modules
Spacing & safe areasRequired for device compatibility
Text hierarchyOptimized for readability
WCAG minimum contrastMandatory

Token Reference


UI ElementTokenValue
Brand namebrand-500#006AFF
Title text (“Scan your ID”)text-body-primary#262831
Subtitle text (“Ensure your ID is readable”)text-body-secondary#60667C
Illustration background surfacesurface-primary-50#E5F0FF
ID card accentsurface-brand-500-static#006AFF
Button background (“Let’s scan”)surface-brand-500-static#006AFF
Button surfacebutton-primary-surface-default#006AFF
Button textbutton-primary-text-default#FFFFFF
Background surfacesurface-neutral-0#FFFFFF
Close iconicon-neutral-500#60667C
Footer text (“Verified by Incode”)text-body-secondary#60667C

Design Notes

  • Keep copy short to minimize cognitive load.
  • The illustration uses brand 50 and brand 500 to reinforce brand identity without overwhelming the UI.
  • Ensure tap targets meet accessibility guidelines.
  • Maintain clear focus states for keyboard and screen reader users (Web).


Fake Permission Screen

The Fake Permission Screen is shown before the operating system displays its native camera permission modal. It prepares the user, explains why camera access is required, and significantly reduces the likelihood of users denying permission. This step increases trust and prevents interruptions during the ID Capture flow.


Customizable Elements

AreaWhat can be customizedNotes
TextTitle, subtitle, permission explanationFully localizable; tone should remain reassuring
ButtonsLabel (“Allow”, “Don’t allow”), color, radiusMust maintain primary/secondary hierarchy
Brand ColorsButton accents, icon color, text accentsUses brand tokens
Modal SurfaceBackground color, elevation, corner radiusMust remain high-contrast and readable
Link/Help Text“Learn more” or similar supportive textOptional; can adapt tone based on compliance needs

Fixed Elements

ElementWhy it is fixed
Background dim opacityIndicates OS-level permission flow; needed for clarity
Modal positionStandardized centered layout for all modules
Button hierarchyMirrors OS expectations; prevents accidental “Don’t allow” taps
Safety text hierarchyEnsures user comprehension before OS prompt
Spacing & safe areasRequired for device consistency
WCAG minimum contrastMandatory

Token Reference

UI ElementTokenValue
Dimmed backgroundsurface-neutral-900-80#14151A 80%
Modal backgroundsurface-neutral-light#FFFFFF
Title texttext-body-primary#262831
Subtitle texttext-body-secondary#60667C
Primary button (Allow)surface-primary-500#006AFF
Primary button textbutton-primary-text-default#FFFFFF
Secondary buttonbutton-secondary-border-default#006AFF
Secondary button texttext-brand-accent#006AFF
Header iconsicon-primary#60667C

Design Notes

  • The pre-permission modal reduces drop-off by providing context before the OS permission.
  • Maintain a clear hierarchy between primary (Allow) and secondary (Don’t allow) actions.
  • Keep the dim overlay consistent to align with OS modal expectations.
  • Ensure high contrast between modal, text, and background elements.
  • Avoid adding extra steps or interaction on this screen.


Capture Screens

During capture, the user aligns their ID within the frame, and the system evaluates real-time conditions such as glare, blur, lighting, and edge visibility. When all conditions are met, the photo is taken automatically. Colors and text on screen can be customized to match your brand, while the capture frame and auto-capture behavior remain fixed to preserve system accuracy.


Customizable Elements

AreaWhat can be customizedNotes
TextInstruction and helper text (e.g., “Fill the frame with your ID”, “Taking photo…”)Fully localizable
Brand ColorsCountdown, borders, and progress indicatorsControlled via design tokens
BackgroundDark or neutral surfacesMust maintain sufficient contrast
IconographyHelp and info iconsColor can be customized only
Footer“All photos are encrypted” or “Verified by Incode” lineOptional

Fixed Elements

ElementWhy it is fixed
ID frame shape & safe areaEnsures correct edge and glare detection
Auto-capture behaviorGuarantees consistency across devices
Detection logicRequired for accurate system-level validation
Layout & hierarchyPreserves visual and functional consistency
Minimum contrastRequired for accessibility compliance
Countdown behaviorAnimation and timing remain fixed

Token Reference

UI ElementTokenValue
Header texttext-body-invert#FFFFFF
Subtext (“Don’t move your ID…”)text-body-secondary#60667C
Countdown backgroundcountdown-surface-default#14151A
Countdown texttext-body-invert#FFFFFF
Frame borderborder-brand-500#006AFF
Capture backgroundsurface-neutral-dark#14151A
Info iconicon-invert#FCFCFD
Footer text (“All photos are encrypted”)text-body-invert#FFFFFF

Design Notes

  • The ID frame shape is fixed and cannot be altered, as it ensures correct alignment and document edge detection.
  • The progress and countdown indicators must retain their default behavior and timing to maintain capture consistency.
  • Apply brand colors subtly—use them for accents like borders or buttons, but avoid overpowering the document preview area.
  • Keep instruction text short and direct, guiding users with clear, actionable phrases (e.g., “Fill the frame with your ID”).
  • Maintain high contrast and accessible tap areas for key controls such as the help icon or retry button


Manual Capture

Manual capture is triggered after a period of inactivity (default: 30 seconds) when automatic detection conditions are not met. In this mode, the user aligns their ID within the capture frame and presses the button manually. This ensures users can complete verification even in low light, complex backgrounds, or edge-case scenarios where auto-capture cannot trigger.


Customizable Elements

AreaWhat can be customizedNotes
TextInstructional text (e.g., “Fill the frame with your ID”, “Press the button to capture”)Fully localizable
ButtonColor, label, radius, and icon colorMust comply with accessibility and tap-target standards
Brand ColorsBorder, header, and accent elementsDriven by brand tokens
BackgroundDark or neutral surfacesMust maintain sufficient contrast for ID visibility
IconsHelp/info iconsOnly icon color may be customized
Footer“All photos are encrypted” or “Verified by Incode”Optional

Fixed Elements

ElementWhy it is fixed
ID frame shape and positionEnsures accurate alignment and detection
Manual button placementEnsures reachability and consistency across devices
Detection logic fallbackManual mode always follows auto-mode failure
Layout spacing & safe zonesMaintains visual and interaction consistency
Accessibility contrastMust meet WCAG AA requirements
Button size & touch areaRequired for usability and accessibility compliance

Token Reference

UI ElementTokenValue
Frame borderborder-neutral-100#EBECF1
Instruction text (“Fill the frame with your ID”)text-body-invert#FFFFFF
Subtext (“Press the button to capture”)text-body-invert#FFFFFF
Capture button iconicon-invert#FCFCFD
Capture button backgroundtooltip-surface-neutral#262831
Background surfacesurface-neutral-dark#14151A
Help iconicon-invert#FCFCFD
Footer text (“All photos are encrypted”)text-body-invert#FFFFFF

Design Notes

  • The ID frame must remain fixed in shape to preserve detection accuracy.
  • Manual capture should always appear as a fallback after auto-capture timeout, never as a default.
  • Apply brand color accents sparingly (e.g., borders or buttons) to keep focus on the document.
  • Keep instructional copy short and directive (e.g., “Fill the frame and tap capture”).
  • Maintain clear tap areas and legible text for accessibility on all device size


ID Capture Complete (Analzying & Success)

Once the ID photo is captured — either automatically or manually — the user transitions to the Analyzing and Success screens. These stages reassure users that their ID is being securely processed and confirm when the image has passed all validation checks. Both the progress indicators and confirmation visuals can be adapted to match your brand identity..


Customizable Elements

AreaWhat can be customizedNotes
Text“Analyzing…”, “Successfully processed!”, “Now let’s capture the back”Fully localizable
Brand ColorsProgress bar, success icon, and action buttonMust follow brand tokens
SurfacesBackground and card surfacesMust ensure clarity and contrast against ID image
ButtonColor, label, and radius (e.g., Scan the back)Must meet accessibility standards
Footer“All photos are encrypted” or “Verified by Incode”Optional
AnimationProgress fill color transitionsOnly color may change; timing and animation curve are fixed

Fixed Elements

ElementWhy it is fixed
Progress bar behaviorMaintains consistent feedback rhythm across capture steps
Success timingEnsures users clearly see confirmation before advancing
Layout structureStandardized for readability and predictable UX
Minimum contrastRequired for WCAG AA compliance
Animation patternFixed to preserve continuity and visual stability across modules

Token Reference


UI ElementTokenValue
Header brandbrand 500#006AFF
Progress bar / Success barborder-status-positive#189F60
Border around ID (if shown)border-status-positive#189F60
Status text (“Analyzing…”)text-body-primary#262831
Success text (“Successfully processed!”)text-body-primary#262831
Subtext (“Now let’s capture the back”)text-body-secondary#60667C
Backgroundsurface-neutral-light#FFFFFF
Footer text (“All photos are encrypted”)text-body-primary-static#262831
Success icon (check mark)positive 600#189F60
Button background (“Scan the back”)surface-brand-500-static#006AFF
Button textbutton-primary-text-default#FFFFFF

Design Notes

  • The progress bar and success icon should use brand-positive tones but remain subtle to avoid visual clutter.
  • The ID image always remains centered and visible throughout both stages — never obscured by overlays or text.
  • Keep status text brief and affirmative (“Analyzing…”, “Success!”) for faster comprehension.
  • Maintain high-contrast text against the background and avoid overlaid color effects on ID photos.
  • Button CTAs should appear only on success (e.g., Scan the back or Continue), never during analysis.



Error Screens

Error screens appear when an issue occurs during ID capture, such as glare, blur, cut-off edges, or when all capture attempts have been exhausted. While text and visual styling can be customized, the error event types are system-defined and cannot be removed or altered.


Customizable Elements

AreaWhat can be customizedNotes
TextError titles, descriptions, and remaining attempts textFully localizable
ButtonsCTA label (“Try again”, “Continue”), button color, and radiusMust maintain clear primary/secondary hierarchy
Brand ColorsHeader, accent colors, and button colorsShould follow brand token system
IconsWarning/error icon colorOnly color may change — shapes are fixed
BackgroundLight or neutral backgroundsMust maintain strong contrast with text and icons
Footer“All photos are encrypted” or “Verified by Incode”Optional

Fixed Elements

ElementWhy it is fixed
Error event typesLinked to detection logic; cannot be reordered or removed
Error icon shapesMaintains universal recognition and visual consistency
Error layout structureStandardized for clarity and predictable behavior
“Attempts remaining” logicEnsures accuracy and reliable retry tracking
Final error behaviorMust transition to manual review once attempts are exhausted
Accessibility contrastMust comply with WCAG AA for readability

Token Reference

UI ElementTokenValue
Brand headerbrand 500#006AFF
Title text (“Glare present”, “ID scan failed”)text-body-primary#262831
Description texttext-body-secondary#60667C
Warning iconicon-status-negative#E71111
Border highlight (around ID frame)border-status-negative#E71111
Attempts texttext-body-secondary#60667C
Background surfacesurface-neutral-0-static#FFFFFF
CTA backgroundsurface-brand-500-static#006AFF
CTA textbutton-primary-text-default#FFFFFF
Footer text (“All photos are encrypted”)text-body-primary#262831

Design Notes

  • Error messaging should remain clear, direct, and action-oriented.
  • Maintain consistent spacing and visual hierarchy for readability.
  • “Try again” should always feel like the primary action when applicable.
  • Final error screens should not offer a retry, only a “Continue” action guiding users into manual review logic.
  • Avoid long or overly technical messages; users should understand the issue at a glance.
  • Include the ID image preview where possible — it helps users understand what went wrong.