All articles

Banking7 min read

Payment processors freeze accounts. Plan for it.

A freeze is not a punishment and it is rarely a mistake. It is an acquirer deciding it is carrying more risk than it agreed to. Understanding whose risk it actually is tells you exactly what to do about it.

The story is always told the same way. Sales were fine, nothing changed, and one morning the payouts stopped and a form appeared asking for documents.

It reads as arbitrary because the reasoning is never explained. It is not arbitrary. When a customer disputes a card payment, the money comes back from the acquirer, not from you — and the acquirer only gets it back from you if you are still there and still solvent. Every reserve, hold and termination is that one exposure being managed.

Read from that side, the triggers become predictable, and most of them are avoidable.

Three different things called a freeze

What happensTypical durationWhat it means
Review holdPayouts pause while documents are requested; processing usually continuesDays to a few weeksSomething tripped a rule. Usually resolvable by answering quickly and completely.
ReserveA percentage of settlement is retained on a rolling basis, or a fixed sum is heldOngoing — commonly 5–10% held for 90–120 daysYou are being allowed to keep processing, priced for the risk. This is a negotiation, not a verdict.
TerminationThe account is closed and remaining funds are held against future dispute exposureFrequently around 90–180 days after the last transactionThe relationship is over. The hold period exists because disputes can still arrive after you stop selling.
Ranges reflect commonly published processor terms as at August 2026 and vary by processor, acquirer, country and category. Your own agreement governs — the reserve and hold provisions are in it, and are worth reading before you need them.

What actually triggers a review

In rough order of how often founders hit them.

A volume anomaly

Underwriting approved you for a business of a certain shape and size. A launch, a viral post or a Black Friday that multiplies weekly volume looks identical, to a risk model, to an account that has been taken over. Growth is the single most common cause of a hold, which is a genuinely perverse feature of the system.

This one is almost entirely preventable. Processors have a channel for telling them a spike is coming, and using it in advance converts a freeze into a note on the file.

Dispute ratios

The card networks monitor merchants directly, and being enrolled in a monitoring programme puts your acquirer under obligations it will pass to you immediately.

  • Mastercard has long run an excessive chargeback programme keyed to a monthly ratio with a minimum count — historically 100 chargebacks in a month combined with a ratio at or above 1.5%, with a higher tier above 3%.
  • Visa consolidated its dispute and fraud monitoring into a single acquirer-level programme from April 2025, measured on a combined fraud-and-dispute ratio. The direction of travel is fewer, broader thresholds and more responsibility pushed onto the acquirer — which means onto you.
  • In practice your processor's tolerance is tighter than the network's. Treat 1% as the ceiling and 0.5% as the target, because remediation starts long before a formal programme does.

Network programme names and thresholds change; verify the current position with your acquirer rather than with a blog, including this one. Last checked August 2026.

Category drift

You were underwritten as a software business. You added a supplements line, or a coaching upsell, or began reselling someone else's service. Every processor publishes a restricted and prohibited list, and the account was priced against the category you declared. Selling outside it is a contractual breach before it is a risk event, which is why this trigger produces terminations rather than holds.

Future delivery

Anything where the customer pays now and receives later — pre-orders, events, travel, annual subscriptions, long lead times — puts the acquirer on the hook for the whole book of undelivered orders if you stop trading. This is why those categories attract reserves as a matter of course rather than as a reaction. It is not personal, and arguing that you are reliable does not move it. Shortening the delivery gap does.

A know-your-business mismatch

The entity name on the account does not match the registered name. The address is a mailbox the processor recognises as a mailbox. A beneficial owner was never disclosed, or the ownership changed and nobody updated it. US financial institutions are required to identify beneficial owners of legal-entity customers, and processors run equivalent checks — so a mismatch is not a formality, it is an unmet regulatory obligation sitting on their file.

The non-resident premium

Everything above applies to everyone. Three things apply more to founders operating a US entity from outside the US.

  1. Onboarding asks for more, and asks again later. Formation documents, EIN confirmation, proof of the owner's identity and address, and often evidence that the business is real — a working site, contracts, invoices. Keep a folder with all of it current; you will be asked twice.
  2. Payout destination matters as much as the entity. A US entity paying out to a personal account in the founder's country of residence is a common flag. Aligning the entity, the bank account and the payout destination removes it. Opening a US bank account as a non-resident covers what is realistically obtainable.
  3. Your recourse is thinner. Domestic merchants have relationships, local regulators and small-claims routes. A remote founder mostly has a support queue. That asymmetry is the argument for redundancy, and it is the whole reason for the next section.

The second rail

The single most useful thing in this article: a second processor is worth nothing if you set it up after the freeze.

Underwriting takes days to weeks. Establishing processing history takes months. An account opened in an emergency is a new account with no history, applying under visible distress, frequently with a terminated account in its background — the worst possible application. An account opened while everything is fine, carrying a small share of live traffic, is a switch you can throw in an afternoon.

  • Two processors, both live. Route a genuine minority of volume — 10% is enough — through the secondary so it accumulates history and you know the integration works.
  • Two banking rails. A processor freeze that also strands your operating cash is two problems. Keep payroll and fixed costs somewhere the processor does not touch.
  • Never hold working capital inside the processor. Sweep to the bank on a schedule. Balances sitting in a processor are the balances that get held.
  • Know your descriptor. A statement descriptor customers do not recognise is the leading cause of avoidable disputes, and it is a five-minute fix.
  • Keep the file current. Entity documents, ownership, address, category, expected volume. Updating these proactively after a change is far cheaper than explaining them during a review.

The first 48 hours

If it happens, the response is mechanical.

  1. Answer the request exactly, and completely, the same day. Partial responses restart the clock. This is the single largest determinant of how long a hold lasts.
  2. Do not open a second account with the same processor. It is a terms breach and converts a hold into a termination.
  3. Switch new volume to the secondary rail. Not to hide anything — to stop adding to a balance you cannot access.
  4. Tell customers what is happening if delivery is affected. Silence produces disputes, and disputes are what caused the review in the first place.
  5. Refund anything you cannot deliver, immediately. A refund costs you the sale. A chargeback costs you the sale, a fee, and a point of ratio.
  6. Ask specifically what would resolve it. "Which document, in what form, and what is the review period?" gets a usable answer far more often than an appeal to fairness.
  7. Write down the balance and the release schedule. If funds are held post-termination, the tranches and dates are in your agreement, and they are enforceable.

The standing setup

None of this requires much. It requires doing it before you need it.

Why
Two processors, secondary carrying live trafficUnderwriting and history cannot be acquired in an emergency
Two banking rails, operating cash separatedA processor hold should not stop payroll
Daily or weekly sweep to bankHeld balances are only ever the balances you left there
Dispute ratio monitored monthly against a 1% ceilingThe remediation window closes before the network programme opens
Clear descriptor, prompt refunds, delivery evidence retainedRemoves the majority of avoidable disputes
Entity, ownership and category documents kept currentTurns a review into an afternoon instead of a month
Advance notice of expected volume spikesConverts the most common trigger into a non-event

The founders who survive a freeze without much damage are not the ones with better luck or better arguments. They are the ones for whom the frozen account was one of two, holding a few days of settlement rather than a quarter of cash.

Banking and payments set up as part of the stack

Entity, address, bank account and payment rails belong in one order, with the redundancy built in at the start rather than after the first hold.

See the Business OS

Founders 8 tracks obligations and deadlines for your reference. It does not provide legal or tax advice — filings are prepared and reviewed by qualified partners.