Using the Helcim Fraud Defender
    • 04 Mar 2025
    • 2 Minutes to read

    Using the Helcim Fraud Defender


    Article summary

    Worried about fraudulent transactions? Helcim Fraud Defender is here to help you assess the risk of online payments, giving you peace of mind and helping to prevent losses for your business.


    In this article

    What is Helcim Fraud Defender?


    Helcim Fraud Defender analyzes seven key transaction factors to provide a risk assessment for online, customer-initiated payments.

    This assessment is presented as a confidence score, ranging from 1.0 (high risk) to 10.0 (low risk). Think of it as a helpful tool that gives you a quick snapshot of potential risks.  

    It's important to remember that this score is an estimation, not a guarantee. While it's a powerful tool, you'll still want to review all your transactions.

    And of course, using Helcim Fraud Defender means you agree to our Terms of Service.

    Transaction confidence score scale

    Enabling Helcim Fraud Defender


    Ready to get started? Here's how to enable Helcim Fraud Defender:

    1. Go to All Tools (top-left corner) and select Settings

    2. Select Helcim Defender under "Security Settings."

    3. Toggle the Defender Status on. This activates the risk assessment feature.

    4. Configure your settings for Ecommerce | Automatic Protection:

      1. AVS Auto-Void: Turn this on to automatically void transactions if the Address Verification Service (AVS) doesn't match.

      2. Accepted AVS: Select the AVS response codes you want to accept.

      3. Defender Auto-Void: Turn this on to automatically void transactions below your chosen score threshold.

      4. Score Minimum: Set the minimum score (out of 10) that will trigger an automatic void.

    5. Click Save to apply your changes.

    Settings page with Helcim Defender settings highlighted.

    Helcim Defender settings page.

    How to view confidence scores


    You can easily view the confidence score in your Helcim transaction details. To get there:

    • Log in to your Helcim dashboard

    • Go to the Payments tool

    • Open the Transactions tab

    • Select a specific transaction

    • Select the Risk insights tab (visible if Fraud Defender is enabled)

    For Helcim API users, confidence scoring is also available when the ecommerce flag is set to "True."

    For a deeper dive, you can click on each dropdown within risk insights to see detailed information about the Fraud Defender analysis. This allows you to make informed decisions about potentially risky transactions.

    Transaction view with risk insights tab highlighted.

    Understanding the calculated risk factors


    Here's a breakdown of the seven factors Helcim Fraud Defender considers:

    1. CVV security code: Checks if the customer entered the card's security code.

    2. Address Verification Service (AVS): Verifies if the billing address matches the cardholder's bank records.

    3. Transaction size: Compares the current transaction size to your average transaction size.

    4. Billing & shipping: Checks if the billing and shipping addresses match.

    5. Shipping location: Verifies if the shipping destination is in the same country as the billing address.

    6. Bank BIN: Checks if the cardholder's bank is in the same country as the billing address.

    7. IP address location: Verifies if the customer's IP address matches the billing address location.

    Next steps


    Now that you understand how Helcim Fraud Defender works, take some time to review your risk insights. Adjust your Helcim Defender settings and customize them to fit your business needs.

    Regularly checking your risk assessments will help you stay ahead of potential fraud.


    FAQs & troubleshooting

    What does a score of 0 mean?

    A score of 0 means there wasn't enough data to perform a full analysis. This doesn't necessarily indicate fraud, but simply that the necessary information was missing. Also, please note that fraud analysis is not performed on transactions that decline due to issues such as NSF and card expiry.


    Was this article helpful?