1.1 Retail & Corporate Features

The following enhancements have been made in the retail or corporate module in this release.

Table 1-1 Enhancements in Retail & Corporate

Enhancements	Description
Multi-Currency Accounts (MCA) Support	Oracle Banking Digital Experience now introduces broader Multi-Currency Account (MCA) support for Retail and Corporate customers. With this enhancement, customers can manage multiple currency holdings under a single account relationship, where one main account could have multiple currency-specific sub-accounts. This provides a more streamlined banking experience by improving visibility into currency-wise balances, transactions, and account details, while reducing the need to manage multiple standalone accounts. The enhancement includes flexible MCA display handling at the module and transaction level, allowing the system to present either the main account or individual sub-accounts. Sub-accounts are displayed using only the main account and currency combination. Therefore, users do not need to know or share the sub-account number separately and can manage their banking using the main account reference alone. In mixed-account scenarios, regular CASA accounts and MCA-linked sub-accounts are displayed together in a clean and intuitive way. Users can view account summaries, account details, transaction history, and statements at the relevant sub-account level, while selected services such as cheque-related requests continue to operate at the main account level. For corporate users, MCA support also simplifies administration by centralizing account access and approval management at the main account level. Access granted to the main MCA automatically extends to linked sub-accounts, and approval rules maintained at the main level are consistently applied across all sub-account transactions. This reduces maintenance effort, improves control, and ensures a consistent entitlement and approval framework across the MCA hierarchy. The MCA enhancement also extends to payment and forex journeys by aligning account selection behaviour with the transaction context. Payment initiation screens support MCA-specific subaccounts while inquiry-oriented screens continue to use main-account-level representation where consolidated results are needed. Forex screens are similarly enhanced to support MCA-specific settlement account behaviour, including correct handling of currency context during booking and inquiry flows. In addition, Open Banking account inquiry and payment services are being aligned to support MCA scenarios. This includes clearer representation of multi-currency balances, currency-aware payment validation, support for FX-related processing where applicable, and preservation of standards-compliant API behaviour for third-party integrations.
Account Activity Enhancements	Pending Transactions List Added a dedicated view on the Transactions screen to display transactions received by the payment product processor but not yet processed, with a separate pending count and drill-down list of transactions. This is applicable to Current & Savings accounts only; available out-of-box for Cloud setup—on prem implementation to be handled by the bank. Search Transactions by Description Introduced a description-based search on the Transactions screen, enabling users to quickly find account activity using keywords/phrases. Display Account Balance for User-selected Date Enabled users to view account balances as of a selected date on the Account Listing page, showing Current/Available balances for today, and Opening/Closing balances for prior dates (based on configured transaction history range). If no account was opened on the selected date, an appropriate message is shown. Grouping of Transactions on Account Statement Enhanced transaction listing with clearer visualization like credits are highlighted in bold and transactions can be optionally grouped month-wise via a filter switch (sorting applies within each month and pagination is replaced with a single scrollable list). Grouping available for Current & Savings, Loan and Deposit accounts; not supported in PDF downloads. Also, added options on the Transactions screen to initiate payments and view outgoing payments for the selected account. Display Transaction Code-based Logo Added transaction category/code-based logos in Account Activity, displaying a mapped logo per transaction with a default logo fallback when no mapping exists. This functionality includes a new administrator maintenance screen to manage logo-to-transaction category mappings.
Bonds Overview and Details	Added a configurable Bonds widget and relationship card to show bond holdings summary, with navigation to a detailed bonds view and date-based filtering.
View and Copy Account & Card Details	Enabled Retail and Corporate users to securely view and copy masked account/card details, with unmasking protected by configured 2FA and copy-to-clipboard options. Also, a “Copy All Details” feature is added where specific information can be copied for accounts and deposits.
Digital Management of Debit Cards	Expanded debit card servicing to self-service, enabling customers to view/manage cards, limits, block (temporary/permanent), replacement, PIN actions, activation and card upgrades without raising service requests.
Transaction Authorization for POS Card Payments	Introduced real-time approve/reject flow for retail card payments via push/email notifications. This will allow customers to authorize merchant/POS transactions within a configurable expiry window. Post request expiry, the transaction will be automatically cancelled or expired.
Automatic Retail User Onboarding	Introduced automatic retail user onboarding in OBDX upon CIF creation in the product processor. Once a CIF and at least one account are created, an automated notification (including CIF) triggers end-to-end onboarding. A new application initiation flag enables digital banking services for eligible customers, with configurable Day‑0 parameters to auto-provision username format, roles, limit packages, touchpoints and entity assignment. Banks can also configure the onboarding flow at user-type level (IDCS-originated/SCIM vs OBDX-originated) through Global Settings in System Configuration. Added a Digital Banking Auto‑Onboarding Status Report with flexible filters to monitor success/failure trends and support operational follow-up.
Support for New Frequencies in Reports and Statements	The Reports Framework is enhanced to support two more frequencies at which reports can be generated- Previous Calendar Month and Previous Calendar Quarter. Using the "Previous Calendar Quarter" frequency option, the Corporate User/ System Administrator can generate or schedule reports for the previous calendar quarter. Report will be generated on selected date for previous calendar quarter. For e.g., if run date is 20th February 2023, then report will be generated for 1st October to 31st December 2022. For the "Previous Calendar Month" frequency option, the Corporate User/ System Administrator can generate or schedule reports for the previous calendar month. Report will be generated on scheduled date for previous calendar month. For e.g., if run date is 20th August 2023, then report will be generated for 1st to 31st July 2023.

