The High-Risk Merchant Account Landscape: Aggregators, Dedicated MIDs, and Offshore

Every high-risk merchant runs the same arc. You start on Stripe or PayPal because it takes ten minutes. You grow until an algorithm notices what you sell. Then one morning there is an email: your account is under review, or terminated, and your money is on a 90 or 180 day hold. The merchants who survive that morning are the ones who understood the landscape before they needed to. There are three tiers of processing available to you, and each one trades convenience against durability in a different way.

The three tiers

	PSP aggregators	Domestic dedicated MID	Offshore acquiring
Examples	Stripe, PayPal, Square, Shopify Payments	High-risk ISOs placing you with acquirers like Esquire, Merrick, Fifth Third	Acquirers in the EU, UK, Mauritius, Curacao, and similar
Onboarding	Minutes, no underwriting upfront	1 to 3 weeks, full underwriting	2 to 6 weeks, heavier docs
Typical rates	2.9% + $0.30 flat	Roughly 3.5% to 6% + fees, negotiable	Roughly 5% to 10%+
Reserves	None until there is a problem, then 100% holds	Rolling reserve, typically 5% to 10%	Rolling reserve, often 10%+
Settlement	2 days, until frozen	1 to 3 days	Weekly or biweekly, sometimes longer
Stability for high-risk	Poor: terms prohibit most high-risk verticals	Good, if underwritten honestly	Varies wildly by acquirer
Who it fits	Low-risk volume, testing	The core of a serious high-risk operation	Restricted verticals, MATCH-listed merchants, geographic reach

Tier 1: PSP aggregators

Aggregators put you on their master merchant account. You never get underwritten upfront; instead you get underwritten continuously, by algorithms, after your money is already in their system. The rates are the best you will ever see and the tooling is genuinely excellent.

The problem is contractual, not technical. Read the prohibited business list: most high-risk verticals are named explicitly. Supplements, CBD, coaching, tickets, peptides, subscription models with negative option billing. Operating there anyway is not a loophole; it is a countdown. When the model flags you, there is no phone number to call and no underwriter to reason with. Termination usually comes with a 90 to 180 day hold on your balance. The pattern is predictable enough that we wrote it up separately in why processors shut down high-risk accounts.

Aggregators are fine for genuinely low-risk volume and for testing offers. They are not infrastructure you can build a high-risk business on.

Tier 2: domestic dedicated high-risk MIDs

A dedicated merchant account means an acquiring bank underwrote your actual business and issued you your own MID. You typically reach these banks through an ISO (independent sales organization) that specializes in high-risk placement.

Honest pros: this is the stable core of the landscape. You were approved knowing what you sell, so routine chargebacks and vertical-specific weirdness do not trigger automated termination. You get a human relationship, negotiable pricing as you build history, and next-day or two-day settlement.

Honest cons: it costs more, typically 3.5% to 6% plus per-transaction and monthly fees depending on vertical and history. You will carry a rolling reserve. Onboarding takes weeks and requires real documentation. And ISO quality varies enormously; the contract section below exists because of this tier.

Tier 3: offshore acquiring

Offshore means your acquiring bank sits outside your home market, in jurisdictions with more permissive risk appetites. It is the right tool in three situations: your vertical cannot get domestic approval at all, you are MATCH-listed and locked out domestically, or you are deliberately routing international traffic to local acquiring.

Go in with clear eyes. Rates commonly run 5% to 10% or more. Reserves are larger, settlement is slower (weekly or worse), and wires cross borders with FX cost on top. Cross-border interchange means more issuer declines on US cards; watch your decline codes closely after any offshore migration, because a cheap offshore MID that approves 15% fewer transactions is not cheap. Counterparty risk is real: due diligence on the acquirer matters as much as the rate sheet, because recovering funds from a failed offshore processor is close to hopeless. Offshore is a legitimate layer in a routing stack. It is a poor sole processor.

What underwriters actually look at

Underwriting is not a vibe check. Files get approved or declined on specific items:

