What makes a business "high risk" for payment processing?

A business is classified high risk when a payment processor expects a higher-than-average rate of chargebacks, refunds or regulatory scrutiny on the money it moves. High risk is a prediction about future disputes — not a judgement about whether a business is legitimate, well run or profitable. Juan Carlos Domínguez heads SB Financial at Studio Bananas Group, where reading that prediction before an application is submitted is the first thing the division does for a merchant; this article sets out how it reads, as at August 2026.

Most owners hear “high risk” and assume they have been accused of something. Nobody has. A processor that approves an account is agreeing to front money to that merchant’s customers before it has collected from them. If a customer disputes a charge four months later, the processor is often the one holding the loss. Every underwriting question it asks is a version of the same question: how likely is that, and how big will it be?

Which industries are usually classified high risk

Classification is not standardised. Two processors can look at the same business and reach different answers, because each is pricing its own exposure and its own appetite. The categories that come up again and again, though, share a small number of features.

The five categories SB Financial works in most often, as at August 2026, are adult, gaming and iGaming, e-commerce and online shopping, online courses, and online payments generally. Alongside those, subscriptions and continuity billing, travel and events, supplements and nutraceuticals, firearms and ammunition, CBD, debt-related services, and professional services that hold client money all tend to draw a closer read.

Look at what those have in common and the logic gets simple:

• The customer is not physically present. Card-not-present transactions carry more fraud and more disputes than a card dipped at a counter.
• Delivery happens after payment, sometimes long after. A course, a booking, an annual subscription. The longer the gap between charge and delivery, the more time there is for something to go wrong.
• Recurring billing. A customer who forgets they subscribed disputes the charge instead of cancelling it.
• Regulation sits on top of the transaction. Age verification, licensing, jurisdiction rules. The processor inherits some of that exposure.
• Average ticket size is large, or wildly variable. A single disputed transaction can wipe out a month of margin.

If your business has two or three of those, expect a longer application. That is not a warning sign. It is the process doing what it is for.

Chargebacks decide it, not the industry code

Here is the part most articles skip. Your industry classification sets the starting point. Your chargeback ratio decides where you end up.

Card networks publish thresholds for disputes as a share of transactions, and processors monitor merchants against them. Cross the line and you can be moved into a monitoring programme, which brings extra fees and closer review, and which is a great deal harder to climb out of than it was to fall into.

The practical consequence: a supplements company with a clean dispute history and a real refund policy can be easier to underwrite than a plumbing company with no dispute history at all, because one of them has evidence and the other only has a good story. A claim about your business is not evidence about your business. Processors know this, and their whole job is to look for the evidence.

Which is also why the single most useful thing you can do before applying is boring: reduce disputes at the source. Clear billing descriptors so customers recognise the charge on their statement. A refund policy someone can actually find. Support that answers before the customer gives up and calls the bank. Cancellation that works in one click rather than three emails. None of that is a payments project. It is a customer-service project that happens to be priced by your processor.

What a high-risk classification actually costs you

Being classified high risk changes four things, and it is worth knowing which are negotiable.

Pricing. Rates and per-transaction fees are set by the processor against the risk it is taking. We do not set them and we do not quote them, because the number depends on the file.

Reserves. A processor may hold back a portion of your settlements — as a rolling reserve released on a schedule, a capped amount held until a threshold is reached, or an upfront amount. This is the one that surprises people, because it is not a fee. It is your money, held. It affects cash flow immediately and it belongs in your forecast before you sign anything.

Settlement timing. Funds may arrive more slowly than the daily settlement a low-risk merchant gets.

Ongoing review. Volume caps, periodic re-underwriting, and a requirement to notify the processor before you change what you sell.

Every one of those is a term in a contract, which means every one of them is a question you are allowed to ask before you sign. Most merchants do not ask. If you want a sense of what you are already paying today, how to read a merchant statement walks through where the real costs hide.

What you can change, and what you cannot

You cannot change your industry. If you sell a product in a category processors watch closely, no amount of presentation makes that go away, and trying to disguise it is the fastest route to a terminated account. Misrepresenting what you sell on an application is the one mistake that closes doors permanently rather than temporarily.

You can change almost everything else:

• Your dispute rate, by fixing descriptors, refunds, delivery times and support.
• Your documentation. Processing history, bank statements, a clean corporate record, a website that describes what you actually sell with real terms and a real refund policy on it.
• Your concentration. Sitting on one processor with no relationship elsewhere is a single point of failure for your entire revenue.
• Your honesty on the application. Volume estimates that match reality. A high average ticket declared upfront rather than discovered in month two.

When you should not submit the application yet

Sometimes the honest answer is that the application should not be submitted yet.

If your dispute rate is already above threshold, applying now converts a fixable problem into a permanent record. If you cannot forecast your volume within a reasonable range, an approval built on the wrong number gets re-underwritten downward the moment you exceed it. If the business model itself depends on customers not noticing a charge, no processor is going to solve that, and none should.

We would rather tell you to spend ninety days fixing your refund flow than put you through an application that generates a decline you then have to explain to the next processor. A decline is not neutral. It goes in the file.

The same logic runs through why payment processors decline law firms — the vertical is almost never the actual reason.

Where we sit in this

Studio Bananas is a consultant and referral partner. We are an approved affiliate of PaySys, authorized to market its services — we do not process, underwrite or set rates, and acceptance is always the processor’s own underwriting decision, not ours. What we do is read your situation before an application goes anywhere: what your statements say, what your dispute exposure looks like, what a reviewer will ask, and whether you are ready to be asked it.

Sometimes that conversation ends with an introduction. Sometimes it ends with a list of four things to fix first. Both are useful outcomes. You can see the categories we work in on payment processing, including adult and gaming and iGaming.