Customization

This section outlines the elements you can customize within the Upload Digital ID 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 reliable document processing across platforms.


Tutorial Screen

The Intro Screen prepares the user for the Upload Digital ID step, explains what type of document is required, and sets clear expectations before the user selects a file.


Customizable Elements

AreaWhat can be customizedNotes
TextTitle, subtitle, descriptive lineFully localizable; tone can be adapted to your brand voice.
IllustrationDigital ID illustrationCan be replaced or recolored using brand tokens.
ButtonLabel, color, radiusMust follow platform guidelines.
Background ColorScreen backgroundMust maintain strong contrast with text and elements.
Brand ColorsHeader text, accent colorUses brand tokens.
Footer"Verified by Incode" lineOptional but recommended for trust and product consistency.


Fixed Elements

ElementWhy it is fixed
File type requirement (PDF)Required to ensure consistent document processing.
Component spacing & safe areasRequired for device compatibility and visual stability.
Text hierarchyOptimized to communicate requirements clearly.
Close icon positionStandardized across all modules for consistent navigation.
WCAG contrast requirementsMandatory for accessibility and regulatory compliance.


Token Refearence

UI ElementTokenValue
Brand nameIcon/Brand/500 Static → Color/Brand/500#006AFF
Title textText/Body/800 (Primary) → Color/Gray/800#262831
Subtitle textText/Body/500 (Secondary) → Color/Gray/500#60667C
Button backgroundButton/Primary/Surface/Default → Surface/Brand/500 Static → Color/Brand/500#006AFF
Button textButton/Primary/Text/Default → Text/Body/0 Static → Color/Gray/0#FFFFFF
Footer textText/Body/500 (Secondary) → Color/Gray/500#60667C
Footer iconIcon/Brand/500 Static → Color/Brand/500#006AFF
Close iconIcon/Neutral/0 Static → Color/Gray/0#FFFFFF
BackgroundSurface/Neutral/0#FFFFFF

Design Notes

  • Keep instructions clear and specific about the required file type and format.
  • The illustration should reinforce what document the user needs to locate before proceeding.
  • Ensure tap targets meet accessibility guidelines.ns.


Review Document Screen

The Review Document Screen allows the user to confirm they have selected the correct file before proceeding. It displays a preview of the uploaded PDF and the filename, with options to continue or replace the file.


Customizable Elements

AreaWhat can be customizedNotes
TextTitle, subtitle, confirmation promptFully localizable.
Button — ContinueLabel, color, radiusMust follow platform guidelines.
Button — Replace fileLabel, color, radiusMust remain visually distinct from the primary action.
Background ColorScreen backgroundMust maintain contrast with preview and text.
Brand ColorsHeader text, accent colorUses brand tokens.
Footer"Verified by Incode" lineOptional but recommended.

Fixed Elements

ElementWhy it is fixed
Document previewRequired so users can confirm the correct file was selected.
Filename displayProvides essential reference for the user before submission.
Button placementStandardized across modules.
Close icon positionStandardized across all modules for consistent navigation.
WCAG contrast requirementsMandatory for accessibility and regulatory compliance.

Token Reference

UI ElementTokenValue
Brand nameIcon/Brand/500 Static → Color/Brand/500#006AFF
Title textText/Body/800 (Primary) → Color/Gray/800#262831
Subtitle textText/Body/500 (Secondary) → Color/Gray/500#60667C
Filename textText/Body/800 (Primary) → Color/Gray/800#262831
Button background (Continue)Button/Primary/Surface/Default → Surface/Brand/500 Static → Color/Brand/500#006AFF
Button text (Continue)Button/Primary/Text/Default → Text/Body/0 Static → Color/Gray/0#FFFFFF
Button text (Replace file)Button/Secondary/Text/Default → Text/Accent/Brand → Color/Brand/500#006AFF
Footer textText/Body/500 (Secondary) → Color/Gray/500#60667C
Footer iconIcon/Brand/500 Static → Color/Brand/500#006AFF
Close iconIcon/Neutral/0 Static → Color/Gray/0#FFFFFF
BackgroundSurface/Neutral/0#FFFFFF

Design Notes

  • Keep messaging focused on helping the user confirm their selection.
  • The Replace file button must remain clearly available so users can correct mistakes without friction.
  • Maintain clear visual separation between the primary and secondary actions.


Analyzing Screen

The Analyzing Screen is shown while the module processes the uploaded PDF and extracts identity data and QR code information. It keeps users informed during the operation with a progress indicator and a document preview.


Customizable Elements

