@redacto.io/consent-sdk-react 10.0.0-beta.1 → 10.0.0-beta.11

package/.turbo/turbo-build.log

@@ -7,16 +7,16 @@
 CLI Cleaning output folder
 ESM Build start
 CJS Build start
-CJS dist/index.js          520.79 KB
-CJS dist/privacy-center.js 2.24 MB
-CJS ⚡️ Build success in 124ms
-ESM dist/index.mjs          506.34 KB
+CJS dist/index.js          516.41 KB
+CJS dist/privacy-center.js 2.21 MB
+CJS ⚡️ Build success in 179ms
 ESM dist/chunk-6A665OPR.mjs 841.00 B
-ESM dist/privacy-center.mjs 2.20 MB
-ESM ⚡️ Build success in 124ms
+ESM dist/index.mjs          501.90 KB
+ESM dist/privacy-center.mjs 2.17 MB
+ESM ⚡️ Build success in 184ms
 DTS Build start
-DTS ⚡️ Build success in 2664ms
-DTS dist/index.d.mts          8.27 KB
-DTS dist/privacy-center.d.mts 33.25 KB
-DTS dist/index.d.ts           8.27 KB
-DTS dist/privacy-center.d.ts  33.25 KB
+DTS ⚡️ Build success in 3448ms
+DTS dist/index.d.mts          8.42 KB
+DTS dist/privacy-center.d.mts 33.31 KB
+DTS dist/index.d.ts           8.42 KB
+DTS dist/privacy-center.d.ts  33.31 KB

package/CHANGELOG.md

@@ -1,5 +1,114 @@
 # @redacto.io/consent-sdk-react
 
