IBM Financial Services Jordan

Capital Bank of Jordan

Marketing Personalization · Risk Management

Capital Bank needed a modern data hub that could unify data from core banking and acquired institutions so it could integrate new businesses quickly, personalize retail banking, and support fraud and risk analytics at scale.

10x increase in detection of mobile experience issues
15+ banking applications
95% reduction in acquisition-related data migration time
millions of records in about four hours

Reported impact

Business outcome

Capital Bank accelerated acquisition integration, improved customer-experience monitoring, and built the predictive-data foundation needed for hyper-personalized offers, churn prevention, and stronger financial-crime detection.

  • Customer Experience
  • Revenue Growth
  • Risk Reduction
  • Speed to Market

Solution

Capital Bank modernized its data foundation with IBM Cloud Pak for Data and IBM Netezza Performance Server as the primary data warehouse. Jordan Business Systems used the platform to centralize data from core banking and more than 15 banking applications, then integrate data from acquired banks across Jordan and Iraq. Once the single source of truth was established, Capital Bank's developers and data scientists began using IBM Watson Machine Learning in Watson Studio on Cloud Pak for Data to predict customer behavior, score product propensity, identify churn risk, and look for suspicious transaction patterns tied to fraud and money laundering. The same data hub also underpins mobile-experience dashboards that help operational teams pinpoint issues quickly. This architecture ties together data integration, warehousing, analytics, and machine learning so the bank can move from acquisition-driven scale to hyper-personalized digital banking and faster operational response.

Data flow

Core-banking, HR, payroll, card, CRM, and acquired-bank data is centralized in Netezza through Cloud Pak for Data, then machine-learning models in Watson Studio and Watson Machine Learning analyze customer behavior, operational issues, and suspicious transactions for targeted offers and risk controls.

Solution architecture

4 components · 3 layers
  1. Compute
    • IBM Watson Machine Learning Runs predictive models for propensity scoring, churn detection, and suspicious-transaction analysis.
    • IBM Watson Studio Gives data scientists the environment to build and manage machine-learning models on Cloud Pak for Data.
  2. Storage
    • IBM Netezza Performance Server Acts as the primary enterprise data warehouse and single source of truth for banking data.
  3. Orchestration
    • IBM Cloud Pak for Data Provides the platform where Capital Bank integrates data, builds analytics workflows, and supports machine-learning use cases.

Architecture clues

  • AI models are applied both to growth use cases and to fraud and anti-money-laundering detection.
  • The bank uses dashboard insights from the data stack to troubleshoot mobile-experience issues quickly.
  • The implementation unified critical data from core banking and acquired institutions into a single source of truth.

Evidence from the source

By helping to deliver a smoother experience, our new data stack played a big part in the success of our mobile rollout.
Capital Bank Data Office captured and centralized data from its core banking and 15+ banking applications into the warehouse.
Reduced acquisition-related data migration time by more than 95%
the IBM Cloud Pak for Data platform, along with the Netezza Performance Server as the primary data warehouse, fit the bill best.
using the IBM Watson Machine Learning tool, a capability in IBM Watson Studio on IBM Cloud Pak for Data, the bank’s data scientists are analyzing the correlations between customer demographic and behavior parameters and demand for banking products.
Transparency Evidence & methodology 100/100 reference value · 89% confidence · 1 source

Review how this reference was scored and trace each normalized claim back to its documented source.

01

Scoring methodology

How scores are calculated

Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.

Customer reference value100/100
  • Problem clarity20/20
    Measures whether the customer's operational problem is specific enough to compare.
  • Implementation depth25/25
    Rewards named components, data flow, integrations, and architecture detail.
  • Outcome specificity20/20
    Measures whether the reported benefit is concrete rather than a generic claim.
  • Quantified impact25/25
    2 metrics describe measurable impact.
  • Deployment scale10/10
    Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence89%
  • Source authority20/25
    The main evidence is an official vendor-published customer story.
  • Claim traceability21/25
    10 of 12 key fields link to a named source.
  • Direct evidence20/20
    5 direct source quotes retained.
  • Date provenance10/10
    The publication date comes from the source page or publisher.
  • Source transparency8/10
    1 source reference document publisher, URL, authority, retrieval, and supported fields.
  • Implementation specificity10/10
    Rewards source-backed components, data flow, quantified impact, and a specific outcome.
02

Traceability

Sources & provenance

Field coverage shows which facts each source supports. Dates are shown only when documented by the source.

  1. IBM

    Capital Bank of Jordan customer story

    First-party
    https://www.ibm.com/case-studies/capital-bank
    Source type
    Vendor-published customer story
    Published
    Apr 15, 2024
    Supports
    • Customer
    • Business problem
    • Solution
    • Products
    • Solution components
    • Data flow
    • Integrations
    • technical area
    • use case category
    • Business outcome
    • outcome category
    • Metrics
    • Architecture
    • evidence quotes
    • Publication date

Date evidence

Not separately sourced Industry, Region, Company size. Treat these normalized attributes as lower-confidence until a dedicated source is added.