Skip to main content

Aggregator vs Dedicated Merchant Account for Subscriptions

Get Started ›
Subscription business owner reviewing a paused payouts notice on a payments dashboard
Summarize this article with AI
Open it in your preferred AI engine for an instant summary.

Quick Answer

For an established subscription business, a dedicated credit card merchant account is safer than an aggregator. It underwrites the business once, in its own name, instead of re-scoring every payout cycle.

An aggregator can pause charges and payouts together, and when charges stop, renewals stop with them. Approval for a dedicated account turns on describing how your recurring billing actually works and the controls around it. Next, I look at who really holds the account.

Did this answer your question?

Key Points

  • A UK Stripe merchant posting on Reddit said about £20K was held after a July 2025 ban, and the balance became available only around November 7, 2025.
  • Mastercard's revised standards for subscription and free-trial merchants took effect on October 11, 2022, and apply equally to both B2B and B2C transactions.
  • SeamlessChex works with established businesses processing a minimum of $25,000 per month, across every vertical, and does not onboard pre-launch startups.
Three things subscription operators believe. Myth or fact?
Call each one, then see how other readers called it.
1 On an aggregator, the platform, not your subscription business, is the merchant of record with the card networks.
2 Emailing support rarely gets frozen funds released early after an aggregator ban.
3 A dedicated merchant account can never freeze your funds.
Subscription business owner reviewing a paused payouts notice on a payments dashboard

When an aggregator pauses charges, every scheduled renewal pauses with them.

Account ownership decides it. On an aggregator, the platform holds the merchant relationship and can pause every renewal at once; on a dedicated merchant account, the business is underwritten in its own name.

Most subscription owners compare aggregators and merchant accounts on fees. I think that misses where the money actually gets stuck. A recurring biller charges stored cards on a schedule, month after month, and every one of those renewals depends on one thing: whether the account behind it is still open.

A commenter on a Reddit thread about released Stripe funds, posted in November 2025, put it plainly: "Payment platform rules aren't just small print. They effectively define the ceiling of how your cash flow works." That line is the whole debate in miniature. The same commenter argued that support emails rarely shorten a hold. The risk timer does.

The question buyers keep asking is how a subscription business gets approved for a recurring billing merchant account, meaning a credit card merchant account issued in the business's own name and underwritten for scheduled charges. Approval depends less on the product and more on its shape. In the underwriting view my team works from, a processor prices how money moves through a business, the application has to describe that movement and the controls around it, and the useful question for any processor is whether it already boards that shape. High-risk subscription sellers, peptide brands among them, face the same test with less room for a vague application.

Below, I walk through who owns the account on an aggregator, why recurring billing trips automated risk rules by design, where a dedicated account can still freeze money, and what an application needs before the first renewal moves over.

Stripe, Shopify Payments, Square and PayPal all solve the same problem for a young business: they let it accept cards today without an underwriter studying it first. For an established subscription company billing customers on a schedule, that convenience has quietly become its largest liability.

The aggregation model never really underwrote you. It boards your business under its own master merchant account, then scores you continuously with automated rules. Every renewal run feeds that score. So does every growth month, and every dispute. When the score tips, payouts pause. So do the renewals you depend on.

A dedicated credit card merchant account works the other way round. You hold the relationship with the acquiring bank directly, so a question about your renewals becomes a conversation with your own underwriter rather than a ticket in a platform's automated review queue. Limits, reserves and terms are set up front, in writing.

The stakes are climbing, too. Mastercard has published revised standards for subscription and recurring payments, so the rules for billing on a schedule are shifting whether or not your platform explains them to you.

I'll make the case plainly. Ask one question about your own setup first: if the platform paused charges tomorrow, which renewals would fail before you could move them? Staying on an aggregator is the biggest closure risk you carry. Here is why, and what to do instead.

Who actually owns the merchant account on an aggregator?

On an aggregator, your business is a sponsored sub-merchant under someone else's master account, so automated platform rules, not an underwriter who studied your business, decide your standing.

