A broker gets declined by three acquirers in a row and concludes the market is unfair. The market is not unfair. It is rule-bound. Visa and Mastercard publish operating rules that bind every acquiring bank, and those rules single out categories of business for extra scrutiny, extra registration and extra monitoring. Retail trading sits in the middle of several of them at once: securities and financial services, cross-border services, high refund and dispute exposure, and heavy dependence on paid advertising to acquire customers who may later dispute the charge.
The acquirer is not deciding whether it likes you. It is deciding whether onboarding you creates a supervisory problem for itself, because the schemes hold the acquirer responsible for its merchants' conduct. Once you understand that, the questions in an underwriting pack stop looking arbitrary.
The merchant category code sets the tone before anyone reads your deck
Every merchant gets a merchant category code, a four digit classifier that tells issuers and schemes what kind of business took the payment. Financial services categories carry known baggage. Some issuing banks treat certain codes as cash-equivalent and either block them, charge cash-advance style handling, or route them into a stricter authorisation policy. That is why a card that works everywhere else declines on a deposit page with no fraud flag anywhere in sight.
Miscoding is the temptation and the trap. Presenting a brokerage deposit under a generic retail or software code is a rulebook breach, and when the acquirer's monitoring or a scheme review catches it, the consequences run from forced reclassification to termination and placement on the industry file that acquirers check before onboarding. Firms that end up there spend years explaining it. If a category is causing declines, the honest fixes are issuer-side education, alternative rails and better presentment data, not a false code. This is one of the places where declined payments have a structural cause rather than a technical one.
Dispute monitoring programmes are the real ceiling
Both major schemes operate monitoring programmes that track a merchant's dispute count and dispute ratio against thresholds, and escalate through stages with remediation requirements and per-dispute fees payable by the acquirer, which passes them on. The thresholds are published in the scheme rules and change over time, so quote the current rulebook rather than a number you read on a forum. The mechanism matters more than the digits: your ratio is measured monthly, it uses the volume from a defined comparison period, and a firm that grows quickly can breach on ratio even when the absolute dispute count is modest, because the denominator has not caught up.
Trading firms generate disputes in patterns retail merchants do not. A client loses money and calls the bank. A card is used by a family member. A promise made by an affiliate is not honoured by the firm. Chargeback reason codes for services not rendered and unauthorised transactions both get used, often incorrectly, and the firm has to answer with evidence. Building that evidence file at deposit time rather than at dispute time is the whole game, which is why representment succeeds for some firms and fails for others on identical facts.
Nothing here is legal or compliance advice. Scheme rules are lengthy, versioned and change several times a year, and they interact with your acquirer's own contract. Take your own legal advice and read the current rulebook with your acquirer before making a decision.
Registration, descriptors and the paperwork acquirers actually enforce
The schemes require acquirers to register certain merchant types and certain arrangements, and to keep records that survive an audit. In practice the recurring items look like this.
| Requirement | What the acquirer is checking | Where firms fail |
|---|---|---|
| Know your business file | Beneficial owners, licences held, group structure, processing history, prior terminations | Nominee directors and unexplained group entities in a low-transparency jurisdiction |
| Merchant category assignment | That the code matches the actual product sold | Deposits coded as software or education |
| Descriptor accuracy | That the text on the cardholder's statement identifies the firm and carries a working contact | Opaque holding-company names that trigger "I do not recognise this" disputes |
| Website and disclosure review | Terms, refund policy, risk warnings, pricing, contact details, jurisdictions served | Marketing claims the licence does not permit, or pages that contradict the terms |
| Sponsorship and aggregation | Whether payments are being facilitated for other parties | Undisclosed sub-merchants sharing one account |
Descriptors deserve a line of their own. A cardholder who does not recognise a statement line calls the issuer, and that call becomes a dispute regardless of merit. Firms that put a recognisable brand plus a support contact in the descriptor cut their unauthorised-transaction disputes without touching anything else. This is boring work with an outsized effect on approval rates further down the chain.
Who accepts which licence, and why the answer is not a list
Founders want a table saying "this licence gets you card acceptance". No such table is honest. Acquirers assess jurisdiction, licence scope, ownership, product and target market as one package. A licence from a well-regarded supervisor in the acquirer's own region reduces friction because the acquirer can verify it on a public register and understands the supervisory consequences of misconduct. A registration from a jurisdiction with limited supervisory capacity does not fail on ideology, it fails because the acquirer cannot rely on anyone to act if the firm behaves badly, and the acquirer carries the loss.
Two further pressures sit on top. Correspondent banking de-risking means the acquirer's own bank may restrict exposure to whole jurisdiction categories, and inter-governmental listings of countries with strategic anti-money-laundering deficiencies feed directly into that. A firm that is legal where it is registered can still be commercially unbankable for card acceptance, and the second fact does not disprove the first. Firms in this position usually build a mixed rail strategy: local schemes, bank transfer, and open banking where available, with cards limited to the markets where their licence actually supports acceptance. Our own view, from watching firms rebuild their stack after a termination, is that a single acquirer is a single point of failure and a multi-provider setup should exist before you need it.
What this means for the operating build
Scheme compliance is mostly a data problem inside the CRM. You need the deposit tied to a verified identity, the terms acceptance timestamped, the trading records retrievable, the descriptor consistent, refunds processed to the original card where the rules require it, and a dispute queue that files evidence within the acquirer's deadline rather than the schemes'. Firms running this by inbox lose disputes they should win. Systems built for the sector, including our own Broker CRM, hold that evidence chain because the alternative is an operator hunting for a screenshot on the last day of a response window.
Trading is high risk for the client and the payment stack inherits that risk. Design for it in month one, and you will not be explaining a monitoring breach in month nine.
"Acquirers are not judging your business, they are judging what happens to them if you fail. Once a founder gets that, the underwriting questions stop feeling personal."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- Your merchant category code drives issuer behaviour before any fraud check runs, and miscoding it is a rulebook breach with lasting consequences.
- Dispute monitoring works on a ratio, so fast-growing firms can breach thresholds even with a modest absolute dispute count.
- Descriptor clarity and a documented evidence chain cut unauthorised-transaction disputes more than any other single change.
- No licence guarantees card acceptance; acquirers weigh jurisdiction, supervision, ownership and target market together, so take your own legal advice.
Frequently Asked Questions
Can a trading firm use a lower-risk merchant category code to avoid declines?
No. The code must reflect the product actually sold, and presenting deposits under an unrelated category breaches the acquirer's obligations under the scheme rules. Detection usually leads to reclassification or termination, and a terminated merchant record follows the firm to the next acquirer. The legitimate routes are issuer-side education, better presentment data and alternative payment rails.
What actually triggers a chargeback monitoring programme?
The schemes measure a merchant's disputes as a count and as a ratio against transaction volume over a defined period, and escalate through stages once published thresholds are exceeded. Escalation brings remediation plans and per-dispute charges that the acquirer passes to the merchant. Because it is a ratio, a firm growing quickly can breach even while its absolute dispute numbers look manageable.
Does holding a regulated licence guarantee card acceptance?
It does not. A licence from a supervisor the acquirer can verify and rely on reduces friction, but the acquirer still assesses ownership, group structure, product, target markets and its own correspondent banking constraints. Firms in jurisdictions facing de-risking pressure often remain legal where registered while being commercially unbankable for cards, and should plan a mixed rail strategy accordingly.
About the Author
Alex Onta is an Executive Director at SINGUARD. He built eTrader, the terminal, the mobile apps, eTrader Broker, Copytrading, Business and Community, along with the worldwide clustered-server infrastructure it all runs on, with his brother Roman Onta helping on the design, and he leads that division today. Together with Roman he builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals, and the two of them carry worldwide compliance, payment processing and international business structuring side by side. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.