@incodetech/prizma-core-screens 0.2.7 → 0.2.12

package/src/DigitalIdUploadErrorScreen.tsx

@@ -0,0 +1,83 @@
+import React, { forwardRef } from 'react';
+import { PrizmaCaptureDigitalId } from '@incodetech/prizma-core-web/capture-digital-id';
+import { PrizmaReviewScreen, type PrizmaReviewScreenProps } from './ReviewScreen';
+import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
+import type { DigitalIdUploadStrings } from './DigitalIdUploadStrings';
+import './ScreenLayout.css';
+
+export interface DigitalIdUploadErrorScreenProps
+  extends Omit<
+    PrizmaReviewScreenProps,
+    | 'stage'
+    | 'title'
+    | 'subtitle'
+    | 'successTitle'
+    | 'analyzingLabel'
+    | 'primaryLabel'
+    | 'secondaryLabel'
+    | 'verifiedLabel'
+    | 'children'
+  > {
+  /** Module copy — this screen reads the `error` slice. */
+  strings: DigitalIdUploadStrings;
+  screenId?: string;
+  overrides?: PrizmaScreenOverrides;
+  onAction?: PrizmaScreenActionHandler;
+}
+
+/**
+ * Digital ID Upload — the uploaded file was rejected, built on the
+ * `PrizmaReviewScreen` archetype's `error` stage (GUIDELINES.md §6-H). Figma:
+ * `Upload Digital ID` file (wxFsHRvllern4VnjRqM4JO), `Errors` section,
+ * `Error` frame (node 25874:11957).
+ *
+ * Kept separate from `DigitalIdUploadReviewScreen` (the confirm flow) rather
+ * than folded into it as a fourth stage of that wrapper — same split Document
+ * Capture draws between its confirm screens and
+ * `DocumentCaptureGenericErrorScreen`, even though here both wrappers happen
+ * to share the same archetype under the hood. The media is
+ * `PrizmaCaptureDigitalId state="error"` (red 4px border) — the same managed
+ * component every other stage uses, not a bespoke verdict illustration — and
+ * the header/footer are hidden exactly like `analyzing`/`success`
+ * (`centeredWhenNoNav`, since this Figma frame draws the identical symmetric
+ * header/media/CTA skeleton).
+ */
+export const DigitalIdUploadErrorScreen = forwardRef<
+  HTMLDivElement,
+  DigitalIdUploadErrorScreenProps
+>(
+  (
+    {
+      strings,
+      screenId = 'digital-id-upload-error',
+      showHeader = false,
+      showFooter = false,
+      overrides,
+      onAction,
+      ...shell
+    },
+    ref,
+  ) => (
+    <PrizmaReviewScreen
+      ref={ref}
+      stage="error"
+      title={strings.error.title}
+      subtitle={strings.error.subtitle}
+      primaryLabel={strings.error.ctaLabel}
+      centeredWhenNoNav
+      verifiedLabel={strings.verifiedLabel}
+      navLabel={strings.navLabel}
+      showHeader={showHeader}
+      showFooter={showFooter}
+      screenId={screenId}
+      overrides={overrides}
+      onAction={onAction}
+      {...shell}
+    >
+      <PrizmaCaptureDigitalId state="error" />
+    </PrizmaReviewScreen>
+  ),
+);
+DigitalIdUploadErrorScreen.displayName = 'DigitalIdUploadErrorScreen';
+
+export default DigitalIdUploadErrorScreen;

package/src/DigitalIdUploadFileTooLargeScreen.tsx

