CATCHM
Code repository for the paper: CATCHM: A novel network-based credit card fraud detection approach using node representation learning
Requirements:
The code has been tested under Python 3.6. The required packages can be installed using the following command:
$ pip install -r requirements.txt
To guarantee that you have the right package versions, you can use Anaconda to set up a virtual environment and install the dependencies from requirements.txt.
Running the code
Step 1: Download the dataset
The data used in the paper is confidential and cannot be made publicly available. However, a transaction fraud dataset is available on Kaggle. The structure and characteristics are very similar to the data from our paper.
You can download the dataset from Kaggle: https://www.kaggle.com/ranjeetshrivastav/fraud-detection-dataset
Make sure to unzip and store the 'transactions' folder someplace easily accessible.
Step 2:
The demo code is available as a Jupyter Notebook. There are two notebooks:
- deepwalk_demo.ipynb
- pagerank_demo.ipynb
The first notebook contains the deepwalk approach with inductive mean pooling extension. The embeddings are used to train an XGBoost classification model. The second notebook contains the inductive pagerank approach [2] and serves as a benchmark. More details on this benchmark can be found in [2].
Both notebook files can be opened with Jupyter Notebook
jupyter notebook
References
[1] Van Belle Rafael, De Weerdt Jochen. "A novel network-based credit card fraud detection approach using noderepresentation learning."
[2] Van Vlasselaer, Véronique, Cristián Bravo, Olivier Caelen, Tina Eliassi-Rad, Leman Akoglu, Monique Snoeck, and Bart Baesens. 2015. “APATE: A Novel Approach for Automated Credit Card Transaction Fraud Detection Using Network-Based Extensions.” Decision Support Systems 75 (July): 38–48.
Metadata
Release files for CATCHM 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| CATCHM-0.1.tar.gz | 5.7 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| CATCHM-0.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 13.1 kB
Release files / CATCHM-0.1.tar.gz
| Download URL | CATCHM-0.1.tar.gz |
|---|---|
| Size | 5.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d6548b3424539099fa3129421053532603410adead3325684ea4c57cafee8019
|
|
BLAKE2b-256 checksum How to use checksums |
557af576c78b96cd7d7c022cc5754aa39c9f1fd89188b269ca2218ed7ac789d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.7.4
|
Release files / CATCHM-0.1-py3-none-any.whl
| Download URL | CATCHM-0.1-py3-none-any.whl |
|---|---|
| Size | 7.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f85e3cf0e896f6f242ee598681061dc2dde6d3495bc92e53be04911f6a4cead0
|
|
BLAKE2b-256 checksum How to use checksums |
6601a963b0f1251bd0502a8965f6da25b44c3a00f5eac7b6de9853d89050ec58
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.6.0 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.7.4
|
Security for CATCHM 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.