AreaWhat can be customizedNotes
Title textProcessing message ("Analyzing..")Fully localizable; should remain concise.
Progress indicator colorAccent and background strokeUses brand tokens; must remain visually clear.
Document border colorPreview frame accentUses status positive token.
Background ColorScreen backgroundMust preserve readability and contrast.


Fixed Elements

ElementWhy it is fixed
Document previewProvides visual continuity from the review step.
Processing flow timingLinked to backend processing; cannot be shortened or skipped.
Progress indicator styleStandardized across SDK for performance and recognizability.
Spacing & safe areasRequired for device consistency.
Minimum contrastRequired for accessibility and compliance.

Token Reference

UI ElementTokenValue
Progress bar accentIcon/Status/Positive → Color/Positive/500#189F60
Progress bar backgroundSurface/Neutral/100 → Color/Gray/100#EBECEF
Title textText/Body/800 (Primary) → Color/Gray/800#262831
Document borderIcon/Status/Positive → Color/Positive/500#189F60
BackgroundSurface/Neutral/0#FFFFFF

Design Notes

  • Keep copy short to minimize cognitive load during the wait.
  • Avoid adding imagery or additional UI elements that may distract from the processing state.
  • The green border on the document preview reinforces that the file was accepted and is being processed.


Success Screen

If the document is successfully processed and identity data extracted, the user moves into the Success state. This screen provides clear confirmation before they continue to the next step in the flow.


Customizable Elements

AreaWhat can be customizedNotes
Title textSuccess message ("Successfully processed!")Fully localizable.
Subtitle textSupporting message ("Let's continue")Tone can match your brand voice.
Status iconGreen checkmarkCan replace with custom success icon; must remain clear.
Document border colorPreview frame accentUses status positive token.
ButtonLabel, color, radiusMust follow platform guidelines.
Background colorFull-screen backgroundKeep high contrast with icon and text.

Fixed Elements

ElementWhy it is fixed
Success logicMust reflect actual backend validation; not customizable.
Status color mappingGreen = positive; required for consistent semantics.
Icon placementEnsures clarity and recognition.
Button placementStandardized across modules.

Token Reference

UI ElementTokenValue
Document borderBorder/Status/Positive/Static → Color/Positive/500#189F60
Title textText/Body/800 (Primary) → Color/Gray/800#262831
Subtitle textText/Body/500 (Secondary) → Color/Gray/500#60667C
Button backgroundButton/Primary/Surface/Default → Surface/Brand/500 Static → Color/Brand/500#006AFF
Button textButton/Primary/Text/Default → Text/Body/0 Static → Color/Gray/0#FFFFFF
BackgroundSurface/Neutral/0#FFFFFF

Design Notes

  • Keep messaging short and reassuring; users should feel confident before proceeding.
  • The green border and checkmark icon reinforce the positive outcome consistently.
  • Ensure the button uses the brand 500 color to provide a clear next step with strong visual prominence.


Error Screen

Error screens appear when the system cannot process the uploaded document. This screen informs the user that the file they uploaded is not a supported digital ID type and prompts them to try a different document. While text and styling can be branded, the error itself is fixed, as it reflects the outcome of the document validation and cannot be altered or removed.


Customizable Elements

AreaWhat can be customizedNotes
Title textError message ("ID type is not accepted")Fully localizable; tone should be neutral and non-blaming.
Subtitle textSupporting messageFully localizable.
Status iconError indicatorCan be replaced; must remain clearly negative.
ButtonLabel, color, radiusAction should guide the user to retry with the correct document.
Background colorFull screenMust support strong contrast.

Fixed Elements

ElementWhy it is fixed
Error logicMust accurately reflect the document validation result.
Status color mappingRed = negative; required for clarity and consistency.
Title hierarchyEmphasizes the issue clearly.
Button placementConsistent across modules.

Token Reference

UI ElementTokenValue
Status icon backgroundIcon/Status/Negative → Color/Negative/500#E71111
Icon (X mark)Icon/Neutral/0 → Color/Gray/0#FFFFFF
Title textText/Body/800 (Primary) → Color/Gray/800#262831
Subtitle textText/Body/500 (Secondary) → Color/Gray/500#60667C
Button backgroundButton/Primary/Surface/Default → Surface/Brand/500 Static → Color/Brand/500#006AFF
Button textButton/Primary/Text/Default → Text/Body/0 Static → Color/Gray/0#FFFFFF
BackgroundSurface/Neutral/0#FFFFFF

Design Notes

  • Error messaging should be clear, direct, and action-oriented.
  • Avoid technical language; users should understand the issue at a glance.
  • Maintain consistent spacing and visual hierarchy for readability.