Velocity Filters are filters housed within the Authorize.Net Fraud Detection Suite, tailored to protect your account from any fraud attempt.
The Suite is housed under Tools on the Home Screen.
In order to ensure a smooth sales flow and exchange relationship between Auth.Net and TicketSearch, we recommend that the following filters be tweaked.
Daily Velocity Filter
Hourly Velocity Filter
Transaction IP Velocity Filter
Daily Velocity Filter
The Velocity Filter allows you to specify a threshold for the number of transactions allowed per day. All transactions exceeding the threshold on that day will be flagged and processed according to the filter action selected below.
Notes:
If you select Authorize and hold for review as the filter action, once the transaction is held for review, we recommend you take action to approve or void the transaction within 72 hours.
You should monitor or review your processing trends over several weeks to help you determine a typical per-day high.
This is set by default to 100 transactions per day, therefore, if sales exceed 100 all other transactions will be held for review for 72 hours then voided. We recommend setting a number based on your estimated highest transactions per day rate. e.g. Highest per day sale is 457 tickets/transactions, therefore, the filter is set to 500. You can also disable the filter altogether.
Hourly Velocity Filter
This Velocity Filter allows you to specify a threshold for the number of transactions allowed per hour. All transactions exceeding the threshold in that hour will be flagged and processed according to the filter action selected below.
Notes:
- If you select Authorize and hold for review as the filter action, once the transaction is held for review, we recommend you take action to approve or void the transaction within 72 hours.
- You should monitor or review your processing trends over several weeks to help you determine a typical per-hour high.
This filter defaults to 100, however, estimate your highest transaction per hour rate and adjust to a number that makes sense following the example given earlier.
Transaction IP Velocity Filter
The Transaction IP Velocity Filter allows you to specify the maximum number of transactions allowed from the same Internet protocol (IP) address per hour. If your account receives more transactions from the same IP address in an hour than the threshold you set, all exceeding transactions received that hour will be flagged and processed according to the filter action selected below.
Notes:
- IMPORTANT: If you submit Advanced Integration Method (AIM) transactions, in order to use this filter you must submit the customer IP address (x_customer_ip) with each transaction.
- If you select Authorize and hold for review as the filter action, once the transaction is held for review, we recommend you take action to approve or void the transaction within 72 hours.
When this function is activated, it monitors for numerous transactions happening in a close time range (1 hour), coming from the same IP address, and flags it as possible fraud. The IP address associated with all customers using the TicketSearch app is 3.19.139.175, therefore this can cause the Transaction IP Velocity Filter to flag TicketSearch transactions on high volume days as fraud, causing funds to be held or transactions to be duplicated, and or canceled.
To ensure your payment gateway (Authorize.Net) functions effectively, we recommended that you update your Transaction IP Velocity Settings, whitelisting the TicketSearch IP Address: 3.19.139.175
To update your settings please follow these steps:
1. Go to Tools - Fraud Detection Suite - Transactions IP Velocity Filter
2. To add an IP address to the IP Address Exclusion list, enter the first set of digits (up to three) of the IP address in the first text field, the next set of digits in the second text field and so on and click Add›› (3.19.139.175)
3. Check the Total IP Address Count box to ensure the IP address is correct
4. Review your pending transactions individually and approve/deny them (deny any duplicated attempts)
Comments
0 comments
Please sign in to leave a comment.