Validate · Enforce · Trust

CMI — Bank Service Initiation Requirements v2.16 min read

The tables below define the display, labelling, and behavioural requirements for the Bank Service Initiation consents (Single Instant Payment and Multi Payment) in the LFI Consent Management Interface (CMI). See the User Experience page for interactive wireframes of the dashboard and detail pages.

The LFI CMI shares the same structure and consent-type logic as the TPP CMI for Bank Service Initiation, with the differences noted below. 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

Paused is not a valid status in the LFI CMI. It is a TPP-local concept that is not reflected in the API Hub.

The dashboard must present Bank Service Initiation consents across two tabs.

Rule

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

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

02 Section

Dashboard — filters

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

Filter

Options

TPP Name

Dynamically populated from the TPPs present in the customer'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

Expired

Expired

Rejected

Rejected

Consumed

See below

`Consumed` — Single Instant Payment

For Single Instant Payments in the Consumed state, the displayed label is derived from the payment's paymentStatus field rather than the consent status.

`paymentStatus`

Displayed label

AcceptedSettlementCompleted

Successful

AcceptedCreditSettlementCompleted

Successful

AcceptedWithoutPosting

Successful

Rejected

Failed

For Multi Payment consents, Consumed is displayed verbatim as Consumed.

05 Section

Dashboard — card content

Each consent card on the dashboard must show a consistent set of fields depending on the payment consent type.

Single Instant Payment

Field

Content

TPP name

Name of the TPP the consent was granted to

Status badge

Mapped label from Status labels

Masked IBAN

Masked payer IBAN (not shown when status is AwaitingAuthorization)

Consent Type

Single Payment

Payment Date

Date the payment was or is to be made

Payment Amount

Amount of the payment in AED. Shown as 0.00 when status is AwaitingAuthorization; must be a positive value once the consent is Authorized or later

Multi Payment (all subtypes)

Field

Content

TPP name

Name of the TPP the consent was granted to

Status badge

Mapped label from Status labels

Masked IBAN

Masked payer IBAN (not shown when status is AwaitingAuthorization)

Consent Type

Flexi Pay

Total paid to date

Cumulative sum of all successful payments under this consent in AED

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 at the time they gave consent — the limits, accounts, and conditions that defined what they agreed to. 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).

Single Instant Payment — additional sections

Section

Content

Payment details

Amount, Reference, and Payment Purpose. If status is Authorized, a Status badge of Authorized must also be shown.

From account

Bank name, Payer Name, and full IBAN of the payer account

To account

Payee Name and IBAN of the destination account

Multi Payment — additional sections

Section

Content

From account

Bank name, Payer Name, and full IBAN of the payer account

To account

Payee Name and IBAN of the destination account

Payment Rules / Payment History

Tabbed section: Payment Rules shows consent parameters (schedule, limits, frequency); Payment History shows a log of all payments with date, amount, purpose, reference, and status

Multi Payment — dates card

A dates card must appear below the Payment Rules / Payment History section for all Multi Payment consents, except when status is Rejected.

Status behaviour

Rejected: Card is not shown
Revoked: Second row label changes to You cancelled payments on
Expired: Second row label changes to Payments expired
All other statuses: Default labels

Date rows

1
You started this permission
Date the consent was first authorised
2
We will make these payments until
Consent expiration date

07 Section

Detail page — action buttons

The LFI CMI does not include Pause or Reactivate buttons. These are TPP-only concepts.

Button

Label

Shown when

Revoke

Cancel Permission

Status is AwaitingAuthorization, Authorized, or Suspended

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

08 Section

Confirmation screen

When the customer selects 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.

Revoke

Title

Cancel payment permission

Confirm button

Confirm cancellation

Once a customer confirms the action, the change must take effect immediately — there must be no delay between confirmation and the consent reflecting its new state. The LFI must update the consent status via the Consent Manager API.