+## 10.0.0-beta.11
+
+### Minor Changes
+
+- 43ea923: route the standard notice-content fetch through the Go ledger (ledgerBaseUrl); the magic-link flow (applicationId) and sandbox sessions stay on the consent server. Per-language audio uses the ledger when configured, except sandbox sessions, which the ledger's X-Consent-Token auth does not support
+
+  drop the separate ledger check-consent round-trip: the notice read already returns the per-principal reconsent overlay (`purpose_selections` / `reconsent_required`) inline, so the banner consumes it directly. This also fixes reconsent on a republished notice, which the standalone check-consent overlay could not detect (no notice-version awareness), and makes `validate_against` apply to the overlay
+
+### Patch Changes
+
+- f4b3cad: Inline notice read: use the authenticated `notices/{notice_uuid}` endpoint whenever an access token is available, so the embedded widget works against the Go consent ledger.
+
+  The inline widget read the notice from `notices/get-notice/{notice_uuid}` — a tokenless endpoint the consent server serves and the ledger does not. Pointing `baseUrl` at the ledger therefore failed with 404 `Resource not found` even though the notice existed there, and the path is compiled into the SDK so no `baseUrl` change could fix it.
+
+  The inline widget already carries the access token it needs to submit consent. When that token is present the notice now comes from `notices/{notice_uuid}` with an `Authorization: Bearer` header — the same endpoint the modal (`RedactoNoticeConsent`) has always used, served by both the consent server and the ledger, and the one that returns the caller's `purpose_selections` / `reconsent_required` overlay and 409 `CONSENT_ALREADY_PROVIDED`. Without a token the legacy tokenless path is unchanged, so the OTP-gated assisted flow and any anonymous embed keep working against the consent server.
+
+  Because the token now selects the endpoint, a token that arrives after the widget mounts also has to re-read the notice: `InlineController.updateToken()` refetches when the first read was tokenless, so the unauthenticated content can no longer be auto-submitted. A later token refresh does not refetch, which would discard in-progress selections.
+
+  A token arriving while the first read is still in flight leaves two reads racing, so the notice read is now generation-guarded in `InlineController` — a superseded tokenless response can no longer replace the authenticated content, reset the selections under the user, or auto-submit against the newly stored token. `hasAlreadyConsented` is also cleared at the start of each read, so a 409 for one principal cannot blank the widget for the next one.
+
+  Also in this change: `Accept-Language` is sent on the tokenless read too (it was only set on the authenticated path in `consent-sdk-js` and `consent-sdk-react`, so `language` was ignored for anonymous callers), and the `consent-sdk-react` notice fetch is now abort-guarded like `consent-sdk-react-native`, so the tokenless request cannot resolve last and overwrite the authenticated one.
+
+- udpate the beta version with latest changes
+
+## 10.0.0-beta.10
+
+### Patch Changes
+
+- refactor(privacy-center): remove purpose revocability, keep the revoke warning message (CON-I1041). Removes only the non-revocable withdrawal-blocking behaviour from feature #490: the Privacy Center no longer consumes a per-purpose `revocable` flag, no longer disables the withdraw control for non-revocable purposes, and no longer maps the `purpose_not_revocable` backend error to a toast. `PurposeItem` drops `revocable`. The per-purpose custom `revoke_warning_message` shown in the revoke modal is **retained** (`PurposeItem` keeps `revoke_warning_message`). Paired with the consent-server and redfront changes; revocability moves to the notice level.
+
+## 10.0.0-beta.9
+
+### Patch Changes
+
+- e44b1a3: Privacy Center: fix the DSAR request form showing "No products available" against the legacy Python backend. The request-form product picker is now sourced from `user-consents` on **both** backends — the Go ledger's `/public/.../user-consents` when `ledgerBaseUrl` is configured, Python's `/dsar/privacy-center/user-consents` otherwise (the same read the Manage Consent view already used in both modes) — instead of being skipped entirely without a ledger, which left the picker dependent on `form/data` product groups that Python no longer emits.
+
+  Two related gaps are closed: a successful-but-empty `user-consents` response no longer overwrites the product groups `form/data` did supply, and a backend that returns only the legacy flat `purposes` list now renders those purposes under a single "Your data" group instead of the empty state. Cases raised from that fallback group are submitted without a `product_uuid` anchor, matching the pre-grouping org-level case shape.
+
+- source Privacy Center DSAR product picker from user-consents on both backends
+
+## 10.0.0-beta.8
+
+### Patch Changes
+
+- fix(consent-sdk): record language on withdraw/regrant + localize RN activity log
+
+## 10.0.0-beta.7
+
+### Minor Changes
+
+- feat(consent-sdk-react): show User ID as primary field in shared-contact profile picker
+
+## 10.0.0-beta.6
+
+### Patch Changes
+
+- minor bug fix in beta version
+
+## 10.0.0-beta.5
+
+### Major Changes
+
+- M3 Version
+
+### Minor Changes
+
+- 1a11423: RedactoNoticeAssisted: add `ledgerBaseUrl` support with the standard fallback, for parity with RedactoNoticeConsent and RedactoNoticeConsentInline. When `ledgerBaseUrl` is set, the consent write is routed through `ledgerBaseUrl || baseUrl || BASE_URL` (only `submit-consent` moves to the ledger; the public notice / OTP / TTS endpoints stay on `baseUrl`). After OTP verification the widget also runs a ledger `check-consent` read and, if the principal has already fully consented, hands off via `onComplete` without writing a duplicate consent event — the ledger equivalent of the legacy Python 409 `CONSENT_ALREADY_PROVIDED`, which no longer fires once consent records live in the ledger. Without `ledgerBaseUrl` the behavior is unchanged (write to the legacy consent server, reactive 409-as-success). The ledger `check-consent` network read is now shared across all three notice components.
+
+### Patch Changes
+
+- 1a11423: RedactoNoticeConsentInline: detect already-consented principals via the Go ledger after the consent cutover. Previously the embedded widget only recognized an already-consented user through Python's 409 `CONSENT_ALREADY_PROVIDED` on `get-notice`; once consent records move to the ledger, Python stops returning that 409, so the widget would re-render the notice and could auto-submit a duplicate consent. When `ledgerBaseUrl` is configured (and outside the magic-link `specific_uuid` flow), the widget now runs the same ledger `check-consent` read the banner uses and short-circuits to the already-consented state, gating auto-submit until that read settles. Without `ledgerBaseUrl` the legacy Python-409 path is unchanged. The ledger `check-consent` read is now shared between `RedactoNoticeConsent` and `RedactoNoticeConsentInline`.
+
+## 10.0.0-beta.4
+
+### Patch Changes
+
+- 05b3452: fix(privacy-center): make the org logo visible and even in the header
+
+  PCAvatar applied its coloured fill to the `<img>` branch as well as the initials branch. Since every
+  call site passes `color="info"` and branding maps `--pc-info` to the org's own primary colour, a
+  brand-coloured logo on a transparent background was painted onto a disc of the same colour and
+  disappeared. Image avatars now render with `object-fit: contain` (no more stretching) and
+  `box-sizing: border-box` (unchanged 24/32/48px box), and fall back to initials when the logo fails to
+  load instead of showing an empty coloured circle. Standalone brand marks get a neutral surface and a
+  hairline ring; a new `framed={false}` opts out of that chrome when a parent control already draws it.
+
+  The header's logo menu is now a real navbar control: it uses the same size token, ring, background
+  and hover as the notification bell (`--pc-navbar-actions-control-height`, 32px circle), instead of an
+  ad-hoc transparent pill wrapping a smaller 24px avatar. That removes the size mismatch next to the
+  bell and the concentric rings its brand-tinted hover glow used to stack around the avatar's own ring.
+
+- 31785c6: Remove Bhojpuri (`bho`) from the language selectors and bundled translations. The backend no longer
+  supports Bhojpuri (it is not a DPDPA-mandated language), so it is dropped from the Privacy Center and
+  Notice language lists to match the supported set. Any consumer still passing `bho` falls back to the
+  default language.
+- Privacy Center: 400 error when DP changes language to Bhojpuri
+
+## 10.0.0-beta.3
+
+### Minor Changes
+
+- show org_user_id to distinguish shared-contact profiles
+
+## 10.0.0-beta.2
+
+### Minor Changes
+
+- add revokable and non revokable purposes
+
 ## 10.0.0-beta.1
 
 ### Major Changes

