Skip to main content

Search

We are excited to announce the launch of updated product names, logos, and headers within our user interfaces as part of the CivicPlus® Solution Rebranding initiative. These changes mark the first step toward creating a cohesive and seamless user experience across all solutions in our portfolio. As part of this transition, users may notice minor design updates. While the functionality you rely on remains unchanged, we are in the process of updating screenshots and other resources on our Help Centers to reflect the new branding. We appreciate your patience and understanding as we work to complete these updates.

CivicPlus Pay and Authorize.net Fraud Detection Filters

  • Updated:

If you are planning on using e-commerce with Authorize.net and CivicPlus Pay, you will want to look over your Fraud Detection Settings.  

  

Daily and Hourly Velocity Filters

If you have your daily and hour 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

 

You will also need to set your Daily Velocity Filter high enough to accommodate your normal transaction plus your auto-billing.

 

hourly vector

 

Transaction IP Velocity Filter

When using e-commerce with CivicPlus Pay, all transactions are going to show as coming from the Pay IP address. You can either whitelist the CivicPlus Pay IP (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

 

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 FDS triggered method to Pay 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 CivicRec receipt. If you accept payment, you will not be able to tie back to a CivicRec receipt.
  4. Decline the transaction

 

Authorized API IP Addresses 

This filter will block CivicPlus Pay even if you whitelist Pay’s IP address.

 

authorized API

Comments

Let us know what was helpful or not helpful about the article.

0 comments

Please sign in to leave a comment.