Everything Identra shipped in H1, in one place.
SYS_OK
DEC_A
ID_VERIFIED
LIVENESS_1
DEC_A
ENCRYPT_256
LIVENESS_1
SYS_OK
ID_VERIFIED
ENCRYPT_256

Design verification screensthat reflect your brand identity

Turn Dynamic Flow steps, states, and outcomes into a clear customer experience.Shape, localize, preview, and validate every screen in one workspace.

Interactive Studio workspace
Display logo
Live canvas preview (light)
IDIDENTRA
Step Welcome

Start with confidence

Introduce the journey and set expectations before verification begins.

Interface configuration

Generated Interface Studio configuration

import { IdentraVerifySDK } from '@identra/sdk';


<IdentraVerifySDK

brandColor="#354CE1"

borderRadius="rounded"

showLogo={true}

theme="light"

/>

Design tokens

--brand-primary: #354CE1;

--corner-radius: 12px;

WHY INTERFACE STUDIO

One place to shape the experience around every verification decision.

Give product, design, operations, and compliance teams a shared view of what customers see at every step.

Compose screens from reusable blocks

Arrange headings, instructions, consent, credential requests, progress, status, and actions without rebuilding common patterns.

Connect content to journey data

Bind approved runtime fields and show the right content only when journey conditions are met.

Adapt across languages and devices

Manage localized copy, light and dark themes, and responsive overrides while previewing the result in context.

Find issues before export

Check accessibility, compare visual baselines, and resolve blocking issues before handing off an experience.

FROM JOURNEY LOGIC TO CUSTOMER EXPERIENCE

Keep every screen connected, intentional, and ready to evolve.

Interface Studio follows the structure of Dynamic Flow while giving teams the tools to control content, presentation, and release quality.

01 / 01 / CONNECT

Start from the journey that already exists

Screens and variants stay associated with the modules, states, and outcomes defined in Dynamic Flow.

  • Create screens for welcome, consent, modules, processing, success, and error states
  • Match interface variants to supported module states and outcomes
  • Keep the experience aligned as journey logic changes

Journey connection

Logic synchronized
Flow step mapped
State variants ready

Outcome linked

02 / 02 / COMPOSE

Build each state from clear, reusable blocks

Shape the content and actions customers need, then connect them to safe runtime data and visibility rules.

  • Arrange reusable content and interaction blocks
  • Bind dynamic content with a localized fallback
  • Control visibility with flow and module conditions

Screen composition

Ready to edit
Content blocks
Dynamic binding
Visibility rules

03 / 03 / ADAPT

Preview the right experience for every context

Review language, device, theme, typography, and layout together instead of treating them as separate handoffs.

  • Edit the default locale and add localized content
  • Preview mobile, tablet, and desktop in light or dark mode
  • Apply responsive overrides or import a design system

Context preview

Preview in context

Five locales

Three breakpoints

Light and dark

04 / 04 / VALIDATE

Prove the experience before it leaves the workspace

Run journey scenarios, audit essential accessibility requirements, and compare visual baselines before export.

  • Walk through a scenario step by step or autoplay the journey
  • Catch accessibility and manifest validation issues
  • Use visual regression and export gates to prevent incomplete handoffs

Release readiness

Ready to export
Journey preview passed
Accessibility checked
Visual baseline matched
ONE JOURNEY, TWO COORDINATED WORKSPACES

LOGIC AND EXPERIENCE IN STEP

Design the decision and the experience together.

Dynamic Flow controls what the journey does. Interface Studio controls how each step is presented. Both stay connected through the same screens, states, and outcomes.

Journey logic

Dynamic Flow

Define modules, conditions, routes, and outcomes that determine what happens next.

Always synchronized

Customer experience

Interface Studio

Shape screens, content, themes, responsive behavior, and localized variants for the journey.

BUILT-IN RELEASE CONFIDENCE

Catch experience issues before export.

Quality checks live beside the design work, so teams can fix problems while the context is still visible.

Accessibility checks

Review essential requirements such as labels, alternative text, and readable structure.

Visual baselines

Capture a screen, variant, device, theme, and locale context for later comparison.

Export readiness

Block incomplete handoffs when interface, flow, or regression issues still need attention.

INTERFACE STUDIO FAQ

A clearer way to manage the customer-facing side of verification.

Answers to the questions teams usually ask before shaping their first experience.

No. Teams can compose screens from supported blocks, edit content, apply themes, and configure common behavior visually. Design-system import and structured export remain available when engineering teams need a deeper handoff.

START WITH A MORE COHERENT EXPERIENCE

Turn journey logic into screens customers can understand and trust.

Open Interface Studio in the Dashboard or talk with Identra about the experience your team wants to create.