, home
Customer access Request an enterprise demo
Request an enterprise demo Customer access

Banking & financial services / APPLICATION BLUEPRINT

Open Banking Consent Management

Manages customer-authorised open banking data-sharing requests, third-party accreditation evidence and permitted access scope.

Start generatingExplore illustrative interface

11 workspace menus · 12 business workflows · 5 role profiles

Application blueprint only. This is a proposed design, not a deployed or production-tested system. Screens and sample figures are illustrative; workflows, business rules, approvals, permissions and integrations require confirmation before build.

Designed for operations analysts and the responsible business owners

Open Banking Consent Management workspace interface preview; illustrative records and figures.
Open Banking Consent Management — operational workspaceIllustrative interface · Sample dataView full interface →

Explore an illustrative interface.

Illustrative workspace and record review. Select a concept screen to inspect it in full.

Open Banking Consent Management workspace interface preview; illustrative records and figures.
Open Banking Consent Management — operational workspaceIllustrative interface · Sample dataView full interface →
Open Banking Consent Management record interface preview; illustrative records and figures.
Open Banking Consent Management — record and workflow reviewIllustrative interface · Sample dataView full interface →

Operational dashboards and work queues.

Operational views

Review work, evidence, exceptions and authorised decisions within a defined operating scope.

Service / branchPeriodAssigned teamReview state

Dashboard measures

  • Active permission records
    Count of all records in the selected workspace.
  • Review queue
    Records at the third stage of the business workflow.
  • Needs attention
    Records with an assigned review requirement.
  • Final-stage records
    Records in the fourth business workflow stage.

Business workflow and operating scope

Manages customer-authorised open banking data-sharing requests, third-party accreditation evidence and permitted access scope. Tracks consent status, exceptions, renewals and revocations, with traceable records supporting connected access controls and review of ongoing sharing arrangements.

Operations

Operational overview

Review the work position and priority actions.

Customer-authorised open banking data-sharing requests

Coordinate customer-authorised open banking data-sharing requests with assigned responsibilities, linked records and review history.

Third-party accreditation evidence

Coordinate third-party accreditation evidence with assigned responsibilities, linked records and review history.

Permitted access scope

Coordinate permitted access scope with assigned responsibilities, linked records and review history.

Consent status

Coordinate consent status with assigned responsibilities, linked records and review history.

Renewals

Coordinate renewals with assigned responsibilities, linked records and review history.

Revocations

Coordinate revocations with assigned responsibilities, linked records and review history.

Insights

Reports and saved views

Review the reporting scope and export agreed operational views.

Governance

Approvals and exceptions

Review delegated decisions, exceptions and recorded conditions.

Audit history

Trace accepted changes, decisions and accountable actions.

Access and configuration

Manage the agreed role permissions and configurable operating rules.

The end-to-end business journey.

From intake to authorised completion, with evidence at each decision.

01

Capture the request and scope

Establish the scope of customer-authorised open banking data-sharing requests, capture the required records and assign the accountable team.

02

Review permissions and evidence

Coordinate third-party accreditation evidence, permitted access scope, with linked evidence and visible outstanding actions.

03

Record the authorised decision

Review the relevant conditions and exceptions. Record the authorised outcome and its supporting evidence.

04

Track access and later changes

Confirm the resulting records and handovers. Track remaining obligations, later changes and follow-up actions.

Business workflows

Select a workflow to review the steps, responsibilities, approval and exception handling.

01 · Manage customer-authorised open banking data-sharing requests

Coordinate customer-authorised open banking data-sharing requests within Open Banking Consent Management.

Trigger
Customer-authorised open banking data-sharing requests requires a new record, an agreed review or a controlled change.

Responsible role
Operations analyst

  • Register customer-authorised open banking data-sharing requests and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

02 · Manage third-party accreditation evidence

Coordinate third-party accreditation evidence within Open Banking Consent Management.

Trigger
Third-party accreditation evidence requires a new record, an agreed review or a controlled change.

Responsible role
Risk reviewer

  • Register third-party accreditation evidence and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

03 · Manage permitted access scope

Coordinate permitted access scope within Open Banking Consent Management.

Trigger
Permitted access scope requires a new record, an agreed review or a controlled change.

Responsible role
Operations analyst

  • Register permitted access scope and its operating scope
  • Check permitted purpose, prerequisites and authority
  • Record the delegated approval or refusal
  • Track term, withdrawal and later changes

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Authority is missing, permission changes or the requested purpose exceeds the accepted scope.

Outcome
A scoped permission or recorded refusal, its conditions and review history.

