Open Banking

The Open banking application displays the consent details from a third-party application, such as Account Information Services and Payment Initiation for the signed-in users.

The signed-in user can perform the following:

• The user can view the account information consent details from a third-party application with an option to Approve or Reject the consent.
• The user can view the third-party name and request information.
• The user can view the account information such as Account number/ IBAN, Account category, Account balance, and Account holder name.
• The user can view the relevant information requested from a third-party application.
• The user can view the payment information request from a third-party application that includes requested amount, any charges if applicable with an option to Approve or Reject the payment request.
• The user can view the list of accounts to make the payment requested by a third party.

Prerequisites and Dependencies

Prerequisite/Dependency	Details
Required Visualizer Micro App	OpenBankingMA HomepageMA AuthenticationMA AboutUsMA CampaignMA UserManagementMA ResourceMA CommonMA
Required Fabric Micro App	Open Banking
Front Office Enterprise	NA
Back Office Enterprise	Mock service Transact
Fabric Engine	NA

Open Banking Visualizer App

The Visualizer app contains the required forms and associated artifacts bundled together in the Micro App architecture. The Visualizer App contains the following features:

• Account Consent (Prelogin Screen, Account Consent details, Acknowledgment screen and Error screens).
• Payment Consent (Prelogin Screen, Payment details, Account selection Acknowledgment screen and Error screens).
• Card Based Payment Consent (Prelogin Screen, Consent details, Acknowledgment screen and Error screens).

From 24.10, this feature is applicable to Mobile Nativeplatforms of the digital banking application.
From 24.12, this feature is applicable to Online banking users.

Open Banking Fabric App

The Fabric app contains the object services and APIs related to the following functionality:

• Auth token validation
• API integration with transact for consent details
• Moving consent to INAU
• Moving consent to live
• Experiance API to invoke existing Payment API for approval
• Rejecting consents
• Deleting consents