• Processing history. Six months of statements from your current processor. Volume, average ticket, refund rate, and chargeback ratio, ideally under 1%. No history at all is workable but caps your initial approval volume.
• Chargeback ratio. The single number that matters most. Above roughly 1.5% expect declines or severe reserve terms.
• Site compliance. The underwriter will click through your checkout. Product claims that survive FTC scrutiny, no miracle-cure language, functioning contact page, and pricing that matches what you charge.
• Terms pages. Refund policy, terms of service, privacy policy, and for subscription offers, explicit disclosure of billing terms at the point of sale. Missing or boilerplate-mismatched terms pages are the most common silly reason files get kicked back.
• Descriptor clarity. The billing descriptor must let a cardholder recognize the charge. Vague descriptors are an underwriting flag because they are a chargeback machine.
• The principals. Personal credit of the owners, MATCH list check, corporate documents, bank letters, and voided checks.

The meta-point: underwriters are pricing the risk that you will generate chargebacks and then disappear, leaving the bank holding liability. Everything on the list is a proxy for that. Make the file boring and complete, and disclose the ugly parts upfront; discovered problems kill deals that disclosed problems would have survived.

Rolling reserves, explained

A rolling reserve is the acquirer holding back a percentage of your gross sales to cover future chargeback liability. Typical structure: 5% to 10% of each day's volume, held for 180 days, then released on a rolling basis.

So at 10% on $100K/month, the bank eventually holds $60K of your money in steady state, and month one you only see 90 cents of every settled dollar. Two things merchants get wrong:

1. Cash flow planning. The reserve builds for six months before the first release. Model it, or it will eat your ad budget at exactly the wrong time.
2. Negotiability. Reserves are not fixed. Six months of clean processing is grounds to request a reduction, and good ISOs will push the bank for it. If yours will not raise the question, that tells you something.

Capped reserves (holdback stops at a fixed dollar amount) are better than uncapped. Ask which one you are signing.

Red flags in high-risk ISO contracts

The high-risk ISO world contains excellent operators and outright predators, and both use the same sales pitch. The difference is in the contract:

• Long auto-renewing terms. Three-year terms that renew automatically unless cancelled in a narrow 30-day window, years from now. One-year or month-to-month exists; hold out for it.
• Liquidated damages. Early termination priced as projected lost revenue on your remaining term, which can be tens of thousands of dollars. A flat, modest early termination fee is normal; a damages formula is a trap.
• Hidden fee schedules. PCI non-compliance fees, annual fees, batch fees, "risk monitoring" fees appearing on page 40. Demand the complete fee schedule in writing before signing and reconcile your first three statements against it.
• Unilateral repricing. Clauses letting the processor change rates with notice buried in a statement message. Common, but negotiate a cap or an exit right triggered by repricing.
• Reserve terms with no release conditions. If the contract does not state when and how reserve funds release, including after termination, assume the worst.
• Personal guarantees beyond the norm. Some personal guarantee is standard in high-risk. Guarantees that survive termination indefinitely or cover the ISO's own fines are not.

None of these are illegal. All of them are signals about how the relationship will go when something breaks.

Sequencing a migration off an aggregator

The order of operations matters, because the failure mode is being terminated mid-migration with no landing spot.

1. Start underwriting while your aggregator account is healthy. Approval takes weeks. The day you get the warning email is too late to start.
2. Fix your file first. Terms pages, descriptor, refund flow, dispute rate. Every fix improves both your survival odds on the aggregator and your underwriting terms.
3. Get the dedicated MID approved and integrated before moving volume. Run test transactions. Verify settlement actually arrives.
4. Move new billing first, then migrate recurring. Point new checkouts at the new MID while existing subscriptions keep billing on the old rail. Migrating stored cards depends on where credentials live: if they are locked in the aggregator's vault, you need a PCI-compliant token migration or a vault you control. That decision is worth getting right early; see payment token vaults explained.
5. Taper, do not cut. Chargebacks lag sales by 30 to 60 days. Dropping the old account to zero overnight shrinks the denominator while old disputes are still arriving, which can spike the ratio and trigger the very termination you were avoiding. Wind down over 60 to 90 days.
6. Keep the aggregator alive as a fallback, at low volume, within its terms, if your vertical allows it. Redundancy is the entire point of the exercise.

Practical takeaways

• Match the tier to the job: aggregators for testing and low-risk volume, dedicated domestic MIDs as your core, offshore as a deliberate layer, not a last resort taken in panic.
• Underwriting is a file-preparation exercise. Complete, honest, boring files get approved on better terms.
• Model your rolling reserve into cash flow before you sign, and ask for the cap.
• Read the termination clause, the fee schedule, and the reserve release terms before anything else in an ISO contract.
• Start the migration before you need it. Every high-risk merchant eventually leaves the aggregator tier; the only question is whether it happens on your schedule or theirs.