Table 1-2 Enhancements in Platform Framework

Enhancements	Description
Group Corporate Onboarding Enhancements for Multi-GCIF Party Mapping	Oracle Banking Digital Experience now enhances Group Corporate Onboarding to support more flexible corporate structures by allowing a single CIF or party to be associated with multiple Group Corporates where applicable. This helps banks manage complex group relationships such as shared-service arrangements, joint ventures, and cross-group affiliations without duplicate onboarding or redundant maintenance. The enhancement introduces Owner and Agent party types in Party Preference maintenance with clearer ownership controls. A Group Corporate is not required to necessarily have an Owner, but also a Group Corporate can have multiple Owner parties. However, a party designated as an Owner can be mapped as Owner to only one Group Corporate, while Agent parties can be associated with multiple Group Corporates. This model provides greater flexibility in group setup while ensuring that owner-level relationships remain clearly governed at the party level. The enhancement also improves administrator visibility by displaying all Group Corporate associations during party preference inquiry and Group Corporate onboarding search. In addition, party account access, user account access, approval rules, and biller maintenance are managed in the context of the relevant party-GCIF combination, while user groups can be maintained at the Group Corporate level and onboarding can be performed against any eligible CIF under the selected Group Corporate. Overall, this strengthens onboarding flexibility, administrative efficiency, and control across complex corporate banking relationships. In addition, File identifiers can now be created and managed directly at the GCIF level, enabling greater flexibility. The enhancement supports listing, viewing, and editing of file identifiers within the GCIF context, while ensuring that existing bank administrator file identifier maintenance flows remain unaffected. In addition, banks can configure and enable file templates based on business requirements through administrative setup.
Locale Maintenance Enhancement	Oracle Banking Digital Experience now enhances English-GB locale maintenance to provide a more consistent and scalable multilingual experience across customer-facing modules. Banks can enable multiple locales while mandatorily defining a default language that acts as the base and final fallback. The enhancement standardizes how language preferences are maintained and applied across communications and UI-driven content. The enhancement extends multilingual support across modules such as alert templates, mailers, feedback templates, security questions, SMS Banking, message maintenance, and resource bundles. Content can be maintained independently by language, with mandatory support for the base language and a consistent fallback sequence from the user’s preferred language to the parent language and then to the default language whenever localized content is unavailable. It also enhances the locale-based user experience by making language display and selection, match the enabled locale settings, including pre-login language choices and user preference handling. This helps ensure that customers receive content and communications in the most relevant available language while giving banks stronger control over multilingual content governance.
Mail Subject Maintenance	Introduced configurable mail subject maintenance and mapping feature on the digital platform. Bank administrators can create, update, activate, deactivate and organize customer-facing mail subjects by business module, user type and administrator user group without code changes. This also enables banks to map mail subjects to specific user groups, helping banks ensure relevant and streamlined communication with end customers. Desktop and mobile banking channels now dynamically display only active, eligible subjects on mail initiation screens—grouped by module—for Retail and Corporate users, while inactive or unmapped subjects remain hidden. The enhancement preserves existing mail subject mappings and flows, while supporting role-based access, auditability and scalability for future modules and user types.
Configurable Alert Email Message Format	Added a new system configuration under Event Management to control the format of banking system alert emails. Bank administrators can configure alert emails to be sent in one of the following message formats: HTML (rich text) - default Plain text The selected format applies to alert emails sent to retail users, corporate users and administrators. For cloud deployments, banks must update this configuration from the default HTML setting to plain-text format alert emails.
Numeric Input Keypad Enablement	Introduced numeric keypads for Amount and OTP inputs to speed up entry and reduce errors. Supports both a standard 0–9 keypad (e.g., PIN) and an amount keypad with 0–9 plus comma and decimal for monetary values.
SMS Notification for New User Setup	Provision to trigger SMS notifications to customers for key events such as new user setup and forgotten password, ensuring timely communication and enhanced security.
Notification for Planned and Unplanned Maintenance	Introduced new feature to display prominent maintenance or ad hoc/broadcast alerts immediately upon user login, ensuring visibility without navigating menus or inboxes. Bank Admins can configure validity period, priority, target audience (all users or specific groups), and activate/deactivate messages as needed.
Provision to skip 2FA for Biometric Login	When users login via registered biometric methods (fingerprint/face recognition), they can be exempted from the additional 2FA step, enabling faster sign-in while maintaining secure access controls and a streamlined login experience.
Auto Biometric Login on Mobile	A provision is given to handle continuous login–logout loop when Face ID (or any biometric login) is enabled. If Face ID is set, then automatic login happens upon app launch and after the user logs out, an intermediate logout page is shown instead of directly redirecting to the biometric login page, preventing auto re-login.
Customer Data Migration	Introduced a migration capability to move customer data (Payees, Users, GCIF) along with associated rules and workflows to a new environment, ensuring data integrity and a smooth, end-to-end transition.
Anonymous Entitlements on Role Maintenance Screen	Enhanced the Role Maintenance screen to support an “Anonymous Role” user type. When selected, all anonymous entitlements are available in Role Maintenance create and update, grouped under the General Access Entitlement category with the appropriate subcategories.
System Configuration Revamp and Entity Maintenance	Revamped system configuration into a dedicated microservice and migrated existing module configurations to the new architecture. Administrators can now manage entities via the Entity Maintenance screen, with options to view the entity list as well as add, edit or view entity details.
Introduction of Persona Maintenance	Introduced a Persona Maintenance screen to view, create and update Personas mapped to enterprise roles, defining user responsibilities within the application. Persona-based restrictions control user creation e.g., System Administrators can create only Bank/System Administrators; Bank Administrators can create only Retail/Corporate users. Personas are applicable across Report Mapping, Mailers, Limit Package and Transaction Working Window transactions.
Multiple Drafts & Parallel Administrator Updates	Enabled multiple independent drafts per GCIF/CIF so Bank and Corporate Administrators can work in parallel on maintenance/onboarding activities. Also, added record-level locking to prevent conflicting updates while preserving data integrity.
Group Corporate Maintenance Enhancement	Enhancement of Modify User Details API The OBDX API earlier mandated providing all users for any user group modification. The new PATCH API enhancement allows incremental updates, enabling addition or deletion of specific users without impacting existing group configurations. First Name and Last Name display in User Group As part of this enhancement, First Name and Last Name are now displayed as a part of User Group.