When Your Processor Reviews You: Holds, Limits, and Termination | HL Hunt
When Your Processor Reviews You: Holds, Limits, and Termination
An email arrives saying your account is under review and settlement is paused. The most common trigger isn't fraud or anything you did wrong — it's a month that looks nothing like the last twelve. A promotion worked, a large customer paid, a new product sold, and monitoring built to detect a merchant who takes money and can't deliver flagged the pattern. Which means ordinary good news is among the most frequent causes, and the businesses hit hardest are the ones growing fastest with the least cash to absorb a settlement pause.
What you'll learn
What the processor is protecting against
Understanding the logic makes the response obvious and the situation less personal.
A processor carries the risk that a merchant takes payments and then fails to deliver. If that happens, customers dispute, the processor funds the refunds, and if the merchant is gone the processor absorbs the loss.
Which means the monitoring is asking one question: how much has this merchant been paid for goods or services not yet delivered?
Everything follows from that:
- Longer delivery times mean more exposure, which is why pre-orders, deposits, and future-dated services attract more scrutiny.
- Sudden volume increases exposure quickly, per our reserves guide.
- Disputes signal delivery problems, so a rising rate is read as an early indicator.
- Unfamiliar activity can't be assessed, so it's treated conservatively.
None of this is an accusation, and treating a review as one is the most common mistake in the response. The processor is managing an exposure, and evidence that the exposure is smaller than it looks is what resolves it.
What actually triggers a review
| Trigger | Frequently caused by |
|---|---|
| Volume spike | A promotion, a season, a successful launch |
| Unusually large transactions | A big customer, a new tier |
| Change in transaction mix | A new product or channel |
| Rising disputes | Delivery issues, or a descriptor problem |
| Longer delivery times | Supply problems, or pre-orders |
| Business detail changes | New address, entity, or ownership |
| Activity outside your stated category | Diversifying |
| An external report | A complaint, or a network inquiry |
The first five are all things a healthy growing business does. Which is the frustration: the monitoring can't distinguish growth from the pattern a failing merchant produces, because from the data they look the same.
And per our descriptor guide, row four frequently has a cause nobody suspects — a dispute rate rising because customers don't recognize the name on their statement, which is a configuration problem being read as a delivery problem.
Hold, limit, or termination
Different situations with different urgency, and the first thing to establish.
| What it means | Urgency | |
|---|---|---|
| Settlement delay | Funds held, acceptance continues | Cash problem |
| Rolling reserve | A percentage retained ongoing | Manageable, plan for it |
| Volume or ticket limit | Caps on what you can take | Revenue problem |
| Acceptance suspended | Can't take payments at all | Immediate |
| Termination | Account closed | Immediate, plus the listing |
Establish which you're in before doing anything else, because the responses differ — a settlement delay is a cash forecasting exercise and a suspension is an emergency.
And ask what would resolve it. Reviews are usually resolvable with documentation, and the specific documents requested tell you exactly what concern is being addressed.
The first day
Speed matters, and delay is read as a problem in itself.
- Read the notice carefully — what's restricted, what's requested, what the deadline is.
- Call your account representative rather than only replying by email, and ask what specifically prompted this.
- Respond with documentation the same day where you can.
- Provide more than asked where it helps — evidence of delivery is the single most useful thing you can send, because it directly addresses the exposure.
- Explain the trigger if you know it. "We ran a promotion on the third and shipped 400 orders by the ninth, here's the fulfilment data" resolves a volume review immediately.
- Forecast cash without the held funds.
- Arrange a backup acceptance route, today.
- Keep a record of every communication.
Item four is what actually resolves reviews. Per our dispute guide, delivery evidence is what answers the question the processor is asking — tracking, signed receipts, completion records, customer confirmations.
What not to do: don't argue, don't threaten to leave, and don't go quiet. The person handling it is working through a process, and a cooperative merchant with documentation resolves faster than an aggrieved one with an argument.
Cash without settlement
The immediate operational problem, and it's the same asymmetry as any disruption.
Obligations continue while settlement is suspended. Per our forecasting guide, build the weekly view:
- How much is held, and any indication of when it releases.
- What continues to settle, if anything.
- Obligations by week, with payroll as the hard constraint per our payroll analysis.
- Other cash available, per our cash management guide.
- The date you run out.
Then act on it — collect receivables, talk to suppliers, and contact your lender early per our workout analysis, rather than waiting to see whether the hold resolves first.
And keep delivering. The instinct to pause fulfilment while funds are held is understandable and makes everything worse: undelivered orders are exactly the exposure being reviewed, so stopping delivery confirms the concern that caused the hold.
Don't stop shipping
A held settlement makes fulfilment feel like working for free. But the review exists because of undelivered orders, so pausing delivery converts a resolvable review into a confirmed problem — and generates the disputes that make termination likely.
The listing that outlasts the account
The consequence merchants discover afterwards and should understand during.
A termination may be reported to an industry file that other providers consult when assessing applications. Which frequently matters more than losing the account itself, because:
- It can make obtaining a replacement difficult or expensive for a period.
- It may persist for years.
- Reasons are recorded, and they vary in seriousness.
- Correcting an inaccurate listing is possible and takes effort, which is why getting it right at the time is better.
What to do if termination is being discussed:
- Ask directly whether a listing will be made and on what basis.
- Ask whether a voluntary closure would be treated differently — sometimes it is.
- Address the underlying reason if it's fixable, and say so.
- Get the reason in writing.
- Take advice where the listing would be materially damaging, since there are processes for disputing an inaccurate one.
The first question is the one nobody asks and it changes the negotiation, because a merchant who understands the listing's consequence has a reason to resolve things cooperatively that the processor can see.
Reducing the chance
Mostly one habit: tell them in advance.
A change flagged beforehand is a conversation; the same change discovered by monitoring is an exception. What to mention:
- A promotion or campaign expected to raise volume.
- A large order or new customer that will produce unusual ticket sizes.
- A new product line, particularly one with different delivery timing.
- Pre-orders or extended delivery, which materially change the exposure.
- Selling into new markets.
- Changes to the entity, ownership, or address.
- Seasonal patterns, so the first year's peak isn't a surprise.
And the ongoing hygiene:
- Keep disputes low, per our dispute guide — and check the descriptor, since that's the cheapest cause to fix.
- Deliver promptly, which reduces the exposure directly.
- Handle refunds properly, per our refunds guide — a refund is cheaper than a dispute in every respect.
- Keep your stated business description accurate as what you sell changes.
- Maintain a relationship with someone there, so a review has a person in it rather than only a process.
The last is underrated. A processor that knows your business and has a contact who can vouch for the pattern resolves a review in days rather than weeks.
Not depending on one provider
The structural lesson, and it's the correlation point from our correlation analysis applied to payments.
A single acceptance route is a single point of failure for revenue, and it fails at the worst time — a review triggered by a good month arrives exactly when volume and obligations are both high.
What resilience looks like:
- A second acceptance route, established and tested rather than theoretical — opening one while under review is much harder than opening one beforehand.
- A bank payment option, per our bank payments guide, which runs on different rails entirely.
- Invoicing capability for larger transactions.
- Reserves sized to a settlement pause, per our cash management guide.
- Knowing your agreement — what permits a hold, what notice applies, what the termination terms are. Per our records guide, read it before you need it.
The first point is the practical one and the timing is everything. A backup arranged while things are normal costs little; the same arrangement attempted during a review means applying as a merchant currently under review elsewhere, which is a much worse application.
Underwriting that understands growth
HL Hunt Pay provides card, contactless, and ACH acceptance with transparent reserve and settlement terms, advance notice of any review, and a named contact who knows your business — so a good month prompts a conversation rather than a hold.
Frequently asked questions
Usually because activity changed unexpectedly — volume, ticket size, product mix, or disputes. Ordinary good news like a successful promotion is among the most common triggers.
Merchant agreements generally permit delayed settlement or reserves in defined circumstances, usually broader than merchants expect. Whether a specific hold is permitted depends on your agreement.
Acceptance stops, funds may be held against future disputes, and the termination may be reported to an industry file — which is frequently the more serious consequence.
Tell the processor in advance about anything that will change the pattern, keep disputes low, and deliver promptly. A flagged change is a conversation rather than an exception.
Key takeaways
- The monitoring is asking how much you've been paid for things not yet delivered — everything follows from that.
- Growth and impending failure produce the same data pattern, which is why success triggers reviews.
- Delivery evidence resolves reviews faster than anything else, because it directly answers the question being asked.
- Don't pause fulfilment during a hold — undelivered orders are the exposure being reviewed.
- Ask whether a termination will be listed and on what basis; that's frequently the bigger consequence.
- Arrange a backup route while things are normal, since applying under review is a much worse application.
A single acceptance route is a single point of failure
Sign up for HL Hunt Pay for acceptance across card and bank rails with clear reserve terms and reporting, so a review at one provider doesn't stop revenue entirely.
This guide is educational and does not constitute legal advice. What a processor may do in the event of a review, hold, reserve, or termination is governed by your merchant agreement and by card network rules, which vary by provider and change over time, as do the criteria and procedures for industry termination listings. Read your agreement and consult qualified counsel where a restriction or listing would be materially damaging.