package/README.md

@@ -117,6 +117,80 @@ npm install @tanstack/react-query @tanstack/react-table \
 
 If you only use `RedactoNoticeConsent` or `RedactoNoticeConsentInline`, these peers are not needed.
 
+## Sandbox Mode (No Backend Required)
+
+Sandbox mode lets you build and test a full consent PoC — **notice → Privacy Center → DSAR** — straight from your app, with **no backend and no token minting**. Instead of your server generating a JWT, you paste a **static sandbox token** into the SDK. Everything you create is recorded as test data, isolated from your live records.
+
+Going live is a config swap, not a rewrite: drop the sandbox props and pass a real JWT (see [Backend Server Setup](#backend-server-setup)).
+
+### 1. Get your sandbox credentials
+
+In the **Redacto Dashboard → API Keys → Sandbox** tab, copy:
+
+- your **Sandbox token** (a static string; it never expires and needs no refresh)
+- your **Organization ID** and **Workspace ID** (shown under *Workspace identifiers* on the same page)
+
+### 2. Collect consent
+
+Pass the sandbox `token`, org/workspace, and a test identity (`email`, `mobile`, or `ucic`). No `accessToken` is needed:
+
+```tsx
+import { RedactoNoticeConsent } from "@redacto.io/consent-sdk-react";
+
+<RedactoNoticeConsent
+  noticeId={NOTICE_UUID}
+  token={SANDBOX_TOKEN}
+  organisationUuid={ORG_UUID}
+  workspaceUuid={WORKSPACE_UUID}
+  email="test.user@example.com" // or `mobile`, or `ucic`
+  onAccept={() => console.log("consent recorded (test)")}
+  onDecline={() => {}}
+/>;
+```
+
+### 3. Manage consent & raise a DSAR
+
+Point the Privacy Center at the same sandbox token and test identity. The same test user can now review the consent from step 2, withdraw it, and file a DSAR — end to end, all as test data:
+
+```tsx
+import { RedactoPrivacyCenter } from "@redacto.io/consent-sdk-react/privacy-center";
+
+<RedactoPrivacyCenter
+  token={SANDBOX_TOKEN}
+  organisationUuid={ORG_UUID}
+  workspaceUuid={WORKSPACE_UUID}
+  email="test.user@example.com" // or `mobile`, or `ucic`
+  slug="acme-co"
+  onError={(error) => {
+    console.error(error);
+    return false;
+  }}
+/>;
+```
+
+### Sandbox props
+
+| Prop                        | Required     | Description                                                                        |
+| --------------------------- | ------------ | --------------------------------------------------------------------------------- |
+| `token`                     | Yes          | Static sandbox token from the Dashboard. Its presence activates sandbox mode.      |
+| `organisationUuid`          | Yes          | Organization ID from the Dashboard.                                               |
+| `workspaceUuid`             | Yes          | Workspace ID from the Dashboard.                                                  |
+| `email` / `mobile` / `ucic` | One required | The test subject. Precedence when more than one is set: `ucic` > `email` > `mobile`. |
+
+`RedactoPrivacyCenter` takes the same sandbox props — `token`, `organisationUuid`, `workspaceUuid`, and `email` / `mobile` / `ucic`.
+
+### How it works
+
+- The SDK sends the sandbox token as an `X-Consent-Token` header and the test identity inside each request (query params on reads, body on writes) — no JWT decode, no token refresh (a `401` fails fast).
+- The server records everything under `environment=test`, namespaced so sandbox data never mixes with — or reads — your live records.
+- Sandbox always talks to the consent server; it never routes to the Go ledger.
+
+### Going live
+
+Sandbox and production use the same components. To ship, remove the sandbox props and pass a real `accessToken` / `refreshToken` (JWT) minted by your backend — see [Backend Server Setup](#backend-server-setup) below. New records are then written as `environment=live`.
+
+> Sandbox is available on `RedactoNoticeConsent` and `RedactoPrivacyCenter`. The inline (`RedactoNoticeConsentInline`) and assisted (`RedactoNoticeAssisted`) widgets are JWT/OTP-only.
+
 ### Backend Server Setup
 
 Before using the SDK components, you need to set up backend server endpoints that generate access tokens by calling Redacto's API. Your server should implement the following endpoints:
@@ -249,6 +323,7 @@ A modal popup component for consent collection. Displays a full-screen modal wit
 | `accessToken`     | `string`                 | Yes      | -       | Authentication token for API calls  |
 | `refreshToken`    | `string`                 | Yes      | -       | Refresh token for token renewal     |
 | `baseUrl`         | `string`                 | No       | -       | Base URL for the consent API        |
+| `ledgerBaseUrl`   | `string`                 | No       | -       | Go ledger base URL. When set, consent writes and prior-consent checks route through the ledger (falls back: ledger → baseUrl → default). Omit to keep the legacy consent-server path. |
 | `blockUI`         | `boolean`                | No       | `true`  | Whether to block UI interaction     |
 | `language`        | `string`                 | No       | `"en"`  | Language code                       |
 | `settings`        | `object`                 | No       | -       | Custom styling options              |
@@ -335,6 +410,7 @@ The component automatically submits consent when all of the following conditions
 | `accessToken`        | `string`                     | No       | -       | Authentication token                   |
 | `refreshToken`       | `string`                     | No       | -       | Refresh token                          |
 | `baseUrl`            | `string`                     | No       | -       | Base URL for the consent API           |
+| `ledgerBaseUrl`      | `string`                     | No       | -       | Go ledger base URL. When set, consent writes and already-consented checks route through the ledger. Omit for legacy behavior. |
 | `language`           | `string`                     | No       | `"en"`  | Language code                          |
 | `settings`           | `object`                     | No       | -       | Custom styling options                 |
 | `applicationId`      | `string`                     | No       | -       | Application-specific UUID              |
@@ -365,6 +441,7 @@ A modal, agent-assisted consent widget for collecting consent from an end-user w
 | `workspaceUuid`    | `string`     | Yes      | -                        | Workspace UUID (path segment of the public notice endpoint)           |
 | `noticeUuid`       | `string`     | Yes      | -                        | Notice UUID to fetch and render                                       |
 | `baseUrl`          | `string`     | No       | Production consent API   | Base URL for the consent API                                          |
+| `ledgerBaseUrl`    | `string`     | No       | -                        | Go ledger base URL. When set, the consent write routes through the ledger (falls back: ledger → baseUrl → default). Notice fetch, OTP, and TTS always stay on `baseUrl`. Omit for legacy behavior. |
 | `onDecline`        | `() => void` | No       | Logs and resets the flow | Called when the agent/customer declines (host should unmount the modal) |
 | `onComplete`       | `() => void` | No       | Logs and resets the flow | Called when the agent clicks "Proceed" on the confirmed screen        |
 
@@ -761,6 +838,7 @@ import { RedactoPrivacyCenter } from "@redacto.io/consent-sdk-react/privacy-cent
 | Prop           | Type                                                                                                                       | Required | Default              | Description                                              |
 | -------------- | -------------------------------------------------------------------------------------------------------------------------- | -------- | -------------------- | -------------------------------------------------------- |
 | `baseUrl`      | `string`                                                                                                                   | Yes      | -                    | Consent server base URL                                  |
+| `ledgerBaseUrl` | `string`                                                                                                                  | No       | -                    | Go ledger base URL. When set, user consents, group purposes, receipts, and manage-consent route through the ledger, and the DSAR form's product picker is overlaid from ledger-served consents. Omit to use the legacy `/dsar/privacy-center/*` routes. |
 | `slug`         | `string`                                                                                                                   | Yes      | -                    | Workspace slug                                           |
 | `accessToken`  | `string`                                                                                                                   | Yes      | -                    | JWT access token                                         |
 | `refreshToken` | `string`                                                                                                                   | Yes      | -                    | JWT refresh token                                        |

package/dist/{chunk-6A665OPR.mjs → chunk-OGL6OC3A.mjs}

@@ -25,6 +25,10 @@ var useMediaQuery = (query) => {
   return matches;
 };
 
+// src/shared/sandbox.ts
+var SANDBOX_TOKEN_HEADER = "X-Consent-Token";
+
 export {
+  SANDBOX_TOKEN_HEADER,
   useMediaQuery
 };

package/dist/index.d.mts

@@ -43,8 +43,34 @@ type DigiLockerCallbackProps = {
 
 type Props$1 = Readonly<{
     noticeId: string;
-    accessToken: string;
-    refreshToken: string;
+    /**
+     * JWT access token. Optional so sandbox integrations (see `token`) can
+     * omit it. Required in the normal JWT flow.
+     */
+    accessToken?: string;
+    /** JWT refresh token. Optional; accepted for source-compat, currently unused. */
+    refreshToken?: string;
+    /**
+     * Sandbox PoC: a pasted static token. When set, the SDK runs against the
+     * sandbox with no JWT — it sends the single `X-Consent-Token` header, carries
+     * the acting identity (`email` || `mobile`) in each request's own payload,
+     * takes org/workspace from `organisationUuid`/`workspaceUuid`, and does no
+     * token refresh.
+     */
+    token?: string;
+    /** Sandbox test subject email (carried in the request payload when set). */
+    email?: string;
+    /** Sandbox test subject mobile (fallback subject when `email` is absent). */
+    mobile?: string;
+    /**
+     * Sandbox UCIC: the client's own user id / org_user_id, e.g. a UUID or
+     * customer code; optional third identifier alongside email/mobile.
+     */
+    ucic?: string;
+    /** Sandbox org UUID (replaces the JWT-decoded org in sandbox mode). */
+    organisationUuid?: string;
+    /** Sandbox workspace UUID (replaces the JWT-decoded workspace in sandbox mode). */
+    workspaceUuid?: string;
     baseUrl?: string;
     ledgerBaseUrl?: string;
     settings?: Partial<Settings$1>;
@@ -76,7 +102,7 @@ type Props$1 = Readonly<{
  * to view and manage their consent preferences. Supports both initial consent
  * collection and reconsent flows.
  */
-declare const RedactoNoticeConsent: ({ noticeId, accessToken, refreshToken, baseUrl, ledgerBaseUrl, language, blockUI, onAccept, onDecline, onError, settings, applicationId, validateAgainst, digilockerMode, digilockerCallbackUrl, includeFullyConsentedData, reviewModeButtonText, }: Props$1) => react__default.JSX.Element;
+declare const RedactoNoticeConsent: ({ noticeId, accessToken, refreshToken, token, email, mobile, ucic, organisationUuid, workspaceUuid, baseUrl, ledgerBaseUrl, language, blockUI, onAccept, onDecline, onError, settings, applicationId, validateAgainst, digilockerMode, digilockerCallbackUrl, includeFullyConsentedData, reviewModeButtonText, }: Props$1) => react__default.JSX.Element;
 
 type Settings = {
     button: {
@@ -139,6 +165,8 @@ type RedactoNoticeAssistedProps = {
     noticeUuid: string;
     /** API base URL (defaults to the production consent API). */
     baseUrl?: string;
+    /** Go ledger base URL — routes the consent write to the ledger; omit to use the legacy consent server. */
+    ledgerBaseUrl?: string;
     /** Called when the agent/customer declines (host should unmount the modal). */
     onDecline?: () => void;
     /** Called when the agent clicks "Proceed" on the confirmed screen. */
@@ -159,7 +187,7 @@ type RedactoNoticeAssistedProps = {
  * submit, `onComplete` fires immediately with no confirmation screen (mirroring
  * RedactoNoticeConsent's `onAccept`). Steps: `notice` → `verify` (with `otpSent`).
  */
-declare const RedactoNoticeAssisted: ({ organisationUuid, workspaceUuid, noticeUuid, baseUrl, onDecline, onComplete, }: RedactoNoticeAssistedProps) => react.JSX.Element;
+declare const RedactoNoticeAssisted: ({ organisationUuid, workspaceUuid, noticeUuid, baseUrl, ledgerBaseUrl, onDecline, onComplete, }: RedactoNoticeAssistedProps) => react.JSX.Element;
 
 /**
  * DigiLockerCallback Component

package/dist/index.d.ts

@@ -43,8 +43,34 @@ type DigiLockerCallbackProps = {
 
 type Props$1 = Readonly<{
     noticeId: string;
-    accessToken: string;
-    refreshToken: string;
+    /**
+     * JWT access token. Optional so sandbox integrations (see `token`) can
+     * omit it. Required in the normal JWT flow.
+     */
+    accessToken?: string;
+    /** JWT refresh token. Optional; accepted for source-compat, currently unused. */
+    refreshToken?: string;
+    /**
+     * Sandbox PoC: a pasted static token. When set, the SDK runs against the
+     * sandbox with no JWT — it sends the single `X-Consent-Token` header, carries
+     * the acting identity (`email` || `mobile`) in each request's own payload,
+     * takes org/workspace from `organisationUuid`/`workspaceUuid`, and does no
+     * token refresh.
+     */
+    token?: string;
+    /** Sandbox test subject email (carried in the request payload when set). */
+    email?: string;
+    /** Sandbox test subject mobile (fallback subject when `email` is absent). */
+    mobile?: string;
+    /**
+     * Sandbox UCIC: the client's own user id / org_user_id, e.g. a UUID or
+     * customer code; optional third identifier alongside email/mobile.
+     */
+    ucic?: string;
+    /** Sandbox org UUID (replaces the JWT-decoded org in sandbox mode). */
+    organisationUuid?: string;
+    /** Sandbox workspace UUID (replaces the JWT-decoded workspace in sandbox mode). */
+    workspaceUuid?: string;
     baseUrl?: string;
     ledgerBaseUrl?: string;
     settings?: Partial<Settings$1>;
@@ -76,7 +102,7 @@ type Props$1 = Readonly<{
  * to view and manage their consent preferences. Supports both initial consent
  * collection and reconsent flows.
  */
-declare const RedactoNoticeConsent: ({ noticeId, accessToken, refreshToken, baseUrl, ledgerBaseUrl, language, blockUI, onAccept, onDecline, onError, settings, applicationId, validateAgainst, digilockerMode, digilockerCallbackUrl, includeFullyConsentedData, reviewModeButtonText, }: Props$1) => react__default.JSX.Element;
+declare const RedactoNoticeConsent: ({ noticeId, accessToken, refreshToken, token, email, mobile, ucic, organisationUuid, workspaceUuid, baseUrl, ledgerBaseUrl, language, blockUI, onAccept, onDecline, onError, settings, applicationId, validateAgainst, digilockerMode, digilockerCallbackUrl, includeFullyConsentedData, reviewModeButtonText, }: Props$1) => react__default.JSX.Element;
 
 type Settings = {
     button: {
@@ -139,6 +165,8 @@ type RedactoNoticeAssistedProps = {
     noticeUuid: string;
     /** API base URL (defaults to the production consent API). */
     baseUrl?: string;
+    /** Go ledger base URL — routes the consent write to the ledger; omit to use the legacy consent server. */
+    ledgerBaseUrl?: string;
     /** Called when the agent/customer declines (host should unmount the modal). */
     onDecline?: () => void;
     /** Called when the agent clicks "Proceed" on the confirmed screen. */
@@ -159,7 +187,7 @@ type RedactoNoticeAssistedProps = {
  * submit, `onComplete` fires immediately with no confirmation screen (mirroring
  * RedactoNoticeConsent's `onAccept`). Steps: `notice` → `verify` (with `otpSent`).
  */
-declare const RedactoNoticeAssisted: ({ organisationUuid, workspaceUuid, noticeUuid, baseUrl, onDecline, onComplete, }: RedactoNoticeAssistedProps) => react.JSX.Element;
+declare const RedactoNoticeAssisted: ({ organisationUuid, workspaceUuid, noticeUuid, baseUrl, ledgerBaseUrl, onDecline, onComplete, }: RedactoNoticeAssistedProps) => react.JSX.Element;
 
 /**
  * DigiLockerCallback Component