Baselight

Fraudulent Transactions Data

Fraudulent transactions data for a financial company

@kaggle.chitwanmanchanda_fraudulent_transactions_data

Loading...
Loading...

About this Dataset

Fraudulent Transactions Data

Context

Develop a model for predicting fraudulent transactions for a financial company and use insights from the model to develop an actionable plan. Data for the case is available in CSV format having 6362620 rows and 10 columns.

Content

Data for the case is available in CSV format having 6362620 rows and 10 columns.

Data Dictionary:

step - maps a unit of time in the real world. In this case 1 step is 1 hour of time. Total steps 744 (30 days simulation).

type - CASH-IN, CASH-OUT, DEBIT, PAYMENT and TRANSFER.

amount - amount of the transaction in local currency.

nameOrig - customer who started the transaction

oldbalanceOrg - initial balance before the transaction

newbalanceOrig - new balance after the transaction

nameDest - customer who is the recipient of the transaction

oldbalanceDest - initial balance recipient before the transaction. Note that there is not information for customers that start with M (Merchants).

newbalanceDest - new balance recipient after the transaction. Note that there is not information for customers that start with M (Merchants).

isFraud - This is the transactions made by the fraudulent agents inside the simulation. In this specific dataset the fraudulent behavior of the agents aims to profit by taking control or customers accounts and try to empty the funds by transferring to another account and then cashing out of the system.

isFlaggedFraud - The business model aims to control massive transfers from one account to another and flags illegal attempts. An illegal attempt in this dataset is an attempt to transfer more than 200.000 in a single transaction.

Inspiration

Following tasks & questions can be answered using the data,

  1. Data cleaning including missing values, outliers and multi-collinearity.
  2. Describe your fraud detection model in elaboration.
  3. How did you select variables to be included in the model?
  4. Demonstrate the performance of the model by using best set of tools.
  5. What are the key factors that predict fraudulent customer?
  6. Do these factors make sense? If yes, How? If not, How not?
  7. What kind of prevention should be adopted while company update its infrastructure?
  8. Assuming these actions have been implemented, how would you determine if they work?

Tables

Fraud

@kaggle.chitwanmanchanda_fraudulent_transactions_data.fraud
  • 268.55 MB
  • 6362620 rows
  • 11 columns
Loading...

CREATE TABLE fraud (
  "step" BIGINT,
  "type" VARCHAR,
  "amount" DOUBLE,
  "nameorig" VARCHAR,
  "oldbalanceorg" DOUBLE,
  "newbalanceorig" DOUBLE,
  "namedest" VARCHAR,
  "oldbalancedest" DOUBLE,
  "newbalancedest" DOUBLE,
  "isfraud" BIGINT,
  "isflaggedfraud" BIGINT
);

Share link

Anyone who has the link will be able to view this.