My Merchant Has Negative Reviews Online. Will That Kill the Deal?

Last Updated on July 8, 2026

Almost certainly not. A handful of negative reviews online, even harsh ones, rarely affects an underwriting decision, because review count on its own tells an underwriter almost nothing. What matters is the number of complaints relative to how many transactions the merchant actually runs, and whether the complaints describe the same specific problem over and over. Twenty angry reviews against ten thousand monthly transactions is noise. Twenty angry reviews against three hundred transactions, all describing the same failure, could be saying something. The count is meaningless without the context.

This is one of the most misunderstood parts of merchant underwriting, on both sides. Agents see a page of one-star reviews online and assume the deal is dead. Merchants panic about a few loud detractors. Neither reaction reflects how a good underwriter actually reads reviews. Here’s the mental model that does.

Every Consumer-Facing Business Accumulates Negative Reviews

Start with the baseline reality: any business that sells to consumers at scale will collect negative reviews no matter how well it operates. It’s not a sign of a problem. It’s a sign of volume.

A merchant processing thousands of transactions a month is interacting with thousands of customers a month. Some fraction of those customers will have a bad day, a delivery that ran late, a product that wasn’t what they expected, or a dispute that didn’t go their way. A small slice of that group will post about it. That’s not a business doing something wrong, rather that’s the arithmetic of serving a lot of people. Consumer-facing operations generate negative noise as a baseline, and a fraction of that noise reaches review sites.

So the existence of negative reviews isn’t the question. Every merchant of any size has them, including the ones that run clean. The question an underwriter is actually asking is: how many complaints, relative to how many customers? And: are the complaints all pointing at the same specific thing?

The Review-to-Transaction Ratio

This is the concept that changes how you read a merchant’s review profile. A complaint count means nothing until you divide it by the transaction volume behind it.

Consider two merchants, each with 30 BBB complaints:

• Merchant A processes 15,000 transactions a month. Thirty complaints against roughly 45,000 transactions a quarter is a complaint rate so low it’s statistically insignificant. This is a well-run business generating baseline noise.
• Merchant B processes 400 transactions a month. Thirty complaints against roughly 1,200 transactions a quarter is a materially different picture. That’s a complaint on more than one out of every fifty transactions, which points at a real operational problem.

Same 30 complaints. Completely different findings. The count didn’t tell you anything; the ratio did.

This is why an underwriter’s first move on a body of negative reviews is to establish the denominator, the transaction volume, before weighing the reviews at all. That volume comes from the processing statements, the bank deposit activity, or a reasonable estimate based on the merchant’s size. Only once there’s a denominator do the reviews mean anything.

The practical implication for you as an agent: the more you can substantiate your merchant’s transaction volume, the more the reviews get read in proper proportion. A merchant with clean processing statements showing real volume has a built-in defense against a scary-looking review page, because the volume puts the complaints in context. A merchant with no documented volume and a page of complaints is harder to read, because there’s no denominator to divide by.

The Second Question: Is There a Pattern?

The second thing an underwriter reads is the content, and here the question is whether the complaints describe the same specific failure repeatedly.

There’s a real difference between:

• Scattered dissatisfaction. “Shipping was slow.” “Customer service was rude.” “Didn’t love the product.” A mix of unrelated gripes across a range of topics is the normal texture of consumer feedback. It doesn’t point at anything structural.
• A repeated failure mode. Twenty reviews all saying “they charged my card again after I cancelled.” Fifteen reviews all describing a refund that was promised and never came. A dozen reviews all reporting a service that was paid for and never delivered. When the same specific, concrete failure shows up over and over, that’s a pattern, and a pattern matters even when the raw count is modest.

The reason the pattern matters is that it describes a repeatable problem in how the business operates, which is exactly what predicts future chargebacks and disputes. Billing without consent, refund refusal, undelivered service — these are the specific failure modes that turn into card disputes, and card disputes are what an acquirer actually cares about.

One important calibration: generic “this is a scam” sentiments are a much weaker signal than a specific, concrete complaint. A review that just says “SCAM DO NOT BUY” with no detail tells an underwriter very little — angry people reach for that word about everything from a genuine fraud to a late package. A review that says “I was billed $89 three months in a row after I cancelled and they won’t refund me” is specific, concrete, and, if it repeats across multiple reviewers, a real finding. Read the substance, not the volume of outrage.

What This Means for the Star Rating and the BBB Grade

The star rating and the BBB letter grade are among the least useful things on a merchant’s review profile, and it’s worth understanding why.

The BBB grade is largely a function of whether the merchant pays for accreditation. The Better Business Bureau is a paid accreditation service. A merchant that doesn’t pay for accreditation will tend to carry a weaker grade regardless of how well it actually treats customers. A strong grade can reflect a paid relationship as much as good conduct, and a weak grade can reflect a merchant that simply never enrolled. The grade is not a reliable risk metric. What’s useful on the BBB is the complaint narratives. Read those for patterns and just ignore the letter.

Star ratings compress everything into a single number that hides the actual signal. A 3.2-star average could mean steady mild dissatisfaction across the board, or it could mean a large base of happy customers alongside a specific cluster of people describing the same serious failure. Those are very different situations that produce a similar star average. The number doesn’t distinguish them; reading the reviews does.

So when your merchant frets about their star rating or their BBB grade, the honest reassurance is that neither is what an underwriter actually weighs. The substance of the complaints, read against the transaction volume, is what matters.