Before going further, I'd ask any subscription operator to answer three questions about their current setup:

  • Do you hold your own merchant ID (MID) with Visa and Mastercard, or does the platform hold it?
  • Who underwrote your account, and on what data: your processing history, or a sign-up form?
  • Which events trigger a review, hold or reserve, and are those terms written into your agreement?

If the answers are the platform, a form, and nobody knows, you are on the aggregation model.

An aggregator, which Visa calls a payment facilitator, owns one large master merchant account and boards its customers beneath it as sub-accounts. The platform tracks your sales internally and pays you out. As far as the card networks and the acquiring bank are concerned, though, the aggregator is the merchant of record. You are not.

The structure has a history worth knowing. Payment facilitation began with aggregators that underwrote doctors' and dentists' offices, taking on the underwriting so small practices could skip setting up their own MID. The model was designed for businesses without many transactions. It was never designed around a company billing stored cards on a fixed schedule, month after month.

Because the aggregator carries risk for everyone under its master account, it protects itself with automated rules rather than individual review. Processors that board merchants leaving these platforms describe the triggers as a few customer disputes, an unexpected jump in sales, or one unusually large charge, any of which can set off a review, a fund hold or a closure. Rolling reserves and delayed payouts can follow even when the account is in good standing.

The consequence is concrete. In July 2025, a UK-based Stripe merchant posting on Reddit had their account frozen and banned over chargebacks they admitted handling badly, and Stripe held about £20K of company money. The balance only became available around November 7, 2025, after the poster says they had tried everything to get it released early. One commenter in that thread summed up the platform's logic: "Chargeback ratio is basically the health score of the account."

Our underwriting team frames the problem differently. In our team's view, a processor is never really pricing the label on an application; it prices the shape of the business behind it, and a sound application describes that shape and how each part of it is controlled. For a subscription company, the shape is stored cards, scheduled charges and renewal disputes. An aggregator's rule engine sees none of that context. It sees a ratio, a spike, a ticket size.

The common assumption is that an all-in-one aggregator is the safest home for recurring billing. A review of 4 sources suggests the opposite: the safety is borrowed, and it can be recalled on the platform's schedule rather than yours. Speed was the trade. Underwriting was the price.

That gap is the reason to evaluate high-risk credit card processing built on your own MID before a hold lands, not after. And for a subscription business, a hold never lands on just one sale.

Why do subscription businesses trip aggregator risk rules by design?

Recurring billing produces the exact patterns automated risk rules flag, so the real question is whether a processor already boards businesses shaped like yours.

The triggers described above sound generic. A subscription company hits them on purpose, every month, because that is how the model works. Consider what a healthy recurring billing operation looks like from inside a rule engine:

  • Volume clusters on renewal dates. Charges stack up on the days customers signed up, which reads as a spike rather than a schedule.
  • Growth arrives in steps. A successful promotion adds a cohort of new subscribers at once, and the next renewal cycle doubles down on that jump.
  • Annual plans raise the ticket. One yearly charge looks like an unusually large transaction next to a history of monthly ones.
  • Disputes lag the sale. A customer who forgot about a renewal disputes it weeks later, long after the original signup.

None of these signals means the business is in trouble. Each one, though, is a reason for an automated system to look twice.

The mechanics of a recurring charge make the gap wider. Industry practice splits stored-card payments into distinct models: one-off payments with saved details, subscriptions charged at regular intervals, and unscheduled charges such as automatic top-ups. A subscription begins with a customer initiated transaction, where the buyer enters card details and consents. Every renewal after that is a merchant initiated transaction, charged against a stored token with no cardholder present. Some issuers even reject the zero-amount authorization many merchants use to validate a card at signup, which forces workarounds.

Put plainly, the renewal is the business. It is also the moment the cardholder is least engaged. That combination is where recurring billing disputes come from, and it is exactly what an aggregator's ratio-based scoring punishes.

The rules themselves are moving. Mastercard has published revised standards for subscription and recurring payments, a sign that card networks are tightening how merchants that bill on a schedule must operate. A dedicated merchant account holder deals with those obligations directly, under its own MID and its own acquirer relationship. A sub-merchant inherits whatever interpretation its aggregator chooses, applied across every account under the master, with no seat at the table.

