Core Banking Augmentation Software for Banks across the UAE

Six connected capability areas: (1) Decree-Law 6/2025 transition layer with evidence capture and item-level readiness tracking. (2) Aani and Jaywan integration orchestration above AEP rails. (3) Article 149 fraud and APP-scam orchestration with customer-facing friction flows. (4) Open Finance consent and TPP management aligned to CBUAE Common Infrastructural Services. (5) Arabic document layer for deposit, credit, and customer communication templates. (6) Leadership dashboards for core platform health, transition progress, and integration status.

Around those six, most banks also want: UAE PASS identity integration alongside the bank's own authentication, Al Etihad Credit Bureau data flows into onboarding and lending, and Takaful product hooks where the bank operates an Islamic window.

Core replacement - moving from Finacle to Mambu or FLEXCUBE to Thought Machine Vault - is a multi-year programme with significant implementation cost and material execution risk. For stable cores serving the bank effectively, replacement lift often exceeds value recovered over a realistic timeframe.

Augmentation keeps the core, adds a surgical layer above it, and closes UAE-specific gaps without the replacement lift. Emirates NBD's seven-country Finacle consolidation, Mashreq's FLEXCUBE rollout across 160+ legacy applications, and Wio's cloud-native Mambu build each required years. The augmentation layer moves forward with the core through any future replacement because the UAE-specific gaps persist.

Federal Decree-Law No. 6 of 2025 applies from 16 September 2025 with a transition to 16 September 2026. Licensing evidence, governance documentation, Article 62 emerging-technology perimeter mapping, Article 149 fraud-prevention evidence, and ESG disclosure frameworks need to be in place before the deadline.

The layer tracks readiness against configurable item sets. Leadership sees item-level status rather than Excel-based progress reports. Existing regulations issued under the 2018 CBUAE Law and 2023 Insurance Law remain in force until formally replaced - the platform supports both frameworks in parallel through the transition.

Al Etihad Payments operates Aani (instant payments) and Jaywan (domestic card scheme) as subsidiaries of CBUAE. Aani uses ISO 20022 messaging with direct and indirect participation models. Jaywan operates with co-badging across Discover, Mastercard, UnionPay, and Visa and supports Samsung Wallet with Apple Pay and Google Pay in progress.

The orchestration layer handles request-to-pay, e-direct-debit, P2P transfer, merchant QR, and Jaywan card issuance customer journeys. AEP format changes and new features (cross-border corridors, electronic direct debit, e-cheques) are absorbed as configuration rather than core releases. Per-institution limits, sub-limits, and fraud controls sit in the layer.

Decree-Law 6/2025 Article 149 requires proactive customer notification of security breaches or fraud incidents and close cooperation with CBUAE on fraud data and patterns. Authorised push payment fraud, impersonation scams, investment scams, and account takeover are the focus areas.

The orchestration layer runs real-time intervention on suspicious flows - customer-facing friction for high-risk transfers, breach notification automation, and fraud-data aggregation for CBUAE reporting. Fraud engines like NICE Actimize or Quantexa provide the detection signal; the layer handles the customer and regulator-facing workflow on top.

CBUAE Open Finance is Phase 1 live, covering banks and insurers. The framework uses a centralised API Hub operated through a CBUAE-aligned entity (publicly referenced as Nebras), a Trust Framework, and a Consent and Authorisation Manager exposed as a standalone user app. TPPs including Tarabut Gateway, Lean Technologies, Fintech Galaxy, and Brankas operate on top.

The augmentation layer provides consent lifecycle management, TPP relationship management, data-scraping prohibition enforcement, and CBUAE No Objection Certificate evidence capture. Open Finance scope covers current and savings accounts, credit cards, personal and auto loans, mortgages, overdrafts, and insurance products.

Here's where custom core augmentation typically sits in a wider stack.

Core banking platforms - we sit alongside Infosys Finacle (Emirates NBD consolidation; Emirates Islamic), Oracle FLEXCUBE (Mashreq legacy consolidation), Temenos Transact, TCS BaNCS, Mambu (Wio Bank on Microsoft Azure), and Thought Machine Vault.

Digital engagement - we integrate with Backbase, Finacle Digital, Oracle Banking Digital Experience, Red Hat OpenShift (Emirates NBD Sahab), and custom React and Flutter front-ends on top of Mambu.

Payment rails and identity - we orchestrate with Al Etihad Payments for Aani and Jaywan, Network International and Magnati for acquiring, and UAE PASS, Emirates ID, and Al Etihad Credit Bureau for identity and credit.

Integration approach is scoped during discovery. We don't ask you to rip and replace anything that works.

Discovery runs six to eight weeks. Working with your IT leadership, risk, compliance, product, and payments teams, we map current core stack, Decree-Law 6/2025 readiness, Aani and Jaywan integration, Article 149 fraud practice, and Open Finance approach. Output is a detailed report covering current-state map, augmentation architecture, integration scope against the core, phased implementation plan, and fixed-price build proposal.

Build for an initial augmentation layer runs sixteen to twenty-four weeks from discovery completion. Full transition-readiness, Aani and Jaywan orchestration, Article 149 workflow, and Open Finance rollout phases in over twelve to twenty-four months depending on core platform count and product mix.

Pricing varies materially by core stack, integration breadth, and product scope. A bracket isn't published; discovery produces a fixed-price proposal with no obligation to proceed.