What Underwriters Do (and Don’t) Ask You For

Here’s a point that saves agents a lot of unnecessary work: you are never asked to compile your merchant’s reviews.

Review research is something the acquirer does internally. On any submission, the underwriter surveys the merchant’s consumer review and complaint footprint (BBB, Trustpilot, Google, and other platforms) as a standard part of the review. That’s an internal research task, run against the merchant name, using the public record. It’s not a document you collect and it’s not something the merchant provides.

So if you’re ever tempted to gather screenshots of your merchant’s Google reviews, or ask the merchant to explain their complaints, or assemble a rebuttal to their BBB profile — don’t. None of that is a useful underwriting input, and asking the merchant to explain their reviews produces exactly the kind of self-serving narrative that carries no analytical weight anyway. The underwriter is going to look at the public review record regardless of what you assemble, and they’re going to weigh it against the transaction volume and read it for patterns. Your job is to submit clean documentation of the merchant’s actual business — the volume, the processing history — which is what gives the reviews their proper context.

When Negative Reviews Actually Do Affect the Outcome

To be straight about it: reviews aren’t always noise. There are situations where a review profile genuinely bears on a deal, and it’s worth knowing what they look like so you can spot them before submission.

Reviews become a real factor when:

• The complaint volume is high relative to a small or unverifiable transaction base. A lot of complaints against a little volume is the ratio that points at an operational problem.
• There’s a clear, repeated failure-mode pattern describing billing without consent, refund refusal, or undelivered service — the specific failures that convert to chargebacks.
• The reviews reference regulatory action or litigation. A complaint that mentions an FTC inquiry, a state AG action, or a filed lawsuit is a different kind of signal, and it routes the deal toward a closer look regardless of the ratio.

In those situations the reviews inform the assessment — sometimes as a condition, sometimes as a reason for elevated monitoring, occasionally as part of a decline when the pattern is severe and points at a structural problem. But even then, it’s the pattern and the ratio doing the work, not the raw count. And a merchant with a genuine review problem is often still workable with the right structure; a pattern of disputes is exactly what reserves and chargeback monitoring exist to manage.

The Bottom Line for Agents

When your merchant has negative reviews, don’t panic and don’t apologize for the deal. Do this instead:

1. Substantiate the transaction volume. Clean processing statements showing real volume are the single best defense against a scary review page, because they give the reviews a denominator and put the complaints in proportion.
2. Read the reviews yourself for pattern, not count. If the complaints are scattered and generic, it’s almost certainly noise. If they all describe the same specific billing, refund, or delivery failure, that’s worth knowing before you submit. Not because it kills the deal, but because it’s the kind of thing that may shape the conditions.
3. Don’t compile or explain the reviews. The acquirer researches this independently. Your energy goes into documenting the real business, not litigating the review page.

A page of one-star reviews looks alarming. But underwriters don’t read the alarm. Instead, they read the ratio and the pattern. A well-run merchant with real volume and scattered complaints is a good deal that happens to have the normal residue of serving a lot of customers. That’s not a problem. That’s just what volume looks like.

Frequently Asked Questions

My merchant has a 2-star average on Google. Is that a dealbreaker? On its own, no. A star average compresses too much into one number to be a reliable signal, and underwriters don’t weight it as a risk metric. What matters is the number of complaints relative to the merchant’s transaction volume and whether the complaints describe a repeated specific failure. A 2-star average on a low-volume merchant reads differently than the same average on a high-volume one, and in both cases the substance of the reviews matters more than the average.

Does a bad BBB rating hurt the application? The BBB letter grade isn’t a reliable risk metric, largely because the BBB is a paid accreditation service and the grade partly reflects whether the merchant pays for accreditation rather than how they treat customers. What underwriters read on the BBB is the complaint narratives, looking for a repeated pattern. A weak grade with no meaningful complaint pattern behind it isn’t a finding.

Should I have my merchant respond to or explain their negative reviews before submitting? No. Don’t ask the merchant to explain their reviews or compile a rebuttal. An explanation of consumer complaints is self-serving and unverifiable, and the acquirer researches the review record independently regardless. Your effort is better spent documenting the merchant’s actual transaction volume, which is what gives the reviews their proper context.

My merchant has real complaints about a billing issue they’ve since fixed. Does that matter? The relevant question is what’s happening now, not what happened before. If there was a genuine billing problem that the merchant has resolved, the evidence of that resolution is in the current processing statements — clean recent chargeback and refund metrics. Older complaints against a backdrop of improved current metrics read as a problem that’s been addressed, not as an active finding. As with most underwriting questions, the recent data controls the read.

How many negative reviews is too many? There’s no absolute number, because the number by itself is meaningless. The measure is complaints relative to transaction volume, plus whether there’s a repeated failure-mode pattern. Thirty complaints against 15,000 monthly transactions is insignificant. Thirty complaints against 400 monthly transactions is a real finding. The same count, opposite conclusions — which is exactly why count alone is never the measure.

My merchant is new and doesn’t have much transaction history yet. How are their reviews weighed? This is the one situation where the ratio test gets harder, because there’s no solid transaction denominator to divide by. When volume genuinely can’t be established, underwriters fall back to reading the review content for a specific, repeated failure pattern — a single unhappy customer isn’t a finding, but the same concrete failure described across multiple independent reviews is. The best thing you can do for a newer merchant is substantiate whatever volume does exist, so the reviews get read in proportion rather than in a vacuum.

Back