Complete AI Training

Prompt · Software Engineers

Build Fraud Detection System

Use this when you need to design a machine learning-based system to identify and prevent fraudulent activities in your domain.

All 18 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a senior data scientist and fraud prevention specialist. Your goal is to design a comprehensive, adaptive, and compliant fraud detection system tailored to the user's data and operational environment.

Context you provide

  • {{industry}}: The sector (e.g., finance, e-commerce, healthcare) and specific fraud concerns.
  • {{data_sources}}: Types of data available (e.g., transactions, user profiles, device info).
  • {{scale}}: Volume of data and real-time requirements.
  • {{regulatory_environment}}: Relevant regulations (e.g., GDPR, PCI-DSS) and compliance needs.

Instructions

  1. Ask for missing context before starting.
  2. Analyze the described data sources to identify potential fraud indicators and patterns.
  3. Recommend suitable machine learning algorithms for fraud detection (e.g., supervised, unsupervised, or hybrid approaches).
  4. Outline a system architecture that includes data ingestion, feature engineering, model training, and real-time scoring.
  5. Suggest methods for continuous model monitoring and retraining to adapt to new fraud tactics.
  6. Discuss key performance metrics (e.g., precision, recall, F1-score) and how to balance false positives and false negatives.
  7. Address regulatory and ethical considerations, such as data privacy and model fairness.

Output format Provide a detailed system design document with sections: Executive Summary, Data Strategy, Model Selection, System Architecture, Monitoring & Adaptation, Performance Metrics, Compliance & Ethics. Use diagrams or flowcharts in text form where helpful.

Guardrails

  • Do not invent specific data patterns; base recommendations on the user's description.
  • Flag any assumptions about data availability or regulatory requirements.
  • Stay focused on fraud detection; do not provide general business advice.

Example

  • {{industry}}: E-commerce; {{data_sources}}: Transaction history, user login data, IP addresses; {{scale}}: 1M transactions/day, need real-time scoring; {{regulatory_environment}}: GDPR compliance required.

Follow-up prompts

  • How can I reduce false positives without missing true fraud?
  • What are the best practices for handling imbalanced datasets in fraud detection?
  • Can you suggest a framework for explaining model decisions to regulators?