Tech Support Ads That Get Merchant Accounts Terminated

On this page 6 sections

1. Why Processors Treat Tech Support Advertising Compliance as Underwriting
2. Google and Microsoft Ads Restrictions on Third-Party Tech Support
3. Pop-Up Warnings and Fake Virus Alerts: Automatic Termination Triggers
4. Pay-per-Call Leads and Affiliates: Your Liability for Their Tactics
5. Disclosures That Make Clear You're Independent
6. Auditing Your Lead Sources Before an Underwriter Does

Key takeaways

• A disclaimer won't fix a manufacturer-name keyword. Callers who searched for the manufacturer still think they reached it, so drop those keywords and add them as negatives.
• You don't need to build a fake virus pop-up to be tied to one. A lead vendor's traffic can put your number on it, and callers reading "error codes" off their screen are the warning sign.
• A separate tracking number for every lead source lets you trace each chargeback back to the vendor that sent the caller.
• Telling callers their manufacturer may offer free warranty support costs some sales. It also removes the strongest argument a cardholder could make in a later dispute.

For tech support merchants, how you find customers can matter as much to your processor as the service itself. Tech support advertising compliance covers the search ads, pop-ups, bought phone calls and affiliate traffic that bring people to your line. If an underwriter finds a fake virus warning, or an ad that reads as if you are Microsoft, expect the account to close no matter how good your technicians are. Firms that keep their accounts limit themselves to channels they can document. They complete whatever ad platform verifications apply to them, and they say plainly, in every channel, that they are independent.

Why Processors Treat Tech Support Advertising Compliance as Underwriting

Remote tech support is underwritten as high risk because the category has a long record of scams aimed at older consumers. The usual pattern runs like this:

1. An alarming message appears on the screen with a phone number.
2. The caller believes they have reached the manufacturer.
3. They read a card number over the phone for a "repair" the computer never needed.

A scam call and an honest one can look identical on a receipt. The difference is in how the customer arrived.

That is why the bank that sponsors your merchant account cares about your marketing. The acquiring bank answers to Visa and Mastercard for the merchants it boards. Payment companies also take on regulatory risk when they keep processing for deceptive operations after the warning signs are visible. Our piece on the FTC's knowledge test for payment processors explains why processors now cut merchants faster when the marketing looks wrong. For a tech support firm, that means questions about your ads at application and monitoring afterward.

Most of your sales are keyed over the phone or taken online, so every one is card-not-present. When a customer later says "I was tricked," the dispute points back to your advertising. A run of those disputes from older cardholders, or from their adult children, tells a risk team more than your website does. Our guide to refund policies when seniors' families dispute charges covers that side.

Google and Microsoft Ads Restrictions on Third-Party Tech Support

"Third-party technical support" means help with computers, printers or software a business didn't make. Google restricts ads for this kind of service and may require advertisers to complete verification before their ads run. Microsoft Advertising restricts tech support advertising under its own policies.

Both platforms revise these rules, so don't rely on a secondhand summary of them, including this one. Before you launch or change a campaign, read the current policy text in each platform's help center. Keep a dated copy of the version you relied on.

Underwriters read your ad accounts as evidence. Proof that you completed the platform verifications that apply to you, plus a clean policy history, counts in your favor. Running tech support ads while avoiding a platform's review counts heavily against you. That includes borrowing a reseller's account or labeling the business "computer repair" to get past screening, and processors read either one as intent to deceive. Those workarounds can also break the platforms' terms. Don't use them.

Two points are often misunderstood:

• Ad verification is not processor approval. Passing a platform's advertiser check shows the business is real. It tells a bank nothing about how your calls are handled once the phone rings.
• An ad platform disapproval is an early warning. If Google or Microsoft rejects your ads for misrepresentation, assume your processor will hear about the same problem through disputes. Fix the cause before you appeal.

Keyword choices matter as much as ad copy. Bidding on searches like "HP printer support number" or "Microsoft help phone" puts your number in front of people who want the manufacturer. A disclaimer in the ad doesn't change who those callers think they reached, and they are the cardholders most likely to file a fraud dispute. Build campaigns around the problem instead: "printer won't connect to Wi-Fi," "slow laptop repair," "home network setup help." Then add manufacturer names as negative keywords.

Pop-Up Warnings and Fake Virus Alerts: Automatic Termination Triggers

Some tactics are judgment calls. This one is not. Processors end the relationship over any of these:

• A pop-up or browser lock screen telling someone their computer is infected and to call a number.
• A fake scan result.
• An audio alarm with the same message.

