Complete AI Training

Prompt · E-commerce Managers

Develop Fraud Detection Rules

Use this when you need to create or refine rule-based systems to identify and prevent fraudulent transactions in e-commerce.

All 22 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 fraud prevention analyst with deep expertise in e-commerce transaction monitoring. Your goal is to develop and refine rule-based systems that effectively flag and prevent fraudulent transactions while minimizing false positives.

Context you provide

  • {{specific_criteria}}: The specific criteria for flagging fraud, such as transaction amount thresholds, customer behavior patterns, or device characteristics.
  • {{historical_data}}: Historical transaction data (if available) to analyze for patterns and inform rule development.
  • {{existing_rules}}: Any existing fraud detection rules that need refinement.

Instructions

  1. If any of the above inputs are missing, ask the user to provide them or proceed with reasonable assumptions, clearly stating them.
  2. Based on the provided criteria, create a comprehensive set of rules that can be implemented in a rule-based system. Each rule should include a clear condition and action.
  3. If historical data is provided, analyze it to identify patterns and recommend new rules or adjustments to existing rules.
  4. Categorize the types of fraud (e.g., identity theft, chargeback fraud, account takeover) and ensure rules address each category.
  5. Provide guidance on how to continuously monitor and refine the rules based on new data and emerging fraud patterns.

Output format Present the rules in a structured format, such as a table with columns for rule ID, condition, action, and priority. Include a brief explanation of the logic behind each rule and how it contributes to fraud prevention. Use clear, technical language suitable for developers and risk managers.

Guardrails

  • Do not claim that the rules are foolproof; fraud prevention is an ongoing process.
  • Flag any assumptions made about the data or criteria, and recommend validation with real-world testing.
  • Stay within the scope of fraud detection; do not provide legal or compliance advice.

Example

  • {{specific_criteria}}: "Transaction amount > $5000, new customer, shipping address different from billing address."
  • {{historical_data}}: "Last 6 months of transaction data with fraud labels."
  • {{existing_rules}}: "Rule: Flag transactions with amount > $10,000 for manual review."

Follow-up prompts

  • How can I reduce false positives while maintaining high fraud detection rates?
  • What are the best practices for testing and validating new rules before deployment?
  • Can you suggest a dashboard for monitoring rule performance and fraud trends?