04 · Track consent status

Coordinate consent status within Open Banking Consent Management.

Trigger
Consent status requires a new record, an agreed review or a controlled change.

Responsible role
Operations analyst

  • Register consent status and its operating scope
  • Check permitted purpose, prerequisites and authority
  • Record the delegated approval or refusal
  • Track term, withdrawal and later changes

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Authority is missing, permission changes or the requested purpose exceeds the accepted scope.

Outcome
A scoped permission or recorded refusal, its conditions and review history.

05 · Track exceptions

Coordinate exceptions within Open Banking Consent Management.

Trigger
Exceptions requires a new record, an agreed review or a controlled change.

Responsible role
Operations analyst

  • Register exceptions and its operating scope
  • Gather the relevant evidence and review options
  • Route the case to the delegated decision owner
  • Record the outcome, conditions and follow-up obligations

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
The case exceeds delegation, contains a conflict or has disputed evidence.

Outcome
An authorised decision or escalation with accountable resolution actions.

06 · Track renewals

Coordinate renewals within Open Banking Consent Management.

Trigger
Renewals requires a new record, an agreed review or a controlled change.

Responsible role
Operations analyst

  • Register renewals and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

07 · Track revocations

Coordinate revocations within Open Banking Consent Management.

Trigger
Revocations requires a new record, an agreed review or a controlled change.

Responsible role
Operations analyst

  • Register revocations and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

08 · Register the operating requirement

Coordinate operating requirement within Open Banking Consent Management.

Trigger
Operating requirement requires a new record, an agreed review or a controlled change.

Responsible role
Operations analyst

  • Register operating requirement and its operating scope
  • Compare options, dependencies and operating constraints
  • Review the selected option with its accountable owners
  • Accept the plan and track its delivery conditions

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
An assumption changes, prerequisites are missing or stakeholders cannot accept the proposed commitment.

Outcome
An approved operating plan and owned actions for its accepted conditions.

09 · Resolve operating exceptions

Coordinate operating exceptions within Open Banking Consent Management.

Trigger
Operating exceptions requires a new record, an agreed review or a controlled change.

Responsible role
Operations analyst

  • Register operating exceptions and its operating scope
  • Gather the relevant evidence and review options
  • Route the case to the delegated decision owner
  • Record the outcome, conditions and follow-up obligations

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
The case exceeds delegation, contains a conflict or has disputed evidence.

Outcome
An authorised decision or escalation with accountable resolution actions.

10 · Verify completion and follow-up

Coordinate completion and follow-up within Open Banking Consent Management.

Trigger
Completion and follow-up requires a new record, an agreed review or a controlled change.

Responsible role
Risk reviewer

  • Register completion and follow-up and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

11 · Review controlled operating changes

Coordinate controlled operating changes within Open Banking Consent Management.

Trigger
Controlled operating changes requires a new record, an agreed review or a controlled change.

Responsible role
Risk reviewer

  • Register controlled operating changes and its operating scope
  • Collect the linked records and qualified evidence
  • Assign the responsible reviewer and record findings
  • Accept the outcome or assign corrective follow-up

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Evidence is incomplete, disputed, expired or outside the reviewer’s authority.

Outcome
A review finding, its accepted evidence and any accountable corrective actions.

12 · Prepare scoped operational reports

Coordinate scoped operational reports within Open Banking Consent Management.

Trigger
Scoped operational reports requires a new record, an agreed review or a controlled change.

Responsible role
Operations analyst

  • Register scoped operational reports and its operating scope
  • Assign the accountable owner and required actions
  • Review the relevant evidence and unresolved conditions
  • Confirm the accepted outcome and retain its history

Approval
Authorised decision maker records the decision when the action changes an accepted commitment or requires delegated authority.

Exception handling
Required information or responsibility is missing, or an operating condition changes.

Outcome
A completed operating record with its linked evidence and remaining obligations.

Governance and control

  • Role permissions reflect the agreed responsibilities and restricted record access.
  • Sensitive information is restricted to the agreed roles and permitted sharing scope.
  • Required information and evidence are checked before the relevant decision or handover.
  • Exceptions have a named owner, recorded reason and an authorised resolution.
  • Approved changes retain their previous values, accountable decisions and linked evidence.
  • Integration mappings, business rules and acceptance criteria are reviewed with the customer.