This is the tactic most associated with tech support scams, and processors treat it as deception on its face. A termination for this kind of deception can also put your business on the shared list of terminated merchants that acquirers check before boarding a new account. That listing follows the business and its principals into future applications.

You don't have to build the pop-up yourself to be tied to it. If a lead vendor buys traffic from shady ad networks, your phone number can end up on a fake warning screen you never saw. These signs suggest that is happening:

• Calls spike late at night or arrive in bursts that don't match your ad schedule.
• Callers read out an "error code" or a "support ID" from their screen.
• Callers describe a frozen browser, a beeping sound or a warning they can't close.
• Callers open with "Is this Microsoft?" or "Is this Apple?"

Softer versions of the same idea also draw scrutiny. Examples include display ads styled like system dialogs, "Your PC may be at risk" banners and countdown timers urging an immediate call. If a creative would alarm a 75-year-old who doesn't know what a browser is, don't run it.

Pay-per-Call Leads and Affiliates: Your Liability for Their Tactics

Tech support lead generation usually means a pay-per-call network or a group of affiliates. You pay for each qualified call or each sale, and the vendor sources traffic from publishers you never meet. The model rewards aggressive tactics, and that is the core of tech support affiliate marketing risk.

Many owners assume an affiliate's ad is the affiliate's problem. Your processor and the law tend to disagree. Merchant agreements generally make you responsible for marketing done on your behalf. Consumer protection law can also reach a business that profits from deceptive marketing by its lead sources. Treat that as general information and have an attorney review your vendor contracts. At a minimum, those contracts should include:

1. A written list of approved traffic sources, with pop-ups, browser lockers, robocalls and brand impersonation banned by name.
2. A separate tracking number for each vendor, and ideally for each publisher, so every call can be traced to a source.
3. Your right to receive call recordings and creative samples on request.
4. Immediate termination, with no payment for the affected calls, when the rules are broken.

An illustrative audit. The numbers below are invented for the example.

• Volume. A firm buys 300 calls a month: 150 from Vendor A and 150 from Vendor B.
• Sampling. Each month it pulls 15 random recordings per vendor (10% of each vendor's calls) and listens to the first minute.
• Vendor A. No caller in the sample mentions a warning screen or a manufacturer.
• Vendor B. Six of 15 callers do, which is 40%.

If that rate holds across all of Vendor B's calls, about 60 of its 150 monthly callers arrived believing something false. Those callers are the likeliest to dispute a charge and to complain to a state attorney general. The right move is to stop buying from Vendor B now, before its traffic shows up in your chargeback ratio. A cheaper cost per call doesn't change that.

Disclosures That Make Clear You're Independent

Legitimate firms state their independence early. They repeat it at every point where a customer could be confused:

• In ad text, where the platform allows it.
• On the landing page above the fold, not only in the footer.
• In the phone greeting, which opens with your company name.
• In the technician's script, before any remote access session starts.
• On the price quote, which states what's included before the customer pays.
• On the receipt and the confirmation email.

Here is a statement that works: "[Company] is an independent technical support provider. We are not affiliated with or authorized by Microsoft, Apple, HP or any other manufacturer. Your device's manufacturer may offer free support while it's under warranty." That last sentence costs you some sales. It also takes away the strongest argument in a later dispute.

Skip manufacturer logos and the word "official." Claim a certification only if you hold it and can name it. Make your billing descriptor match the brand the customer saw in the ad, so the charge is recognizable on their statement.

The timing of payment matters too. Our guide on charging before or after a remote support session walks through the options.

Auditing Your Lead Sources Before an Underwriter Does

Run this review before you apply, and repeat it every quarter. The table shows what an underwriter is likely to look at for each channel and what you should keep on file.

Next, connect disputes to sources. Map every chargeback to a tracking number so you can see whether one vendor produces most of your "I was scammed" cases. Our guide to winning tech support chargebacks covers the evidence that helps once a dispute is filed.

Bring this package with you when you apply. Our article on why tech support merchant accounts get declined explains what else underwriters request. MannyPay offers high-risk merchant accounts, and a specialist responds to free quote requests within one business day. Approval still depends on underwriting.

Your first task this week: pull 10 recordings from each lead source and listen to how each call starts.

MB

About the author

Marcus Bennett

Marcus Bennett is Payments Risk & Compliance Analyst for Beyond the Swipe, covering high-risk processing, chargebacks, rolling reserves, frozen merchant accounts and fraud prevention.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.