Black Friday falls on November 27 this year, and for merchants on Authorize.Net and NMI the gateway settings that matter most over the holiday weekend are the ones that decide what happens when a bot starts firing stolen card numbers at checkout. Both gateways publish step-by-step help for these controls. The list below sticks to settings whose location is documented by Authorize.Net or NMI, so a store owner or developer can check each one before Thanksgiving week.
Card testing, where fraudsters run large numbers of stolen cards through a store with small charges to see which ones work, is the main threat these settings address. NMI’s card testing guide describes the pattern as hundreds to thousands of card-not-present requests within minutes, often for the same low amount, and warns that it can bring large transaction fees and chargeback fees.
Authorize.Net
The paths below are for the New Merchant Interface (2.0). Authorize.Net’s own Advanced Fraud Detection Suite (AFDS) article places the fraud filters under Account, then Account and API Settings, then Advanced Fraud Detection Suite Settings, where Configure opens each filter. EC4IM covered these filters in more depth in Authorize.Net AFDS settings for card testing.
1. Confirm AFDS is actually on
Only the account owner can enable AFDS, through Marketplace and the Available Products tab. Authorize.Net says some accounts have it switched on at activation. If the owner is not the person running the store day to day, this is the week to find out which applies.
2. Set the Daily and Hourly Velocity Filters from real volume
The Daily Velocity Filter caps how many transactions the account accepts in 24 hours, and the Hourly Velocity Filter does the same per hour. Authorize.Net’s configuration help suggests basing each threshold on weekly or monthly volume history. A limit built from an ordinary week can trip on genuine Black Friday orders, so the history worth pulling is last year’s holiday weekend.
Each filter offers four actions: process as normal and report, authorize and hold for review, do not authorize but hold for review, or decline. When a transaction trips several filters, Authorize.Net applies the most severe action. Authorize.Net says the report-only option is useful for testing a threshold before it starts blocking sales.
3. Make sure the Transaction IP Velocity Filter can see IP addresses
This filter limits how many transactions one IP address can submit per hour, which is closer to how a card-testing script behaves. It only works if the integration sends the shopper’s IP address. Authorize.Net says API users must include the customerIP field, so a developer should confirm the cart or plugin passes it.
4. Turn on the Suspicious Transaction Filter and an Amount Filter floor
The Suspicious Transaction Filter flags transactions using Authorize.Net’s own criteria. The Amount Filter sets lower and upper limits, and Authorize.Net describes it as a way to restrict the small charges often used to test cards. The company cautions against setting the upper limit too tightly, since a customer may buy several higher-priced items in one order.
5. Review AVS and card code handling
The Enhanced AVS Handling Filter and Enhanced CCV Handling Filter let a merchant flag or hold transactions based on the Address Verification Service (AVS) and card code responses, rather than only accepting or rejecting them.
6. Turn on CAPTCHA if the store uses Accept Hosted
Authorize.Net’s hosted payment form, Accept Hosted, has a hostedPaymentSecurityOptions setting that adds CAPTCHA to the form. It defaults to off, so the cart or plugin has to request it when it asks for the form token. Stores that collect cards another way would need a CAPTCHA on their own page, which Authorize.Net’s fraud prevention tips also suggest. EC4IM reported on hosted form CAPTCHA failures in August, which is worth reading before switching it on during a peak week.
7. Check the Transaction Cut-Off Time
The cut-off time decides when the day’s transactions are picked up for settlement. Authorize.Net’s New Merchant Experience FAQ puts it under Account, Account and API Settings, Transaction Settings, Transaction Cut-Off Time. Authorize.Net advises reviewing transactions before settlement and voiding suspicious ones while they are still unsettled, so staff should know exactly when that window closes over the long weekend.
8. Clean up the user list
Owners and administrators manage logins under Account, then Manage Users, where each user’s role and individual permissions can be edited and former staff can be deleted. Changes require a one-time PIN sent by email or text.
NMI
NMI’s settings sit in the Merchant Portal. Some are included with every gateway account, and Fraud Prevention is a paid add-on.
9. Put a mobile number on the card testing alerts
NMI runs automated Card Testing Detection. When it spots an attack it restricts the account, which stops all processing, and alerts primary users by email and text. Text alerts only go to users who have entered a mobile phone number in User Accounts. A restricted account cannot take a single sale until someone reviews the alert and releases it, so a holiday weekend is a bad time for that alert to reach an unmonitored inbox.
10. Set AVS and card ID rules for each processor
NMI places Address Verification and Card ID Verification under Settings, then Security Options. Its card ID verification article notes that a merchant with more than one processor has to set rules for each one through the processor dropdown, and that separate rules can apply to non-U.S. cards. NMI lists making the card verification value (CVV) a required field among its card testing defenses.
11. Review Fraud Prevention thresholds if the service is active
Merchants who pay for Fraud Prevention reach it under Other Services, and the user needs the Access Fraud Prevention permission. Thresholds can be set by day, week, month or year, by transaction count or value. “Attempted” rules count every submission, including declines, while “Approved” rules count only successful charges. Because card testing generates large numbers of declines, only attempted rules count the full volume of an attack. Each rule can flag a transaction for review or deny it. NMI says Fraud Prevention cannot stop a bot from reaching the website itself, because transactions have to arrive at the gateway before the rules apply.
12. Lock down logins and keys
NMI’s card testing guide recommends separate user accounts instead of shared passwords (Settings, General Options, User Accounts), two-factor authentication, IP restrictions on who can log in to the control panel and API, and rotating API keys under Settings, Security Options, Security Keys. The same guide recommends a CAPTCHA on the store’s checkout. EC4IM’s earlier piece on rotating gateway keys after a WordPress compromise covers why old keys are a risk.
A short list worth finishing before Thanksgiving
On both gateways, the settings that matter over Black Friday weekend fall into three groups: limits that slow a flood of attempts, verification rules that catch mismatched cards, and housekeeping that decides who gets alerted and who can log in. Every item above is documented by the gateway itself, and each works only if it is in place before the first holiday order arrives, not after a card-testing run turns up in the settlement report.
Sources
- Authorize.Net, What is Advanced Fraud Detection Suite (AFDS) and how to enable and use it? New Experience (2.0)
- Authorize.Net, Enabling, Disabling, and Configuring Filters in the AFDS
- Authorize.Net, Hourly Velocity Filter
- Authorize.Net, Accept Hosted API documentation
- Authorize.Net, Managing Suspicious Transactions and Fraud Prevention Tips
- Authorize.Net, New Merchant Experience (2.0) FAQ
- Authorize.Net, How Account Owners and Administrators can add and manage users in the Merchant Interface
- NMI, How to Protect your Account from Card Testing
- NMI, Card Testing Detection
- NMI, Card ID Verification Settings (CVV)
- NMI, Fraud Prevention