Operating rules by business workflow
  • For customer-authorised open banking data-sharing requests, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For third-party accreditation evidence, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For permitted access scope, the request stays within the recorded permission and delegated authority.
  • For consent status, the request stays within the recorded permission and delegated authority.
  • For exceptions, a decision retains its authority, reason, supporting evidence and resulting obligations.
  • For renewals, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For revocations, the record retains an accountable owner, its supporting evidence and accepted outcome.
  • For operating requirement, the accepted plan records assumptions, rejected alternatives, dependencies and conditions.
  • For operating exceptions, a decision retains its authority, reason, supporting evidence and resulting obligations.
  • For completion and follow-up, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For controlled operating changes, evidence, reviewer authority and acceptance conditions are visible before a reviewed outcome is accepted.
  • For scoped operational reports, the record retains an accountable owner, its supporting evidence and accepted outcome.

Data, interfaces and operating requirements.

Core records

Permission recordCustomer-authorised open banking data-sharing requestsThird-party accreditation evidencePermitted access scopeConsent statusRenewalsDecisionSupporting evidenceActivity history
Record fields and linked information
  • Record identifier — Stable reference for the operating transaction.
  • Service / branch — Business scope used for responsibility and reporting.
  • Operating subject — The request, commitment or work item being handled.
  • Accountable owner — Named responsibility for the next action.
  • Workflow stage — Current position in the agreed business journey.
  • Review requirement — Required review and outstanding decision.
  • Due or review date — Agreed action window or review trigger.
  • Linked evidence — Source records supporting the operating decision.
  • Decision authority — The delegated authority relevant to the accepted outcome.
  • Accepted outcome — Recorded decision and its business consequences.
  • Follow-up obligation — Remaining responsibilities after an accepted action.
  • Revision history — Trace of accepted changes and their evidence.
  • Customer-authorised open banking data-sharing requests reference — Link the relevant customer-authorised open banking data-sharing requests to the operating transaction and its decision evidence.
  • Third-party accreditation evidence reference — Link the relevant third-party accreditation evidence to the operating transaction and its decision evidence.
  • Permitted access scope reference — Link the relevant permitted access scope to the operating transaction and its decision evidence.
  • Consent status reference — Link the relevant consent status to the operating transaction and its decision evidence.
  • Renewals reference — Link the relevant renewals to the operating transaction and its decision evidence.

Systems and interfaces

  • Core banking or financial service records
  • Approved risk, payment or case-management interfaces
  • Identity and role-based access services
  • Approved document and communication services

Interface scope, data mapping and testing are agreed for each engagement.

Implementation requirements
Confirm the operating boundaries, customer-authorised open banking data-sharing requests, responsible roles, review authority, record retention, interface mappings and acceptance scenarios.

Mobile and tablet access

Authorised users can review customer-authorised open banking data-sharing requests, supporting records and assigned actions through mobile and tablet access. The relevant tasks and permissions are agreed for the deployment.

Access approved workflows through the Dalfin mobile app. Device tasks and permissions are confirmed for the deployment.

Apple App Store ↗Google Play ↗

AI extensions

Core workflows and approval rules are defined with your business owners. Operational AI can be assessed separately against a specific business outcome and review requirements.

AI extensions are scoped around the required data, business outcome and review controls.

Engineered with Genesis.

Structured application engineering

Connect requirements, roles, records, workflows and interfaces through the agreed Genesis engineering process.

Controlled changes

Review dependency impact and validation requirements. Context Memory supports governed changes and accepted application revisions.

Deployment and support

Agree customer cloud or on-premises requirements, device access, implementation acceptance and ongoing engineering support.

AN EXAMPLE OPERATING SCENARIO

What to validate in a scoped demonstration.

Start with customer-authorised open banking data-sharing requests and follow the record through review permissions and evidence. Introduce a missing item or operating exception, record the authorised resolution and inspect the final handover, evidence and history.

What to review

  • A saved end-to-end transaction
  • An exception and its authorised resolution
  • Different operator, approver and reviewer permissions
  • Final records, history and the relevant report
Discuss this solution

Questions before implementation.

What can we review in a tailored demonstration?

Review a representative permission record, its workflow stages, accountable roles, an exception and the resulting operational report. Bring the business process and existing system requirements that matter to your organisation.

How is the solution adapted to our organisation?

The operating scope covers your records, role permissions, review authority, business rules and integration boundaries. These requirements are agreed with the responsible business owners.

How does the solution connect with existing systems?

Connection design defines interfaces, data ownership, mapping, authentication and exception handling. The agreed implementation includes validation against the selected systems and workflows.

How are subsequent changes controlled?

The agreed engineering approach covers review of change impact, bounded implementation, validation and accepted revisions. Discuss the relevant Genesis Context Memory and support requirements during solution scoping.