Validate · Enforce · Trust

CMI — Bank Data Sharing Requirements v2.15 min read

The tables below define the display, labelling, and behavioural requirements for the Bank Data Sharing consents in the TPP Consent Management Interface (CMI). See the User Experience page for interactive wireframes of the dashboard and detail pages.

Adjustments to the requirements below are permitted provided the customer can always clearly understand what consents they have granted. Any adjustments must be documented in your CX certification submission.

01 Section

Dashboard — tabs

The dashboard must present Bank Data Sharing consents across two tabs.

Rule

The Current tab must display all consents whose status is AwaitingAuthorization, Authorized, Suspended, or Paused.

The History tab must display all consents whose status is Rejected, Expired, or Revoked.

02 Section

Dashboard — filters

A filter panel must be available on the dashboard. The following three filters are required:

Filter

Options

LFI Name

Dynamically populated from the LFIs present in the user's connections

Consent Type

Dynamically populated from the types present in the current tab

Consent State

Dynamically populated from the statuses present in the current tab

03 Section

Status labels

Consent statuses must be translated from their API values into user-friendly labels before display.

API status

Displayed label

Authorized

Active

AwaitingAuthorization

Pending

Revoked

Cancelled

Suspended

Suspended

Paused

Paused

Expired

Expired

Rejected

Rejected

05 Section

Dashboard — card content

Each Bank Data Sharing consent card on the dashboard must show the following fields.

Field

Content

LFI name

Name of the LFI the consent is held with

Status badge

Mapped label from Status labels

Account count

Number of connected accounts, e.g. 1 Account Connected or 2 Accounts Connected

Consent Type

Data Sharing

Last data received

Date the most recent data was retrieved under this consent

Connection expires

Date the consent expires

06 Section

Detail page

Selecting a consent on the dashboard opens its detail page. The detail page presents the same information the customer saw on the Consent Page at the time they gave consent — the permissions, accounts, and conditions that defined what they agreed to. This gives the customer a clear reference point for what they originally authorised, without requiring them to recall it from memory. In addition to all fields shown on the dashboard card, the detail page must show a truncated Consent ID with a copy button (format: f47ac10b...d479).

Additional sections

Section

Content

Accounts

List of all accounts the user has connected under this consent, each showing account type name and full IBAN

Data permissions

Expandable list of data categories the consent covers, derived from the consent's Permissions field

"How we are using your data" card

A card titled How we are using your data must appear below the Data permissions section, except when status is Rejected.

Status behaviour

Rejected: Card is not shown
Revoked: Title changes to You cancelled this connection
Expired: Connection Expires label changes to Connection Expired
All other statuses: Default title and labels

Date rows each prefixed with a calendar or refresh icon

1
First Connected
Date the consent was first authorised
2
Connection Expires / Connection Expired
Consent expiration date
3
Last Updated
Date of the most recent data retrieval — only shown when the consent has a BaseConsentId
4
List of Updates
Clickable link to the List of Updates view — only shown when the consent has a BaseConsentId

Detail page — List of Updates

When a consent carries a BaseConsentId, a List of Updates link must be shown on the detail page. Clicking this link navigates to a dedicated view that displays all consents related to the current consent through the same BaseConsentId. The related consents are retrieved via GET /account-access-consents, passing the baseConsentId query parameter. A consent is included in the list if:

its BaseConsentId matches the current consent's BaseConsentId, or
its ConsentId matches the current consent's BaseConsentId

The current consent must not appear in its own list of updates.

Each related consent card

Each related consent must be displayed in the same visual format as the dashboard connection list, with the following differences:

Field

Content

Title (bold)

Date the consent was last updated

Subtitle (italic)

LFI name, e.g. [LFI 9]

Consent Type

Type label from Consent type labels

Last data received

Date the most recent data was retrieved

Connection expires

Consent expiration date

Each card must include a chevron and hover interaction matching the dashboard, and clicking a card must navigate to the detail page for that consent. No status badge is shown on the update cards.

07 Section

Detail page — action buttons

Button

Label

Shown when

Pause

Pause

Status is Authorized

Reactivate

Reactivate

Status is Paused

Revoke

Stop Sharing

Status is AwaitingAuthorization, Authorized, Suspended, or Paused

No action buttons are shown when status is Expired, Rejected, or Revoked.

08 Section

Confirmation screen

When the user selects Pause, Reactivate, or Revoke, replace the detail view with a single confirmation screen that includes: a title, a description of the impact of the action on the service, a Confirm button, and a Go back button.

Pause

Reactivate

Revoke

Title

Pause data sharing

Resume data sharing

Stop sharing

Confirm button

Confirm pause

Confirm reactivation

Confirm stop sharing

Once a user confirms the action, the change must take effect immediately — there must be no delay between confirmation and the consent reflecting its new state.

Revoke Immediate PATCH to /account-access-consents/{ConsentId}
Pause No API Hub update — record paused state in the TPP's own system only
Reactivate No API Hub update — clear the paused state in the TPP's own system only