@@ -0,0 +1,67 @@
+import React, { forwardRef } from 'react';
+import { PrizmaResultScreen, type PrizmaResultScreenProps } from './ResultScreen';
+import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
+import type { DigitalIdUploadStrings } from './DigitalIdUploadStrings';
+import './ScreenLayout.css';
+
+export interface DigitalIdUploadFileTooLargeScreenProps
+  extends Omit<
+    PrizmaResultScreenProps,
+    'status' | 'title' | 'subtitle' | 'ctaLabel' | 'verifiedLabel' | 'navLabel'
+  > {
+  /** Module copy — this screen reads the `fileTooLarge` slice. */
+  strings: DigitalIdUploadStrings;
+  screenId?: string;
+  overrides?: PrizmaScreenOverrides;
+  onAction?: PrizmaScreenActionHandler;
+}
+
+/**
+ * Digital ID Upload — the selected file exceeds the size limit, built on the
+ * `PrizmaResultScreen` archetype (GUIDELINES.md §6-F). Figma: `Upload Digital
+ * ID` file (wxFsHRvllern4VnjRqM4JO), `Errors` section, `File Limit Error`
+ * frame (node 26083:3981).
+ *
+ * Unlike `DigitalIdUploadErrorScreen` (the rejected-document verdict, built on
+ * the Review archetype because it reuses `PrizmaCaptureDigitalId`), this
+ * screen never had a file to show — the size check runs before anything
+ * uploads — so Figma draws the plain F recipe: status icon + title + subtitle
+ * centred in the full height, one CTA pinned near the bottom. No media slot,
+ * no card, nothing to reuse from the capture component.
+ */
+export const DigitalIdUploadFileTooLargeScreen = forwardRef<
+  HTMLDivElement,
+  DigitalIdUploadFileTooLargeScreenProps
+>(
+  (
+    {
+      strings,
+      screenId = 'digital-id-upload-file-too-large',
+      showHeader = false,
+      showFooter = false,
+      overrides,
+      onAction,
+      ...shell
+    },
+    ref,
+  ) => (
+    <PrizmaResultScreen
+      ref={ref}
+      status="error"
+      title={strings.fileTooLarge.title}
+      subtitle={strings.fileTooLarge.subtitle}
+      ctaLabel={strings.fileTooLarge.ctaLabel}
+      verifiedLabel={strings.verifiedLabel}
+      navLabel={strings.navLabel}
+      showHeader={showHeader}
+      showFooter={showFooter}
+      screenId={screenId}
+      overrides={overrides}
+      onAction={onAction}
+      {...shell}
+    />
+  ),
+);
+DigitalIdUploadFileTooLargeScreen.displayName = 'DigitalIdUploadFileTooLargeScreen';
+
+export default DigitalIdUploadFileTooLargeScreen;

package/src/DigitalIdUploadReviewScreen.tsx

