The underwriting decision starts from an uncomfortable fact: if your firm fails tomorrow with unsettled disputes outstanding, the acquirer pays them. Card scheme rules make the acquirer responsible for its merchant's obligations, so the analyst reading your application is estimating how much money they could be left holding and how likely that is. Reserves, caps and settlement delays are all answers to that estimate. Once you see the file that way, the terms stop feeling arbitrary.
Delivery risk is the core question
Acquirers classify merchants partly by when the customer receives what they paid for. A restaurant delivers instantly and carries little forward exposure. A firm taking deposits that a customer might use over months, and might dispute after losing money on them, sits at the other end. The exposure window is long, the dispute reasons are broad, and the emotional profile of the disputing customer is unfavourable. Leveraged trading also produces a class of complaint no other category has, where the customer accepts they authorised the payment but disputes the circumstances in which they were persuaded to make it.
This is why the underwriter asks for the withdrawal policy and the average time to pay a withdrawal. A firm that pays out quickly has fewer disputes, because most disputes in this sector start as a withdrawal the customer could not get.
Merchant category coding and what it signals
Every merchant is assigned a category code that tells issuers what kind of business generated the transaction. Issuers apply their own authorisation rules by category, and some block certain categories entirely for certain products or cardholder segments. Coding a trading business accurately means lower approval rates on some issuers, and that is a legitimate cost of being correctly described. Coding it inaccurately to gain approvals is a scheme rules breach with consequences that follow the directors personally, and it is the single fastest way to lose an account and the reserve with it.
Where an acquirer offers a choice of coding, that choice is theirs to justify to the scheme, not yours to optimise. If a provider proposes a code that does not describe what you do, that is information about the provider.
The dispute ratio and the monitoring programmes
Both major card networks run programmes that identify merchants whose dispute or fraud ratios exceed defined thresholds and place them into remediation, with escalating obligations and fees for each period the merchant remains above the line. Acquirers underwrite with those programmes in mind, because a merchant entering one creates cost and scheme attention for the acquirer as well. The practical effect is that your ratio is not a private performance metric. It is a shared exposure, and it is the number most likely to trigger a mid-life review of your terms. The mechanics of contesting individual cases sit in chargeback representment, and the prevention side in chargebacks and fraud prevention.
Authentication changes who carries the loss on a fraud dispute. Where a transaction is authenticated under the current scheme framework, liability for fraud-reason disputes generally shifts to the issuer, which is why acquirers underwriting this category care so much about how you use it. The detail is in 3-D Secure 2 explained.
What the underwriter reads beyond the numbers
The financials, for whether the firm could absorb a spike in refunds from its own balance sheet. The ownership chain, for who would be pursued if it could not. The licence and country map, because an acquirer processing for clients the merchant cannot lawfully serve inherits that problem. The website, for outcome promises, hidden pricing and a descriptor that does not match the brand. Affiliate arrangements, since you own the conduct of the people you pay, and aggressive affiliate marketing is a reliable predictor of complaint volume. And the previous processing relationships, including why they ended, which will be discovered anyway.
The offer, and what changes it later
A trading firm approval typically arrives with a rolling reserve held from settlements for a defined period, a monthly or per-transaction cap, a settlement delay, country and card-type restrictions and a scheduled review. Those terms are the acquirer sizing its contingent liability. They improve with clean history, and they tighten immediately on a small number of triggers: a dispute ratio approaching a monitoring threshold, volume materially above the approved forecast, a change in the country mix, a regulatory warning notice naming the brand, negative press, or a change of control that was not disclosed.
The disclosure point is worth dwelling on. Firms routinely change beneficial ownership, add a new entity or open a new market without telling the acquirer, then are surprised when the account is frozen. The merchant agreement almost always requires notification, and an undisclosed change discovered during a review is treated as a control failure regardless of how benign the change was.
Two habits make the whole relationship easier. Report your own numbers before the acquirer's monitoring reports them, including the bad month with the explanation attached. And keep the operational levers that reduce disputes in working order: fast withdrawals, a clear descriptor, honest marketing and a support channel that answers before the customer calls their bank instead. SINGUARD builds the CRM, portal and payment orchestration layer these firms run and holds no payments licence itself, so our view of underwriting is the one from inside the merchant. The firms with the best terms are not the biggest ones. They are the ones whose dispute ratio never surprises anybody.
"Every term in an acquiring offer is the same sentence in different words: what happens to us if you disappear next month with refunds outstanding."
— Roman Onta, Executive Director, SINGUARD
Key Takeaways
- Acquirers guarantee your refunds to the card schemes, so reserves, caps and settlement delays are liability sizing, not fees.
- Long delivery windows and loss-driven disputes put leveraged trading at the high end of the exposure scale.
- Miscoding the merchant category to raise approvals is a scheme breach that costs the account and the reserve.
- Undisclosed changes in ownership, volume or country mix are treated as control failures during a review.
Frequently Asked Questions
Why does an acquirer hold a rolling reserve?
Because it is contractually responsible to the card schemes for refunds and chargebacks if the merchant cannot pay them. The reserve funds that contingent liability and is normally released on a schedule, with terms improving as clean processing history accumulates.
What triggers a mid-life review of my acquiring terms?
A dispute or fraud ratio approaching a scheme monitoring threshold, volume well above the approved forecast, a changed country mix, a regulatory warning naming the brand, adverse media, or an undisclosed change of ownership or business model.
Do faster withdrawals really reduce chargebacks?
In this sector most disputes begin as a withdrawal the customer could not obtain or did not understand. Paying out promptly and communicating delays clearly removes the trigger before the customer contacts their issuer, which is why acquirers ask about withdrawal times during underwriting.
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.