Here is where the underwriting view matters. Our underwriting team's position is that an acquirer prices the shape of a business, and that the qualification question for any processor is whether it already boards that shape. Subscription billing is a well-understood shape for acquirers that specialize in it. Stored cards, merchant initiated renewals and lagging disputes are expected, priced into the reserve, and written into the terms up front.

That is the practical case for dedicated merchant services over a sub-account. The same renewal spike that trips a platform's rule is, to an underwriter who approved a subscription model, simply Tuesday.

The harder question is what happens when the platform has already decided, and the account or integration is shut off in the middle of a billing cycle.

Is a dedicated merchant account safer, or does it just move the tripwire?

Processors that sell dedicated merchant accounts pitch them as the escape from frozen funds. A guide from one such processor, published in July 2026, explains exactly how a dedicated account freezes money too.

Underwriters, the guide says, build risk parameters around the volumes a merchant states on its application. Declare a top ticket of $200 and then clear a $10,000 invoice, or let monthly volume run "from an approved $20,000 limit up to $150,000," and "the bank's automated risk flags will instantly freeze the incoming funds." The author's company sells these accounts, which gives the warning extra weight.

Automation survives the move. What changes is the standard you are measured against. On an aggregator, your business sits under the platform's master account. One card network's public rulebook, dated October 2026, still sets out requirements for a "Sponsored Merchant" boarded that way. The model was built for small sellers. Casey Porter, a vice president for merchant sales and acquiring at a card network, told PYMNTS in 2023 that the early aggregators served medical offices that "did not have all that many transactions back then," so "the aggregator stepped in, did the underwriting, took on that responsibility."

When one company underwrites thousands of sellers, it protects itself with rules that apply across the whole platform:

What decides a freezeAggregatorDedicated merchant account
Who sets the lineThe platform's own thresholds for monthly sales and average ticketLimits the acquiring bank builds from the volumes and ticket sizes on your application
What can trip itA handful of disputes, a sudden jump in sales, a bigger-than-usual transactionGoing past your declared top ticket or approved monthly volume
Reserves and holdsRolling reserves, delayed payouts and holds, possible even in good standingRolling or fixed reserves, depending on your underwriting risk profile
Whose record countsPartly everyone else on the platformYour own business, under a MID that "belongs entirely to your business entity"

The difference matters most when an account closes. In November 2025 a UK merchant posted on Reddit that an aggregator had banned the account in July. The owner admits mishandling chargebacks, and about £20K of company money was held. "I tried everything to get them to release it," the merchant wrote. Nothing worked.

About four months without £20K

  1. July 2025: account frozen and banned over chargeback handling, with about £20K held.
  2. November 6, 2025: the scheduled release date. Nothing arrives and the dashboard shows no update.
  3. November 7, 2025: the merchant emails support, and an automated reply repeats the original ban email.
  4. Shortly after: the status changes from "charges and payouts paused" to "charges paused," payouts can be scheduled, and the full balance arrives.

One merchant's own account, posted anonymously on Reddit, November 8, 2025.

A commenter offered a likelier explanation for the release: the account had "cleared the liability window." Card disputes can stretch to "around 120 days," the commenter wrote, and a 120 to 180 day hold "is tied to card network rules, so support usually can't bypass it even if they want to."

One anonymous merchant can't tell us how often closures drag on this long. The explanation also cuts both ways: if dispute windows set the length of a hold, a closed dedicated account might tie up cash for a similar stretch. None of our sources describes such a case. What the evidence does support is that the closure itself is the costly event, and chargebacks set this one off. As the same commenter put it, "Chargeback ratio is basically the health score of the account."

For a subscription business on a dedicated account, avoiding that closure starts with describing itself accurately at approval. The July 2026 guide expects checkout to show "explicit subscription billing terms where recurring models are deployed." Mastercard raises the stakes. Its revised standards for subscription and free-trial merchants took effect on October 11, 2022. They apply "equally to both B2B and B2C transactions," cover subscription sellers that use a different merchant category code, and are judged offer by offer.