@@ -0,0 +1,119 @@
+import React, { forwardRef } from 'react';
+import { PrizmaCaptureDigitalId } from '@incodetech/prizma-core-web/capture-digital-id';
+import { PrizmaReviewScreen, type PrizmaReviewScreenProps } from './ReviewScreen';
+import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
+import type {
+  DigitalIdUploadConfirmStage,
+  DigitalIdUploadStrings,
+} from './DigitalIdUploadStrings';
+import './ScreenLayout.css';
+
+export interface DigitalIdUploadReviewScreenProps
+  extends Omit<
+    PrizmaReviewScreenProps,
+    | 'title'
+    | 'subtitle'
+    | 'successTitle'
+    | 'analyzingLabel'
+    | 'primaryLabel'
+    | 'secondaryLabel'
+    | 'verifiedLabel'
+    | 'children'
+    | 'stage'
+  > {
+  /** Module copy — this screen reads the `review` slice. */
+  strings: DigitalIdUploadStrings;
+  /** Which stage of the confirm flow to render. Default `review`. */
+  stage?: DigitalIdUploadConfirmStage;
+  /** The uploaded file's name, shown under the card on `review` only. Not
+   *  copy — it is runtime data from the picker, so it stays out of
+   *  `strings` (same contract as `DocumentCaptureConfirmUploadScreen`). */
+  filename?: string;
+  /** Loading-bar progress on `analyzing`, 0–100. */
+  progress?: number;
+  screenId?: string;
+  overrides?: PrizmaScreenOverrides;
+  onAction?: PrizmaScreenActionHandler;
+}
+
+/**
+ * Digital ID Upload — review / analyzing / success, built on the
+ * `PrizmaReviewScreen` archetype (GUIDELINES.md §6-H). Figma: `Upload Digital
+ * ID` file (wxFsHRvllern4VnjRqM4JO), "Web Happy Path - Light Mode" section —
+ * `Review Document` / `Analyzing` / `Success` (nodes 25351:14725/6/7).
+ *
+ * The media stage is Core's `PrizmaCaptureDigitalId` across all three stages
+ * — its own state enum (`review` / `analyzing` / `success`) maps directly
+ * onto the archetype's stage axis, so it already owns the border treatment
+ * (neutral on review, green 4px on analyzing/success), the scan-flash sweep
+ * and the filename row. Nothing is hand-built here, unlike
+ * `DocumentCaptureConfirmUploadScreen`'s bespoke file-card — Core ships a
+ * purpose-built component for this module.
+ *
+ * Header/footer visibility is genuinely per-stage in this Figma (logo nav +
+ * verified tag show on `review`, both are absent on `analyzing` and
+ * `success`) — not a layout choice this file invents, just the existing
+ * `showHeader`/`showFooter` chrome knobs (owner rule 2026-08-18: header and
+ * footer are independently controlled) applied per stage.
+ *
+ * Always opts into the archetype's `centeredWhenNoNav` — it only takes effect
+ * while the nav is hidden (`analyzing`/`success` here), where this Figma
+ * draws the header + media as one group centred with equal space above and
+ * below it, not a pinned header (see ReviewScreen.tsx for the mechanics).
+ * `review` always shows its own nav, so the flag is a no-op there, and the
+ * default `false` leaves Document Capture's existing analyzing/success
+ * screens byte-for-byte unchanged (neither ever hides the nav here).
+ *
+ * GAP (report, not workaround — README rule 2): Figma's `Success` section
+ * also shows a subtitle ("Let's continue") under the success title, but the
+ * shared `PrizmaReviewScreen` archetype only renders a subtitle on
+ * `stage="review"` — every other current consumer's success state has none.
+ * Left unset here pending an owner call on whether to extend the shared
+ * archetype with a `successSubtitle` slot.
+ */
+export const DigitalIdUploadReviewScreen = forwardRef<
+  HTMLDivElement,
+  DigitalIdUploadReviewScreenProps
+>(
+  (
+    {
+      strings,
+      stage = 'review',
+      filename,
+      progress = 45,
+      showHeader = stage === 'review',
+      showFooter = stage === 'review',
+      screenId = `digital-id-upload-${stage}`,
+      overrides,
+      onAction,
+      ...shell
+    },
+    ref,
+  ) => (
+    <PrizmaReviewScreen
+      ref={ref}
+      stage={stage}
+      title={strings.review.title}
+      subtitle={strings.review.subtitle}
+      successTitle={strings.review.successTitle}
+      analyzingLabel={strings.review.analyzingLabel}
+      centeredWhenNoNav
+      progress={progress}
+      primaryLabel={strings.review.ctaLabel}
+      secondaryLabel={strings.review.replaceLabel}
+      verifiedLabel={strings.verifiedLabel}
+      navLabel={strings.navLabel}
+      showHeader={showHeader}
+      showFooter={showFooter}
+      screenId={screenId}
+      overrides={overrides}
+      onAction={onAction}
+      {...shell}
+    >
+      <PrizmaCaptureDigitalId state={stage} filename={filename} />
+    </PrizmaReviewScreen>
+  ),
+);
+DigitalIdUploadReviewScreen.displayName = 'DigitalIdUploadReviewScreen';
+
+export default DigitalIdUploadReviewScreen;

package/src/DigitalIdUploadStrings.ts

