1.5 Virtual Accounts Management
As part of this release, Virtual Accounts Management OBAPI has been enhanced with APIs that supports the following features:
Access check in Statements:
Currently, search results for the chosen statement type in both Pre-Generated and Ad hoc statements are driven only by the statement preference set at the Virtual Entity/Account level. With this change, existing API has been enhanced to verify if an appropriate access has been provided to the Virtual Account(s) for the selected Virtual Entity for which the user wants to download the statement.
- Pre-Generated Statements -
PDF Statements:
- In the scenario, when the statement preference is set to the Virtual Entity Level (consolidated), users can generate the PDF statement only if they have access to all the Virtual accounts associated within that Virtual Entity.
- If the statement preference level is at the Account Level, users can download the PDF statement only if appropriate access has been maintained to the Virtual Account in context.
MT/CAMT Statements:
- Users can download MT/CAMT statement only if an appropriate access has been provided to the Virtual Account in context.
- Ad hoc statements -
- Users can download all statement types (PDF & MT/CAMT) provided an appropriate access has been maintained to the Virtual Account in context.
Removal of Core DDA dependencies:
Existing API has been enhanced to capture whether integration with bank’s DDA is available or not for Oracle Banking Digital Experience. With this, the Virtual Account module will work seamlessly even when integration to the bank’s DDA is not available. In such a scenario, the parameter "DDA availability for Virtual Accounts Management (Y/N)" will be set to N and the real account balances will not be displayed on the UI but the virtual account functionalities will continue to work.
Role Transaction Mapping Clean-up:
Existing API has been enhanced to simplify the categorization of role transaction mapping for all the transactions related to Virtual Accounts Management, effectively grouping them under the relevant transaction menu categories. Following changes have been done –
- Grouping of transactions from individual transactions (Create, Edit, View, Download, etc.) into broader categories (Maintain, Inquire, Delete, etc.)
Additionally, the dependencies between cross transactions have been updated to ensure that all functional transactions in the Hamburger Menu works in line with the corresponding line items listed under RTM transactions.