Detect suspicious card-testing patterns quickly, alert the right people and restrict processing before an automated attack causes more damage.
NMI Card Testing Detection monitors gateway activity for patterns associated with card testing—automated attempts to discover which stolen payment credentials are valid. When NMI’s algorithm detects a suspected event, it can alert configured merchant users and restrict the gateway account while the activity is reviewed.
The feature is an important safety net, but it is not a substitute for website-side bot protection. VCCP helps merchants combine NMI alerts with CAPTCHA, rate limiting, secure checkout design and layered gateway fraud controls.
What Is Card Testing?
Card testing is a form of fraud in which criminals use bots, scripts or compromised credentials to submit many card-not-present transactions—often for small or repeated amounts. An approval tells the attacker that a stolen card may be usable elsewhere.
Even when most attempts decline, the merchant can face authorization fees, operational disruption, chargebacks, processor scrutiny and damage to the customer experience.
Common Warning Signs
- A sudden increase in authorization attempts over minutes or hours
- Large volumes of low-dollar or identical transaction amounts
- Many declines followed by occasional approvals
- Repeated names, generic customer details or related card-number ranges
- Transaction volume far outside the merchant’s normal pattern
- Unexpected API activity or payment attempts on a donation, invoice or hosted-payment workflow
How NMI Card Testing Detection Responds
- NMI monitors gateway activity for patterns its algorithm associates with card testing.
- When a suspected event is detected, NMI restricts the gateway account to suspend transaction processing.
- Configured users receive email alerts and, when enrolled with a confirmed mobile number, SMS notifications.
- An authorized administrator reviews the activity and indicates whether the transactions were intentional.
- If the event was fraudulent, the merchant secures the exposed payment path before the account is unrestricted.
Notification and Access Setup
- Primary merchant users receive the applicable card-testing notification permission by default.
- Additional users can be assigned the Receive Card Testing Notifications permission.
- SMS alerts require a mobile number to be added, confirmed and periodically reconfirmed.
- Only users with the appropriate administrative permission receive the direct option to unrestrict the account.
- Partners are also notified when a merchant is restricted and can review the restriction from the Partner Portal.
Detection Is Only One Layer
NMI states that attackers continually change their methods and not every event can be identified in real time. Merchants should protect the payment path before the transaction reaches the gateway.
Protect the Website or Application
- Place CAPTCHA or comparable bot verification before a customer can reach or submit the payment flow.
- Apply rate limits, velocity controls and temporary blocking to repeated attempts.
- Use secure sessions, CSRF protection, input validation and a maintained web application firewall where appropriate.
- Do not expose unrestricted open-amount payment endpoints without abuse controls.
- Monitor traffic and transaction patterns continuously instead of waiting for the monthly statement.
Layer Gateway Controls
- Require CVV where appropriate and configure AVS responses deliberately.
- Use NMI Fraud Prevention rules, including velocity or approval-rate controls suited to the merchant.
- Consider 3DSService and Kount Advanced Fraud Prevention for compatible ecommerce environments.
- Restrict API access, rotate compromised credentials and use unique user accounts with two-factor authentication.
- Keep processor, gateway and VCCP contact information current so urgent alerts reach the right people.
What to Do After an Alert
- Do not immediately unrestrict the account if the activity appears fraudulent.
- Identify the exposed website, payment link, API user or integration and stop the attack at that entry point.
- Review transaction reports, approvals, refunds, fees and possible cardholder impact.
- Change compromised credentials and add or tighten the applicable bot and fraud controls.
- Coordinate with VCCP, NMI and the processor as needed, then test the secured flow before resuming transactions.
Important Limitations
- Detection can reduce damage but cannot identify or stop every card-testing attempt.
- Restriction interrupts legitimate processing until an authorized merchant or partner user reviews and releases the account.
- Unrestricting an account without securing the exposed payment path can allow the attack to resume.
- Merchants remain responsible for transaction fees, disputes, website security, credential management and compliance obligations.
- Available alerts, permissions and response options can change with NMI account configuration and platform updates.
Related NMI Protection
- Fraud Prevention for configurable gateway screening rules
- Kount Advanced Fraud Prevention for compatible behavioral and risk analysis
- 3DSService for issuer-supported ecommerce authentication
- Webhooks for compatible event-driven monitoring workflows
- Collect Checkout and Collect.js for supported checkout implementations
Card Testing Detection Frequently Asked Questions
What is a card-testing attack?
Card testing is an automated fraud attack in which criminals submit many card-not-present transactions to learn which stolen payment credentials are valid. Attempts often use small or repeated amounts and may produce many declines followed by occasional approvals.
How does NMI Card Testing Detection respond?
When NMI detects a pattern associated with card testing, it can restrict the gateway account and notify configured users. An authorized administrator must review the activity before legitimate processing resumes.
Does Card Testing Detection stop every attack?
No. Detection is a safety net, not a guarantee. Attackers change tactics, and some harmful authorization attempts may occur before a pattern is detected or an account is restricted.
Why is CAPTCHA still needed if NMI monitors card testing?
CAPTCHA or comparable bot verification helps block automated traffic before it reaches the payment gateway. Preventing the attempts at the website or application can reduce authorization fees, disruption and exposure that gateway-side detection alone cannot eliminate.
Where should CAPTCHA be placed on a hosted-payment workflow?
Bot verification should occur before the customer is redirected to or allowed to submit the hosted payment flow. The surrounding website should also use rate limiting, secure sessions and controls appropriate to fixed- or open-amount payments.
What should a merchant do when NMI restricts the gateway?
Review the activity, identify the exposed payment path, stop the attack at its entry point, secure credentials and strengthen the relevant controls. Do not simply unrestrict the account while the vulnerable page or integration remains exposed.
Can card testing create fees even when transactions decline?
Yes. Authorization attempts can create gateway or processor costs even when most cards decline. Approved tests may also lead to refunds, disputes, monitoring and operational disruption.
Protect the Entry Point Before the Next Attempt
Tell VCCP how customers reach your payment page, whether the amount is fixed or open, and which gateway integration you use. We can help identify the controls to review with your website provider, NMI and processor.
Card Testing Detection, notification timing, restrictions, permissions and available controls depend on NMI account configuration and current platform rules. No fraud tool can guarantee that every attack, fee, loss or unauthorized transaction will be prevented.