@@ -0,0 +1,88 @@
+// Digital ID Upload module — copy contract.
+//
+// Every Digital ID Upload screen receives the SAME `strings:
+// DigitalIdUploadStrings` object (rule: all copy via props, no hardcoded
+// English — GUIDELINES.md §9).
+//
+// Authoritative screens: the "Web Happy Path - Light Mode" purple section of
+// the Upload Digital ID Figma file (wxFsHRvllern4VnjRqM4JO, node 25351:14721)
+// — covers `tutorial` and the `review` / `analyzing` / `success` stages of
+// the confirm flow — plus TWO separate `Errors` sections: node 25874:11955
+// (`ID type is not accepted`) and node 26083:3981 (`File Limit Error`, "File
+// is too large"). Three frames of the happy-path section are NOT part of
+// this contract: `1-1-1-how to verify` (a verification-method chooser shared
+// with ID Capture — see IdCaptureDocumentSelectionScreen.tsx, which is one
+// row short of this Figma's version), a native iOS file-browser frame (OS
+// chrome, DEVIATIONS.md #DC-20 precedent), and `1-18-1-id-hold-on` (ID
+// Capture's own server-side-wait screen — dropped from this module by
+// product decision, not a gap to fill).
+
+/** The three stages the confirm flow's screen shares — matches
+ *  `PrizmaReviewScreen`'s own `PrizmaReviewStage` (ReviewScreen.tsx). Kept as
+ *  a separate module-scoped type rather than importing it, same convention as
+ *  `DocumentCaptureConfirmStage` (DocumentCaptureStrings.ts). */
+export type DigitalIdUploadConfirmStage = 'review' | 'analyzing' | 'success';
+
+export interface DigitalIdUploadStrings {
+  /** Accessible name for the logo nav region (i18n — no baked-in English). */
+  navLabel?: string;
+  /** "verified by" attribution copy for the footer tag. */
+  verifiedLabel: string;
+
+  /** `Tutorial Screen` (node 25351:14722). */
+  tutorial: {
+    title: string;
+    subtitle?: string;
+    /** "Upload PDF" */
+    ctaLabel: string;
+  };
+
+  /** `Review Document` / `Analyzing` / `Success` (nodes
+   *  25351:14725/14726/14727) — one screen, three stages. */
+  review: {
+    /** `review` title ("Review document"). */
+    title: string;
+    /** `review` description. Figma draws no subtitle on `analyzing` or
+     *  `success` — the shared `PrizmaReviewScreen` archetype already only
+     *  shows one on `review`, so this needs no per-stage handling here. */
+    subtitle?: string;
+    /** Loading-bar caption on `analyzing` ("Analyzing.."). */
+    analyzingLabel: string;
+    /** H2 on `success` ("Successfully processed!"). */
+    successTitle: string;
+    /** Secondary CTA on `review` ("Replace file"). */
+    replaceLabel: string;
+    /** Primary CTA on `review` / `success` ("Continue"). */
+    ctaLabel: string;
+  };
+
+  /** `Errors` section, `Error` frame (node 25874:11957) — the uploaded file
+   *  itself was rejected (wrong document type). Built on the SAME
+   *  `PrizmaReviewScreen` archetype as `review`, stage `"error"`: the card
+   *  reuses `PrizmaCaptureDigitalId state="error"` (red 4px border), not a
+   *  generic archetype-F verdict screen (DigitalIdUploadErrorScreen.tsx). */
+  error: {
+    /** "ID type is not accepted" */
+    title: string;
+    /** "Please try scanning a different document" */
+    subtitle?: string;
+    /** "Scan your ID" */
+    ctaLabel: string;
+  };
+
+  /** `Errors` section, `File Limit Error` frame (node 26083:3981) — the file
+   *  was never uploaded at all (client-side size check), so there is no
+   *  rejected document to show. Built on Archetype F (`PrizmaResultScreen`,
+   *  ResultScreen.tsx) rather than the review archetype `error` uses above —
+   *  Figma centres the status + title + subtitle in the full available
+   *  height with no media stage at all, exactly F's shape, not H's
+   *  header-above-a-card one (DigitalIdUploadFileTooLargeScreen.tsx). */
+  fileTooLarge: {
+    /** "File is too large" */
+    title: string;
+    /** "The selected file is larger than 5 MB, please upload a smaller one" */
+    subtitle?: string;
+    /** "Choose another file" */
+    ctaLabel: string;
+  };
+}

package/src/DigitalIdUploadTutorialScreen.tsx

