IBM Financial Services Vietnam

TPBank

Sales Automation

TPBank had modernized its data estate on IBM Cloud Pak for Data, but a digital credit-card acquisition program was still converting below expectations and the bank needed faster, repeatable model-development workflows to turn transaction data into higher-quality leads and broader AI use cases.

12 million corporate and individual customers in Vietnam
15 data science and machine learning models developed and deployed with CP4D in 2024
24% conversion rate of credit card propensity model
processed up to 25 GB data from transactional structured data sources

Reported impact

Business outcome

The bank increased credit-card conversion, shortened model build and deployment cycles, and used the same IBM stack to put more than 15 analytics and machine learning models into production during 2024.

  • Productivity Improvement
  • Revenue Growth
  • Speed to Market

Solution

TPBank expanded the data platform it had already built on IBM Cloud Pak for Data by using IBM Watson Studio, IBM Watson Machine Learning, IBM Watson Pipelines, and IBM Analytics Engine to operationalize customer propensity modeling. The bank’s data team processed up to 25 GB of structured transactional data through a CRISP-DM workflow covering preparation, feature engineering, model development, and deployment, then used the resulting propensity models inside its digital banking channel to identify credit-card prospects while protecting credit quality. Cloud Pak for Data gives the team a shared foundation for building and deploying data-science assets, and the surrounding Watson components reduce the handoff and operational overhead required to move models into production. Over three years the same platform also helped TPBank build a broader data-fabric capability and scale analytics products across the bank rather than treating each model as a one-off effort.

Data flow

TPBank ingests up to 25 GB of structured transactional data into Cloud Pak for Data, applies feature engineering and propensity modeling through Watson Studio, Watson Machine Learning, and Watson Pipelines, and then deploys the resulting scores into the bank’s digital channel to target likely credit-card applicants and support broader analytics products.

Solution architecture

6 components · 2 layers
  1. Compute
    • IBM Watson Studio Supports development of the credit-card propensity models used to identify likely prospects.
    • IBM Watson Machine Learning Runs and operationalizes machine learning models for production business use.
    • IBM Analytics Engine Contributes analytics processing that helps the bank scale data science use cases across operations.
  2. Orchestration
    • IBM Cloud Pak for Data Provides the bank’s shared data and AI platform for model development, deployment, and ongoing analytics modernization.
    • IBM Watson Pipelines Coordinates the steps needed to prepare data and deploy new models efficiently.
    • IBM Red Hat OpenShift Supplies the container platform underpinning the deployed IBM data and AI environment.

Architecture clues

  • Over three years TPBank also built a data fabric platform to support customer insights and data products.
  • The bank uses a CRISP-DM approach for the propensity modeling workflow.
  • The implementation followed a four-step flow: data preparation, feature engineering, model development, and model deployment.

Evidence from the source

“15 data science and machine learning models developed and deployed with CP4D in 2024”
“24% conversion rate of credit card propensity model”
“Since 2021, Tien Phong Commercial Joint Stock Bank (TPBank) has been using IBM Cloud Pak for Data (CP4D) to modernize the bank’s data infrastructure.”
“To address this problem, the TPBank data team developed Credit Card Propensity models using IBM Watson Studio, IBM Watson Machine Learning and IBM Watson Pipelines.”
“the bank reduced the development and operation time of new models by 30% to 40%.”
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
    3 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

    TPBank customer story

    First-party
    https://www.ibm.com/case-studies/tien-phong-commercial-joint-stock-bank
    Source type
    Vendor-published customer story
    Published
    Dec 20, 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.