A prop firm's merchant category is decided by an underwriter reading a website, not by the firm's own description of itself. The page says simulated accounts and evaluation fees. The underwriter sees a consumer paying a fee for a chance at future money, a product with no physical delivery, a refund promise, and a customer base spread across countries the acquirer may not want. That reading is what sets the reserve, the volume cap and the review cycle, and it happens before anyone at the firm speaks to a human.
The distinction that matters to a payments team is simple. A broker takes client deposits, which are funds held for the client and returned on withdrawal. A prop firm takes a fee, which is revenue. Fees are a cleaner product to acquire in one sense, because there is no client money question, and a much messier one in another, because a fee attached to a pass or fail outcome produces disputes when the answer is fail. Every part of the acceptance stack follows from that.
What the underwriter is actually testing
Know your business review for a prop firm covers the same ground as any other merchant file: incorporation documents, ownership chain to natural persons, director identification, a bank account in the trading name, and proof the website belongs to the applicant. Then come the category questions. What exactly is sold. Whether payouts are made from firm capital. What the refund policy says. How many customers are in the acquirer's own restricted country list. Whether the firm has processed elsewhere before, and why it stopped.
That last question carries more weight than founders expect. A firm arriving with no processing history is an unknown. A firm arriving from a terminated account is a known risk with a paper trail, because scheme-level merchant monitoring records survive the relationship. Presenting the history honestly with the dispute data behind it works better than presenting a fresh company with no explanation for why a five year old brand has no processing record. Underwriters read the mismatch.
Corporate structure feeds directly into this. A single entity holding the brand, the website, the bank account and the customer contract is easy to underwrite. A structure where the customer contracts with an offshore company while an unrelated entity holds the merchant account is a descriptor and liability mismatch, and it is one of the faster routes to a terminated account. Our own notes on group structure and holding companies cover why the contracting entity has to be the one on the payment page.
Disputes are the whole game
The dispute pattern in prop is predictable. A trader breaches a rule, loses the fee, and files a chargeback claiming the service was not as described or was never authorised. Card schemes run monitoring programmes with published dispute-to-transaction ratio thresholds, and a merchant that crosses one enters a remediation programme with fees attached. Cross the threshold repeatedly and the acquirer stops, because the acquirer is the party the scheme fines.
Defence is built before the dispute, not after. That means a checkout that captures explicit acceptance of the rules with a timestamp, a rule set the customer can retrieve unchanged, an account log showing which rule was breached and when, and a delivery record showing credentials were issued and used. Representment succeeds on evidence quality, and a firm that cannot produce the rule version the trader accepted loses cases it should win. The mechanics of building that file are set out in chargeback representment.
Nothing here is legal or payments advice. Scheme rules, acquirer policies and licensing requirements differ by country and by contract, and every firm needs its own legal and compliance counsel before choosing a structure or a processor.
Building the stack, not the account
Treating payments as one merchant account is the mistake that ends firms. The working shape is several routes, each with a defined job, and the ability to move traffic between them without a code release. Cards for the markets where approval rates justify them. Local rails where cards are weak, because approval on a domestic method often beats a cross-border card attempt by a wide margin. A crypto processor for regions where card access is genuinely unavailable, priced with settlement volatility in mind.
Routing between them is where operators earn the difference. Approval rates vary by issuer country, by card product, and by whether the descriptor matches what the customer expects to see on the statement. A firm that measures approval by route and by country finds the losses; a firm that reads one blended number does not. Running more than one PSP is the practical version of that argument.
The refund policy is a payments decision
Refund terms are usually written by marketing and paid for by the payments team. A generous refund promise on the sales page and a strict one in the terms is the exact contradiction an issuer resolves in the cardholder's favour. A policy that is narrow but plainly stated, visible at checkout and honoured without argument produces fewer disputes than a policy that reads well and is enforced tightly, because a refund costs a fee and a dispute costs a fee, a ratio point and eventually the account.
Refundable fee models change the arithmetic again. If the fee is returned on a first payout, the firm is holding money it expects to give back, and that liability sits inside the same account the acquirer is reserving against. Firms running that model should read refundable challenge fees alongside their reserve terms rather than after them.
Payouts are a separate problem
Acquiring brings money in. Paying traders out is a different rail with different requirements, usually a bank transfer, a payout provider or a crypto transfer, each with its own source of funds and sanctions screening. A firm that solves acceptance and ignores payouts discovers the gap at the worst moment, when a public payout complaint drives both refund requests and disputes at the same time. The two sides need to be planned together, and the operational side of that runs through the CRM that already holds the trader's verified identity, which is where our Prop Firm CRM keeps the fee, the rule breach and the payout record in one file.
The firms that keep processing are not the ones with the cleverest structure. They are the ones whose website, terms, entity, descriptor and dispute evidence all say the same thing, and who can prove it on the day an acquirer asks.
"Underwriters do not read your pitch deck. They read your refund page, your descriptor and your dispute ratio, and if those three disagree with each other you are already on a clock."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Acquirers classify prop firms by what the website and terms say, so the entity on the contract, the descriptor and the refund policy must match.
- Dispute-to-transaction ratio monitoring is the main termination risk, and the evidence file has to be built at checkout, not after the claim.
- Run several payment routes with country-level approval measurement instead of one merchant account carrying all volume.
- Plan trader payouts and fee acceptance together, because a payout problem produces disputes on the acceptance side within days.
Frequently Asked Questions
Why do acquirers treat prop firm fees as high risk?
The product has no physical delivery, the customer pays for an outcome that is often a loss, and the customer base is international. That combination produces higher dispute rates than a typical retail merchant, and the acquirer carries the scheme fines when ratios rise.
Can a prop firm use a normal small business merchant account?
Applying under a generic description and processing prop fees through it is misrepresentation to the acquirer, and it usually ends in termination and a monitoring record that follows the directors. Firms should apply on their real business description and accept high risk pricing.
Does taking crypto payments solve the problem?
It removes chargebacks on that route but adds settlement volatility, travel rule obligations at the processor, and its own compliance review of the business. It works as one route in a mixed stack rather than as a replacement for card acceptance.
About the Author
Roman Onta is an Executive Director at SINGUARD. He builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals side by side with his brother Alex Onta, and he helped on the design of eTrader, the division Alex built and leads. His ground is worldwide payment processing, AML compliance and the corporate structures brokers are built on, work the two of them carry together, shaped by executive roles in the UAE and international corporates. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.