@@ -0,0 +1,59 @@
+import React, { forwardRef } from 'react';
+import { PrizmaCaptureDigitalId } from '@incodetech/prizma-core-web/capture-digital-id';
+import { PrizmaTutorialScreen, type PrizmaTutorialScreenProps } from './TutorialScreen';
+import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
+import type { DigitalIdUploadStrings } from './DigitalIdUploadStrings';
+import './ScreenLayout.css';
+
+export interface DigitalIdUploadTutorialScreenProps
+  extends Omit<
+    PrizmaTutorialScreenProps,
+    'title' | 'subtitle' | 'ctaLabel' | 'illustration' | 'verifiedLabel' | 'navLabel'
+  > {
+  /** Module copy — this screen reads the `tutorial` slice (+ shared labels). */
+  strings: DigitalIdUploadStrings;
+  screenId?: string;
+  overrides?: PrizmaScreenOverrides;
+  onAction?: PrizmaScreenActionHandler;
+}
+
+/**
+ * Digital ID Upload — tutorial, built on the `PrizmaTutorialScreen` archetype
+ * (GUIDELINES.md §6-A). Figma: `Upload Digital ID` file
+ * (wxFsHRvllern4VnjRqM4JO), "Web Happy Path - Light Mode" section, `Tutorial
+ * Screen` (node 25351:14722).
+ *
+ * The illustration slot is Core's own `PrizmaCaptureDigitalId` in its
+ * `tutorial` state — the Figma file names this exact instance "Capture /
+ * Digital ID" (node 26161:10686, Figma description: "Incode specific
+ * component for Digital ID module experience"), the same managed component
+ * already shipped as `core/platforms/web/src/CaptureDigitalId.tsx`. No module
+ * illustration is drawn here — the component owns its own tutorial artwork
+ * (`PrizmaIllustrationDigitalId`).
+ */
+export const DigitalIdUploadTutorialScreen = forwardRef<
+  HTMLDivElement,
+  DigitalIdUploadTutorialScreenProps
+>(
+  (
+    { strings, screenId = 'digital-id-upload-tutorial', overrides, onAction, ...shell },
+    ref,
+  ) => (
+    <PrizmaTutorialScreen
+      ref={ref}
+      title={strings.tutorial.title}
+      subtitle={strings.tutorial.subtitle}
+      ctaLabel={strings.tutorial.ctaLabel}
+      illustration={<PrizmaCaptureDigitalId state="tutorial" />}
+      verifiedLabel={strings.verifiedLabel}
+      navLabel={strings.navLabel}
+      screenId={screenId}
+      overrides={overrides}
+      onAction={onAction}
+      {...shell}
+    />
+  ),
+);
+DigitalIdUploadTutorialScreen.displayName = 'DigitalIdUploadTutorialScreen';
+
+export default DigitalIdUploadTutorialScreen;

package/src/DocumentCaptureIllustration.tsx

@@ -7,7 +7,7 @@ import './DocumentCaptureLayout.css';
  *
  * WHY IT LIVES IN THE MODULE LAYER: `prizma-core-web` ships
  * `PrizmaIllustrationSelfie`, `…IdTutorial`, `…IdIntro`, `…IdFlip`,
- * `…IdHint`, `…IdFeedback`, `…NfcScan`, `…NfcIssue`, `…Geolocation`,
+ * `…IdHint`, `…IdFeedback`, `…NfcScan`, `…Geolocation`,
  * `…DigitalId` and `…Avatar` — there is NO document / proof-of-address
  * illustration. GUIDELINES.md §10 is the standing asset rule for that gap
  * ("Illustrations…: inline SVG React components (Figma-sourced), tintable via

package/src/EkybCountryScreen.tsx

@@ -1,5 +1,6 @@
 import React, { forwardRef } from 'react';
 import { PrizmaDropdown } from '@incodetech/prizma-core-web/dropdown';
+import { PrizmaCountryFlag } from '@incodetech/prizma-core-web/combined';
 import { PrizmaFormScreen, type PrizmaFormScreenProps } from './FormScreen';
 import type { PrizmaScreenActionHandler, PrizmaScreenOverrides } from './types';
 import type { EkybCountryState, EkybOption, EkybStrings } from './EkybStrings';
@@ -55,12 +56,12 @@ export interface EkybCountryScreenProps
  *    live interaction) — the same mechanism Phone Input's `countryCode` and
  *    CURP's `Gene.dropdown` sections use. The search bar Figma draws inside the
  *    menu is Core's own `searchable`.