Both processor sources see aggregators as a fit for small, early businesses, though neither names a dollar figure. Ours is specific: we board only established businesses processing at least $25,000 a month. We also sell dedicated accounts, so we have a stake in this answer.

Both models freeze money automatically. On an aggregator, the platform sets one line for everyone, and the line can move without warning. On a dedicated account, the line comes from the numbers you gave the bank. Either way, the tripwire stays. With your own MID, you help decide where it sits, and you have to move it before your business outgrows it.

  • Before you apply, put your real numbers on the application: typical monthly volume, your largest single charge, and the volume your renewals produce in your busiest month.
  • Ask any acquirer, us included, how to raise approved limits before a launch or an unusually large invoice, and how much notice it needs.
  • Audit checkout offer by offer, free trials and business plans included, for clearly stated recurring terms.
  • Track your chargeback ratio every month on whatever account you use.
  • On an aggregator now? Ask what hold would apply if it closed your account, and whether your cash flow could absorb funds held for months.

How we checked this

We read an explainer from a processor that sells dedicated merchant accounts, a July 2026 newsletter guide from another merchant-services provider, a 2023 PYMNTS interview with a card-network executive, a card network's public rulebook, Mastercard's published questions and answers on its subscription standards, and one merchant's Reddit post with its comment thread. The $25,000 monthly minimum is our own figure. The closure timeline comes from one anonymous merchant. The 120 to 180 day figure comes from an anonymous commenter, and the platform has not confirmed it. Both processor sources sell dedicated accounts, and so do we, so all three of us have a stake. We do not name or link competing providers. Still unknown: how often dedicated accounts freeze or close compared with aggregators, and how long funds stay held after a dedicated account closes. None of our sources measured either.

  1. Explainer on aggregators versus dedicated merchant accounts, published by a processor that sells dedicated accounts, undated. Not linked because the publisher competes with us.
  2. Payment Technology Newsletter, a merchant-services provider's guide to establishing a merchant account, July 1, 2026. Not linked for the same reason.
  3. PYMNTS, interview on payment facilitation with Casey Porter, January 23, 2023.
  4. Card network public core and product rules, October 24, 2026.
  5. Mastercard, questions and answers on subscription and recurring payment standards, standards effective October 11, 2022.
  6. Anonymous UK merchant and commenters, Reddit post on released frozen funds, November 8, 2025. Not linked because the forum is named after a competing platform.
  7. SeamlessChex, merchant qualification minimum provided by Evan Albert, July 2026.

How do subscription businesses get approved for a recurring billing merchant account?

Subscription businesses get approved by describing their recurring billing shape and its controls to an acquirer, backed by bank statements, written policies and a website that discloses billing terms.

If recurring billing is a distinct risk shape, the answer is not to hide it inside a shared pool. As FeedArmy has covered, Google Merchant Center now allows subscription pricing in product listings, so the plan prices shoppers see there should match the ones your application declares. A dedicated credit card merchant account gives the business a merchant identification number that belongs to the business entity itself, not to a platform's shared risk pool. The acquiring bank vets the model, evaluates its specific risk profile, and sets processing limits from the business's own data.

Here is the sequence I'd follow to prepare an application:

  1. Describe the model plainly. State the billing intervals, trial terms, plan mix and cancellation flow. Our underwriting team's guidance is that an application should describe the business's real shape and how each part of it is controlled, rather than a product label.
  2. Assemble the core documents. Expect to provide the legal entity name and Federal EIN, government ID for every principal owner holding 25% or more equity, and a bank verification letter for the settlement account.
  3. Bring your history. Underwriters typically ask for three to six months of consecutive business bank statements and, where you have them, three to six months of prior processing statements. For a business leaving an aggregator, those statements are the strongest evidence you have.
  4. Put policies in writing. Refund, shipping and fulfillment policies should be documented, along with any licenses your category requires.
  5. Fix the website before you apply. For subscription and card-not-present merchants, the public site is the main tool an underwriter uses to evaluate you, and checkout should show explicit subscription billing terms wherever recurring charges apply.
  6. Declare realistic volume and ticket size. Limits are built around what you state.

