--- title: "Payments and Authorize.net Fraud Detection Filters" slug: "payments-and-authorizenet-fraud-detection-filters" description: "Optimize your Authorize.net Fraud Detection Settings to prevent transaction declines and ensure smooth auto-billing for your e-commerce business." updated: 2025-08-11T19:57:58Z published: 2025-08-11T19:57:58Z canonical: "www.civicplus.help/payments-and-authorizenet-fraud-detection-filters" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://www.civicplus.help/llms.txt > Use this file to discover all available pages before exploring further. # Payments and Authorize.net Fraud Detection Filters If you are planning on using e-commerce with Authorize.net and Payments, you will want to look over your Fraud Detection Settings. ## Daily and Hourly Velocity Filters If you have your daily and hourly velocity set and they are set too low and to ‘decline’, you will run into issues with auto-billing. For example, if you have your hourly velocity filter set to 100 transactions, and you have 2,500 memberships to process, 2,400 of your invoices will fail to process. You will need to set your hourly velocity filter higher than your auto-billing and allow yourself some room for growth. ![Daily vector.](https://cdn.us.document360.io/17dc564a-8310-4f61-b929-1bd73b36e158/Images/Documentation/360100137653.png?sv=2026-02-06&spr=https&st=2026-11-22T12%3A43%3A40Z&se=2026-11-22T13%3A43%3A40Z&sr=b&sp=r&sig=8u22hPL2nRHOh2HUlmykgMNm6AtATJmJKK0fD6aLH6M%3D) You will also need to set your Daily Velocity Filter high enough to accommodate your normal transaction, plus your auto-billing. ![Hourly vector.](https://cdn.us.document360.io/17dc564a-8310-4f61-b929-1bd73b36e158/Images/Documentation/360100137633.png?sv=2026-02-06&spr=https&st=2026-11-22T12%3A43%3A40Z&se=2026-11-22T13%3A43%3A40Z&sr=b&sp=r&sig=xF%2FpTvO2RXLrmwaFZQdNbCU0nUHPx6w8DfGeGTxA5kY%3D) ## Transaction IP Velocity Filter When using eCommerce with Payments, all transactions are going to show as coming from the CivicPlus Payments . You can either allowlist the CivicPlus Payments IP ([contact Support](/recreation-management/docs/contact-support) to get this), not enable this filter, enable and set to allow, or set this filter high enough to accommodate spikes. For example, if you have a large registration day and you have 1,000 sign-ups for your summer programs on opening day, you will need to set this filter high enough to accommodate that spike. ![Transaction IP.](https://cdn.us.document360.io/17dc564a-8310-4f61-b929-1bd73b36e158/Images/Documentation/360100137593.png?sv=2026-02-06&spr=https&st=2026-11-22T12%3A43%3A40Z&se=2026-11-22T13%3A43%3A40Z&sr=b&sp=r&sig=Jiyzmxgzl4GLRL1UmRcRjdeZYcDiunMaO1uiwMgMoG4%3D) ## FDS Filter Actions Authorize.net does have the option for you to choose between the following filter actions: 1. **Process as normal and report filter(s) trigger:** You will get an email letting you know that the filter was triggered 2. **Authorize and hold for review:** This sends an Fraud Detection System (FDS)-triggered method to CivicPlus Payments, which is not a successful message. The user will be charged but will not be given a receipt 3. **Do not authorize, but hold for review:** If you choose this option, the user will not be given a Recreation Management receipt. If you accept payment, you will not be able to tie back to a Recreation Management receipt 4. Decline the transaction ## Authorized API IP Addresses This filter will block CivicPlus Payments even if you allowlist Payment’s . ![Authorized API.](https://cdn.us.document360.io/17dc564a-8310-4f61-b929-1bd73b36e158/Images/Documentation/360100137613.png?sv=2026-02-06&spr=https&st=2026-11-22T12%3A43%3A40Z&se=2026-11-22T13%3A43%3A40Z&sr=b&sp=r&sig=TLAMq0W750CEh1wyflT6U5GIl1UEyUBgZ%2F%2FkaMr%2FuvY%3D)