- * 3. Menu rows and the closed field read the same "🇺🇸 United States": flag
- *    and country name, no dial code. Figma 5707:54174 draws the rows with
- *    Phone Input's "+1" prefixes, dropped by the owner (Elena, 2026-09-28)
- *    because a country of registration has no phone prefix. The flag travels
- *    inside the label text because Core still ships no country-flag primitive
- *    (#PI-3).
+ * 3. Menu rows and the closed field read the same flag + "United States",
+ *    no dial code. Figma 5707:54174 draws the rows with Phone Input's "+1"
+ *    prefixes, dropped by the owner (Elena, 2026-09-28) because a country of
+ *    registration has no phone prefix. The flag is Core's raster in the
+ *    dropdown's leading slot, not an emoji in the label (Elena, 2026-10-23;
+ *    #PI-3, the WatchlistBusinessFormScreen precedent).
  *
  * This page is the only eKYB form page with NO "Back" secondary and NO Stepper —
  * it is step 0, before the three-step wizard starts.
@@ -135,6 +136,22 @@ export const EkybCountryScreen = forwardRef<HTMLDivElement, EkybCountryScreenPro
           clearSearchLabel={copy.clearSearchLabel}
           /* The `dropdown` section IS the open-menu spec state. */
           forceOpen={state === 'dropdown'}
+          /* Core's canonical flag raster in the closed field and every menu
+             row (see note 3). A country outside the bank falls back to its
+             `flag` emoji. */
+          renderLeading={(option) => {
+            const match = countries.find((c) => c.value === option.value);
+            return match ? (
+              <PrizmaCountryFlag
+                country={{
+                  code: match.value,
+                  name: match.label,
+                  dialCode: '',
+                  flag: match.flag ?? '',
+                }}
+              />
+            ) : null;
+          }}
         />
       </PrizmaFormScreen>
     );

package/src/EkybStrings.ts

@@ -98,8 +98,13 @@ export interface EkybOption {
   label: string;
   /** Compact face for the CLOSED field when it differs from the menu row —
    *  Core's own `PrizmaDropdownOption.fieldLabel`. The eKYB country list
-   *  does not need it: rows and field both read "🇺🇸 United States". */
+   *  does not need it: rows and field both read "United States" after the
+   *  flag. */
   fieldLabel?: string;
+  /** Country menus only: the emoji fallback for a `value` outside Core's
+   *  flag raster bank. The country screen draws the bank's flag by `value`,
+   *  so this never travels inside `label`. */
+  flag?: string;
 }
 
 /** The values the business-identity page carries. Runtime data, never copy. */

package/src/ErrorScreensScreen.tsx

@@ -38,7 +38,7 @@ export interface ErrorScreensScreenProps
  * Error screens — the session-level failures, built on the Result archetype
  * (GUIDELINES.md §6-F, `PrizmaResultScreen`).
  *
- * ONE screen for all three generic sections. They draw the identical skeleton —
+ * ONE screen for all four generic sections. They draw the identical skeleton —
  * a centred mark + title + supporting line over a CTA band — and differ only in
  * copy, in which mark leads, and in what the band carries:
  *
@@ -46,8 +46,11 @@ export interface ErrorScreensScreenProps
  * - `noConnection`       — Wi-Fi glyph, "Refresh"
  * - `unsupportedBrowser` — canonical negative mark, the session URL above
  *                          "Copy link", with "Continue anyways" under it
+ * - `somethingWentWrong` — canonical negative mark, "Try again" when the copy
+ *                          carries a CTA, "Quit process" under it when it
+ *                          carries a quit label; a dead end when it has neither
  *
