Component Overview

Mas Consents is a hosted frontend that lets a customer review and submit consent statements. Consumer applications embed it and provide the customer context through URL parameters, with an optional JSON configuration message when they need to customize the experience.

The component:

loads runtime platform configuration from /config.json
reads customer, brand, locale and flow information from the URL
fetches consent data from the consents backend
renders the current Custom UI path
submits the customer selection
notifies the host with lifecycle messages

Runtime contract

The runtime has one rendering path: AppCustomTheme mounting ConsentsCoreCustom. The previous Legacy UI component is no longer part of the application flow.

URL flag	Rendering behavior	Host configuration requirement
`enableCustomConfig` absent or `false`	Renders immediately with default theme and UI options	None
`enableCustomConfig=true`	Sends `CONSENTS_CONFIG_REQUIRED` and waits until the host sends JSON via `SET_CONFIG`	Required

enableCustomConfig only controls whether the component waits for host-provided JSON configuration before rendering. It does not select a different component implementation.

Integration model

text

Host application
  -> builds the iframe / WebView URL
  -> optionally listens for CONSENTS_CONFIG_REQUIRED
  -> optionally sends SET_CONFIG
  -> listens for loaded, completed and error events

mas-consents
  -> reads URL parameters
  -> loads /config.json
  -> initializes the bridge
  -> renders the Custom UI path
  -> calls the backend
  -> reports lifecycle events back to the host

Host responsibilities

The host application must:

provide the URL parameters needed by the target flow
provide a valid token for real backend calls
listen to completion and error events
decide what to do after the customer submits or the component reports an error
send SET_CONFIG only when enableCustomConfig=true is present in the URL

The host application does not need to understand the internal statement tree, token validation implementation, or local development setup to integrate the component. Those details are covered in the IDP technical reference.