Authorize.Net Fraud Detection Settings
Make sure the Fraud Detection settings on your account will allow you to process your event night transactions!.
Typical Event Night transactions can look suspicious and WILL trigger Auth.net's fraud flags:
- An unusually high number of transactions in a single day and/or hour. . .
- An unusual number of transactions submitted from a single IP address (laptop). . .
And stringent Address/CVV matching settings are likely to result in failures of legitimate transactions and frustration among your supporters.
Because security tools are being added and revised continuously - you should review your Auth.net settings before each event - even if you've used the same account for years
A. Reviewing your Fraud settings in "New Authorize.net"
Authorize.net is rolling out a major overhaul of their website. If the images below do not match your view - scroll down to view instructions illustrated on Auth.net's retiring layout.
1a. Login to your Auth.net account
Go to: Account > Account and API Settings > Card Testing Settings AND Transaction Settings > Configure
2a. Set All Card Testing Settings to "Process as Normal and Report Filter(s) Triggered"
3a. Set Address Verification Setting (AVS) Filters to "Process as normal"
Important! If your ticket forms do not collect complete billing address information for each guest (via required fields), your AVS settings MUST be lowered.
4a. Recommended Card Code Verification (CCV) Settings:
B. Reviewing your Fraud settings in "retiring" Authorize.net
1b. Login to your Authorize.net account
Go to: Tools > Fraud Detection Suite
2b. Set All Card Testing Settings to "Process as Normal and Report Filter(s) Triggered"
3b. Set Address Verification Setting (AVS) Filters to "Allow":
Important! If your ticket forms do not collect complete billing address information for each guest (via required fields), your AVS settings MUST be lowered.
4b. Recommended Card Code Verification (CCV) Settings:
