Reselling Antivirus and Software Licenses: Processor Rules
Reselling antivirus software as a tech support firm? See the reseller proof and renewal rules processors check before they approve you.

Photo: Pixabay
On this page 7 sections
- Why Reselling Antivirus Software Raises Flags in Tech Support Underwriting
- Authorized Software Reseller Agreements vs. Gray-Market Keys
- Who Owns the Renewal: You or the Software Vendor?
- Mark up the License, but Disclose Whose Software It Is
- Set the Refund Rule Before the Key Is Activated
- Stop Double Billing Against the Vendor's Own Auto-Renewal
- Build Your Software File Before the First Bundled Sale
Key takeaways
- Before you sell a bundled license, have a reseller or distributor agreement and invoices that trace each key to an authorized source.
- Decide in writing who bills the renewal, if anyone, and make your checkout and receipts match that decision.
- Once a key is activated, its cost is gone whether you refund or fight, so base your refund rule on the dispute fee and your chargeback ratio.
- At intake, check every device for an existing security subscription so the vendor's auto-renewal and yours never charge the same customer twice.
Processors can approve a tech support firm that resells antivirus and other software licenses, but generally only if your file proves two things: you are authorized to sell the product, and the customer understood what they bought. Underwriters will also ask who bills the renewal and how you handle refunds on keys that are already activated. If you can't answer those questions, reselling antivirus software is one of the fastest ways for a support business to lose its merchant account, because it looks like the scam model that card networks and regulators have spent years shutting down.
The paperwork comes before the first bundled sale. The mistakes come at renewal time.
Why Reselling Antivirus Software Raises Flags in Tech Support Underwriting
Underwriters already treat tech support as high risk, and software bundles are a big reason. The fraud pattern they remember starts with a pop-up or cold call claiming the computer is infected. A "technician" gets remote access, finds "threats," and sells the caller a multi-year "security package" at a steep price. What gets installed is a free tool or an unlicensed key. Federal and state regulators have brought enforcement actions against this model. Processors carry their own exposure when they keep processing for merchants they know, or should know, are deceptive. We covered that pressure in our look at the FTC's knowledge standard for processors.
That history explains the follow-up questions you'll get when a software line appears anywhere in your application. The underwriter will ask what the product is and where your keys come from. They will compare your price with the vendor's own and ask who charges the card when the term ends. Expect requests for your reseller agreement, recent distributor invoices, a sample receipt and the page where you sell the license. If you can't produce them quickly, the application stalls. Missing supply-chain documents are one of the patterns behind why tech support merchant accounts get declined.
The same scrutiny applies when you add software after approval. Find the clause in your merchant agreement on material changes to what you sell, and give notice before the product launches. Your processor might first see the new line as a shift in ticket size or a jump in descriptor complaints. That triggers a review you'd rather have started yourself.
Authorized Software Reseller Agreements vs. Gray-Market Keys
An authorized software reseller has a written relationship with the vendor or with a distributor the vendor has approved. That relationship produces paperwork: a signed agreement, partner portal access, and invoices that list each key or license block you bought. Those invoices are what underwriters want, because they trace every license you sell back to a legitimate source.
Security vendors run antivirus reseller programs on very different terms. Before you build pricing around one, read the agreement for these points:
- Whether you may bundle the license with your own paid services
- How you may use the vendor's name and logos in ads
- Pricing rules, such as minimum advertised prices
- Who handles billing and renewal
- Whether unactivated keys can be returned for credit
Gray-market keys are licenses sold outside the vendor's authorized channel. Deeply discounted keys from online marketplaces are the most common example. OEM keys meant to ship only with new hardware, volume licenses issued to one organization, and keys intended for another region all belong in the same category. They are cheap because the vendor never authorized the sale.
These keys get accounts closed from several directions. Vendors revoke keys they trace to unauthorized channels. When that happens, a customer's protection stops working weeks after they paid you, and that becomes a dispute you have no evidence to win. Rights holders complain to acquirers about unauthorized sales, and card network rules give acquirers grounds to act on those complaints. An underwriter who asks about your supply chain and gets a marketplace receipt will decline the application or close the account. Depending on the termination reason, that can put the business on the MATCH list, as explained in what happens when a tech support merchant account is terminated.
A license key resale merchant account is approved on the strength of your supply chain. If you can't show where a key came from, don't sell it.
Who Owns the Renewal: You or the Software Vendor?
Selling software licenses with tech support forces a decision that has to be made in writing: who charges the customer when the term ends? Underwriters will ask, and your checkout flow and customer emails have to match the answer.
| Renewal model | Who charges the card next term | What underwriting wants to see | Main dispute risk |
|---|---|---|---|
| You bill the renewal | You, as merchant of record | Renewal terms shown at checkout and recorded consent | "I didn't authorize this renewal" |
| Vendor bills directly | The vendor, on the customer's own account | Proof you stop charging for the license after the first term | Double billing if you also charge |
| Fixed term, no auto-renewal | Nobody, unless the customer buys again | A receipt stating the end date | Lowest risk, but you give up renewal revenue |
Billing the renewal yourself means taking on recurring-billing obligations. Card network rules for stored credentials and subscriptions apply. State automatic renewal laws add disclosure and cancellation requirements, and those laws differ from state to state, so confirm your obligations with a qualified attorney. The billing mechanics match those in recurring billing for annual tech support plans.
Read the reseller agreement before you design a "support plus protection" subscription, because it might settle the question for you. If it requires customers to hold their own vendor accounts and renew through the vendor, storing a card for license renewals breaches it.
Mark up the License, but Disclose Whose Software It Is
Unless your agreement sets pricing rules, the markup is your call. Processors care far more about whether the customer knew what they paid for than about the size of your margin.
Your sales pages and receipts should name the product and its vendor and say plainly that it's third-party software. Show the term length and device count, and list the license price as its own line, separate from your labor. Tell the customer whether the license renews automatically and who bills it. Spell out who supports what: you for setup and first-line help, the vendor for product problems. Phone scripts need the same disclosures, spoken before payment. Never imply you are the vendor or its official support line; the risks there are covered in using Microsoft or Apple names in tech support.
Underwriters compare your price with the vendor's public price. An annual license at a modest premium, bundled with installation, reads as a service business. A "lifetime protection plan," or a license priced at a multiple of retail and sold to a nervous caller, reads as the scam model. That's especially true when buyers skew older, a pattern discussed in refund policies for senior customers and family disputes. Use a billing descriptor with a business name customers recognize, so nobody disputes a charge just because they can't place it.
Set the Refund Rule Before the Key Is Activated
Expect your distributor to refuse credit on activated licenses, and confirm that in the return terms of your agreement. A refund on an activated key comes out of your margin, so your policy has to deal with that honestly. On small tickets, the math favors refunding.
Illustrative example, using your own numbers. You sell an annual antivirus license during a remote session and activate it on the spot. A couple of weeks later the customer asks for the license to be refunded, and your distributor won't credit the key.
Start by setting the key cost aside. You paid it the moment you activated the license, and no outcome gets it back. Firms that count it as a reason to refuse are deciding on money that's already spent. What remains is a comparison of three outcomes:
- Refund on request. You return the license price. Nothing touches your chargeback ratio.
- Refuse, and the customer disputes and wins. You return the same license price and pay your processor's dispute fee, and a chargeback goes on your record.
- Refuse, and you win the dispute. You keep the license price, but representment takes staff time. Check whether your processor charges the dispute fee regardless of outcome.
Losing a dispute leaves you worse off than refunding by the full dispute fee plus the ratio hit. A high-risk account has little room under its chargeback monitoring threshold. Fight only the disputes where you hold strong evidence, such as recorded consent and the disclosed refund rule. Whether you recover the original processing fee on a refund depends on your processor's pricing, so check your agreement.
Two habits cut down on these refunds. Activate keys only after the customer confirms the purchase in writing or on a recorded call. Then state your rule for activated licenses before payment, right next to the price. For wording that holds up, see cancellation windows for tech support refund policies. For disputes you decide to fight, read winning "I was scammed" chargebacks. A revoked gray-market key, though, leaves you with no defense at all.
Stop Double Billing Against the Vendor's Own Auto-Renewal
Double billing is a quiet source of tech support disputes, and it follows predictable patterns. In the first, a customer already has a security subscription that renews with the vendor, you sell a second one, and months later both charge. In the second, the firm sets up the license in the vendor's portal with auto-renewal on the customer's card and also schedules its own renewal. The third pattern starts with a free trial you installed, which converts to paid without anyone noticing.
Build the check into intake. Before you quote, look for security products already on the device and ask the customer about current subscriptions. Record the answer on the ticket. A repair POS like the ones in our computer repair shop POS checklist makes that easy.
When you bill the renewal, confirm with the customer present that auto-renewal is off in their vendor account. When the vendor bills, take the license off your renewal schedule entirely. Remove conflicting products only with the customer's consent, and note that consent on the ticket. Before any renewal you bill, send a reminder with the exact amount and charge date. A customer who sees the charge coming has no reason to call the bank about a mystery charge. For renewals or phone sales keyed into a virtual terminal for card-not-present payments, attach the recorded consent to the ticket so you can produce it if a renewal is disputed.
Build Your Software File Before the First Bundled Sale
Assemble one folder before you sell your first bundled license. Start with your reseller or distributor agreement and your latest distributor invoices. Add the product page or price sheet that shows the license as a separate line. Write a short statement of your renewal model and your refund rule for activated keys, then finish with a sample receipt. Send the folder to your processor before the product goes live, and ask in writing whether software resale falls under your current approval.
If your current processor won't cover software resale, MannyPay offers high-risk merchant accounts. You can request a free quote and share your software file when a specialist follows up. MannyPay specialists respond to quote requests within one business day.
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.