That last step deserves weight. Industry guidance gives the example of a business declaring a $200 maximum ticket and then running a $10,000 invoice, or jumping from an approved $20,000 monthly limit to $150,000; either can trigger an automated freeze. Understating volume to look small is a mistake. Before you sign, ask the processor which top ticket and monthly volume it will approve, and what it does when you exceed either.

Qualification comes first, though. SeamlessChex works with established businesses processing a minimum of $25,000 per month, across every vertical, and does not onboard pre-launch startups. That floor reflects the logic of underwriting: there has to be a real processing history for an acquirer to price.

Merchants in elevated-risk categories, such as sellers looking for a peptide merchant account, follow the same path. The documents do not change much. The scrutiny on how the model is described does.

So which credit card processor is best for a subscription business? Not the one with the fastest signup. It is the one that already boards recurring billing models like yours and will say so before you sign, because a processor that understands renewals prices them once, at approval, instead of discovering them later in a rule engine.

Ready to move recurring billing onto your own MID?

SeamlessChex underwrites subscription businesses on their real billing shape, so renewals are priced once at approval instead of re-scored by a platform's rule engine.

We work with established businesses that already meet our monthly volume minimum. Credit card processing comes first, with ACH available as a second rail. Bring your statements. We'll start there.

Should an established subscription business stay on an aggregator?

No. Once recurring billing is the business, an aggregator's continuous re-scoring is the largest closure risk you carry, and a dedicated merchant account replaces it with terms agreed at approval.

The Reddit case makes the cost concrete: one Stripe merchant spent roughly four months without access to their operating cash after a chargeback-driven ban. A commenter in that thread tied such holds to a 120 to 180 day window under card network rules, one that support emails rarely shorten. If Stripe closes your account or cuts off your integration mid-cycle, that is the realistic picture: renewals stop now, and the money follows later.

Our underwriting team's view is the counterweight. A processor that already boards your shape prices it once. Google's Universal Commerce Protocol lists subscriptions among the categories it leaves out of its own native buying flow, so renewals still run on whichever account you hold.

As card networks keep revising how scheduled billing must work, I expect the gap between those two models to widen, not narrow. The businesses that move first will make that switch on their own timeline, with statements in hand and renewals still running, rather than on a platform's.

Frequently Asked Questions

What else do people ask about aggregators vs dedicated merchant accounts for subscriptions?

Most remaining questions come down to who controls the account, whether a platform can stop renewals without warning, and how quickly a recurring biller can move.

Is Stripe an aggregator or a merchant account?

Stripe is a payment aggregator: a provider that processes many businesses under its own master account instead of issuing each one a merchant ID. You get speed at signup. You do not get an account in your own name.

Can Stripe close my account or integration in the middle of a billing cycle?

Yes. In one public account of a frozen Stripe merchant, the status read "charges and payouts paused" before it narrowed to charges paused alone, and a paused charge means no renewal runs. I wish I could give you a reliable hold length, but the window quoted earlier comes from an anonymous commenter, not from Stripe. We also do not yet have client data on how recurring revenue holds up after a migration.

Do I need a dedicated merchant account for recurring billing?

Once subscriptions carry the business, I think so. Our underwriting team's view is that a processor prices the shape of a business, the application should describe that shape and its controls, and the real qualification question is whether the processor already boards it. Card networks are also revising their rules for subscription and recurring transactions, as Mastercard's published standards show.

How fast is onboarding with SeamlessChex?

SeamlessChex offers same-day onboarding with no contracts for established businesses. Underwriting still happens; it just happens once. You can accept credit card payments first, with ACH alongside, online or in person, and the contact page at seamlesschex.com/contact is where an application starts.

Written by

Jonathan Albert

Co-Founder, SeamlessChex

Jonathan Albert is Co-Founder of SeamlessChex, a credit card processing and fintech payments platform recognized on the Inc. 5000.

Connect on LinkedIn

SeamlessChex works with established businesses processing a minimum of $25,000 per month.

Need a processor?
Credit card processing that gets you approved—and keeps you processing.
Open a merchant account