- * Chrome is CONSTANT. All three frames are drawn without the logo header and
+ * Chrome is CONSTANT. All the frames are drawn without the logo header and
  * without the verified tag; both are kept here, because the owner rule of
  * 2026-08-18 (#F-30, #F-34) makes the chrome the same on every screen so
  * nothing shifts between states, and every module's connectivity screen must
@@ -91,11 +94,19 @@ export const ErrorScreensScreen = forwardRef<HTMLDivElement, ErrorScreensScreenP
   ) => {
     const unsupported = variant === 'unsupportedBrowser';
     const noConnection = variant === 'noConnection';
+    const generic = variant === 'somethingWentWrong';
     const copy = unsupported
       ? strings.unsupportedBrowser
       : noConnection
         ? strings.noConnection
-        : strings.sessionExpired;
+        : generic
+          ? strings.somethingWentWrong
+          : strings.sessionExpired;
+    const linkLabel = unsupported
+      ? strings.unsupportedBrowser.continueLabel
+      : generic
+        ? strings.somethingWentWrong.quitLabel
+        : undefined;
 
     return (
       <PrizmaResultScreen
@@ -133,7 +144,7 @@ export const ErrorScreensScreen = forwardRef<HTMLDivElement, ErrorScreensScreenP
             : undefined
         }
         ctaLabel={copy.ctaLabel}
-        linkLabel={unsupported ? strings.unsupportedBrowser.continueLabel : undefined}
+        linkLabel={linkLabel}
         verifiedLabel={strings.verifiedLabel}
         navLabel={strings.navLabel}
         screenId={screenId}

package/src/ErrorScreensStrings.ts

@@ -6,19 +6,27 @@
 //   214:3357 Geolocation.error.noNetwork      → `noConnection`
 //   240:154  Error screen - Unsupported browser → `unsupportedBrowser`
 //
-// The three failures that belong to the SESSION rather than to any module: the
-// link has expired, the network went away, the browser cannot run the SDK.
-// Every module can hit all three, which is why they are drawn once in the
-// generic file — a user who sees three different "no internet" screens in one
-// journey reads them as three different products.
+// plus the one failure every module draws for itself and the file never did:
+//
+//   —        <module>.error "Something went wrong" → `somethingWentWrong`
+//
+// The failures that belong to the SESSION rather than to any module: the link
+// has expired, the network went away, the browser cannot run the SDK, the
+// server said no for a reason the user cannot act on. Every module can hit all
+// four, which is why they are recorded once in the generic family — a user who
+// sees three different "no internet" screens in one journey reads them as three
+// different products.
 //
 // `noConnection` is deliberately the same screen every module already ships
 // (`FaceCaptureNoConnectionScreen`, `IdCaptureNoConnectionScreen`,
-// `DocumentCaptureNoConnectionScreen`, `GeolocationErrorScreen`'s `noNetwork`).
-// The generic entry is where the shape is DOCUMENTED; the module copies stay
-// put until someone retires them deliberately, because deleting four exported
-// components to save one screen is a breaking change for every host that
-// imports them. Flagged for the owner.
+// `DocumentCaptureNoConnectionScreen`, `GeolocationErrorScreen`'s `noNetwork`,
+// Phone Input's and Video Selfie's `noConnection`). `somethingWentWrong` is the
+// same screen eKYC, eKYB, Forms, Email Input, Phone Input, Certificate
+// Issuance, both signatures and Video Selfie already ship. The generic entry is
+// where the shape and the copy are DOCUMENTED; the module copies stay put until
+// someone retires them deliberately, because deleting exported components to
+// save one screen is a breaking change for every host that imports them.
+// Flagged for the owner (DEVIATIONS #GEN-7, #GEN-18).
 //
 // The family has no flow of its own: each of these is entered from wherever the
 // session broke and exits to a retry or to nothing. Core Lab lists it as a
@@ -27,15 +35,17 @@
 // No hardcoded English anywhere in a screen: every visible string arrives here.
 
 /**
- * The three sections.
+ * The four sections.
  * - `sessionExpired`     — the link is dead; the user must go back to the provider
  * - `noConnection`       — the network went away; retry when it returns
  * - `unsupportedBrowser` — the SDK cannot run here; copy the link and move
+ * - `somethingWentWrong` — the generic failure; try again, or nothing, or quit
  */
 export type ErrorScreensVariant =
   | 'sessionExpired'
   | 'noConnection'
-  | 'unsupportedBrowser';
+  | 'unsupportedBrowser'
+  | 'somethingWentWrong';
 
 export interface ErrorScreensCopy {
   title: string;
@@ -63,4 +73,19 @@ export interface ErrorScreensStrings {
     /** Snackbar copy after the link is copied — the frame's second state. */
     copiedLabel: string;
   };
+
+  /**
+   * The generic failure. Three ways the modules fill it, all the same screen:
+   * `ctaLabel` "Try again" (eKYC, eKYB, Forms, Email Input);
+   * no `ctaLabel`, a dead end (Certificate Issuance, Qualified Signature);
+   * `ctaLabel` plus `quitLabel`, the way out under the retry (Video Selfie).
+   * Phone Input's `unknown` fills it with "Continue" instead, because a retry
+   * may not be possible there (owner, 2026-10-09) — the CTA is the module's
+   * call; the shape and the title are what the family fixes.
+   * The title never carries an ellipsis — a failure is not in progress.
+   */
+  somethingWentWrong: ErrorScreensCopy & {
+    /** Tertiary link under the CTA — "Quit process". Omit for no way out. */
+    quitLabel?: string;
+  };
 }