> For the complete documentation index, see [llms.txt](https://academy.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.pentaho.com/pentaho-data-integration/use-cases/machine-learning.md).

# Machine Learning

Algorithms .. Credit Card Fraud

{% hint style="info" %}

#### **Machine Learning**

The machine learning use case in Pentaho Data Integration addresses credit card fraud detection, a critical business challenge where organizations typically lose about 5% of their yearly revenue to fraudulent activities\*.

This hands-on lab demonstrates three powerful approaches to fraud detection:

First, it teaches how to use H2O (AutoML) to automatically discover well-performing machine learning models without extensive manual tuning.

Second, it covers supervised learning algorithms that can detect fraudulent behavior by learning patterns from historical fraud cases.

Third, it explores unsupervised learning methods to identify new, previously unseen types of fraud activities.

A key focus of this use case is handling imbalanced datasets, which is essential since fraudulent transactions are rare compared to legitimate ones. The use case provides practical techniques for properly classifying data when dealing with this common real-world challenge, ensuring that machine learning models can effectively identify fraud without being overwhelmed by the volume of normal transactions.

\*Association of Certified Fraud Examiners (ACFE) "Occupational Fraud 2024: A Report to the Nations," published in March 2024
{% endhint %}

{% embed url="<https://www.loom.com/share/cc869ef3f59a412b8cdfd53baaba2ea6?hideEmbedTopBar=true&hide_owner=true&hide_share=true&hide_title=true>" %}
Lab Overview
{% endembed %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://academy.pentaho.com/pentaho-data-integration/use-cases/machine-learning.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
