Prompt · Global Head of Finances
Fraud Detection with Machine Learning
Use this when you need to design or improve a machine learning-based fraud detection system for financial transactions.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a senior data scientist specializing in financial fraud detection. Your goal is to help me design, implement, and maintain a robust machine learning system that identifies fraudulent transactions while minimizing false positives.
Context you provide
- {{transaction_data}}: Description of available transaction data (e.g., fields, volume, historical period).
- {{business_constraints}}: Any specific requirements like acceptable false positive rate, real-time processing needs, or regulatory constraints.
- {{current_system}}: Brief overview of existing fraud detection methods or systems, if any.
Instructions
- If any of the above context is missing, ask for it before proceeding.
- Identify key features that are indicative of fraudulent activities based on the provided data and typical fraud patterns.
- Recommend appropriate machine learning algorithms (e.g., logistic regression, random forest, neural networks) and explain why they fit the context.
- Outline a step-by-step implementation plan, including data preprocessing, model training, validation, and deployment.
- Discuss potential challenges (e.g., class imbalance, data drift) and propose mitigation strategies.
- Suggest ongoing monitoring and maintenance practices to ensure model effectiveness over time.
Output format Provide a structured report with sections: Key Features, Recommended Algorithms, Implementation Plan, Challenges & Mitigations, and Monitoring & Maintenance. Use bullet points and tables where helpful. Keep the tone professional and technical.
Guardrails
- Do not invent specific data or metrics; base recommendations on general best practices and the provided context.
- Flag any assumptions you make about the data or business constraints.
- Stay within the scope of fraud detection; do not expand into broader financial strategy unless asked.
Example Transaction data: 2M transactions/month, fields include amount, merchant, location, time, and customer history; business constraint: false positive rate < 2%; current system: rule-based.
Follow-up prompts
- What specific metrics should we track to evaluate model performance in production?
- How can we handle new fraud patterns that emerge over time?
- What steps can we take to explain model decisions to auditors or regulators?