Merchant Account vs Payment Aggregator

Most businesses that accept cards believe they have a merchant account. Many of them do not. What Stripe, Square, PayPal, and Shopify Payments provide is access to their merchant account, not a dedicated account of the merchant’s own. The distinction is not technical pedantry. It is the operational explanation for why accounts on these platforms get frozen without warning, why high-risk businesses get terminated, and why the chargeback monitoring that applies to a merchant using Stripe is different from the monitoring that applies to a merchant with a dedicated account at an acquiring bank.

Understanding the structural difference between a payment aggregator and a dedicated merchant account is the most useful single piece of information a high-risk merchant can have before they choose how to process.

What a Payment Aggregator Is

A payment aggregator is a company that holds a single master merchant account with an acquiring bank and allows other businesses to process payments through it as sub-merchants. Stripe, Square, PayPal, and Shopify Payments are the most widely used examples. When a business signs up with any of these platforms, they are added to the aggregator’s master account. All transactions processed by every sub-merchant on the platform flow through the same master MID. Stripe’s own published resource on the aggregator model, updated August 2026 at stripe.com, confirms this directly: the aggregator operates under a master merchant account and processes transactions on behalf of multiple businesses, which operate as sub-merchants under that account.

The aggregator handles underwriting, compliance, fraud monitoring, and settlement for the entire sub-merchant portfolio. The individual merchant does not have a direct relationship with the acquiring bank. The billing descriptor on the cardholder’s statement typically reads as the aggregator’s name followed by the merchant name, rather than the merchant’s own name standing alone.

The practical advantages for most low-risk businesses are significant. Signup takes minutes, there is no underwriting package to assemble, flat-rate pricing is predictable at low volumes, and integrations are well-documented. For a new business processing under $10,000 per month in a standard retail or service category, these advantages outweigh the structural limitations.

What a Dedicated Merchant Account Is

A dedicated merchant account is a direct relationship between the merchant and an acquiring bank or its ISO, with a unique MID assigned to that merchant’s specific business. All transactions processed on that MID belong to that merchant alone. The chargeback ratio, fraud monitoring, and reserve calculations apply only to that merchant’s own volume.

The underwriting process for a dedicated account takes longer because the acquirer is making a specific credit decision about a specific business rather than accepting a sub-merchant into a pooled risk structure. For high-risk merchants, that process typically takes 5 to 15 business days. The output is a contract with defined reserve terms, a specific processing rate, and a volume limit that can be adjusted over time as the merchant establishes a track record.

The billing descriptor on the cardholder’s statement is the merchant’s own name, or a name the merchant configures at the acquirer level. This alone reduces unrecognized charge disputes for businesses where cardholder recognition of the charge drives dispute rates.

The Structural Difference That Matters for High-Risk Merchants

The aggregator model is built for the average merchant. Risk management in an aggregator portfolio is automated and portfolio-wide. When fraud rates rise in a category, all merchants in that category face tighter controls or termination. When a regulatory or reputational event affects a vertical, the aggregator’s response affects every merchant in that vertical simultaneously.

This is not a hypothetical risk. Square announced it is closing all CBD and hemp merchant accounts by November 5, 2026, affecting every merchant in that category regardless of individual chargeback history or compliance record. Stripe has progressively tightened its acceptable use policy across subscription continuity, nutraceuticals, telemedicine, and digital goods categories. PayPal maintains documented fund hold practices that have affected merchants across multiple categories with holds of $10,000 to over $100,000 for 90 to 180 days.

Aggregator termination is also algorithmically driven. A merchant whose volume spikes, whose chargeback ratio crosses a threshold, or whose product category gets recoded by a compliance review can receive an account termination notice with limited warning and limited appeal. The aggregator is managing a portfolio. The individual merchant’s account is one data point in a risk model that does not account for the merchant’s specific business circumstances.

A dedicated merchant account operates differently. The acquiring bank has underwritten the specific merchant’s business. Reserve terms are defined in a contract. Processing limits are set based on the merchant’s specific file. A chargeback spike triggers a conversation with a relationship manager before it triggers account action. The merchant has a direct advocate inside the acquiring relationship.

Pricing at Scale

Aggregator flat-rate pricing is competitive at low volumes and becomes progressively less competitive as volume grows. Stripe’s published standard rate is 2.9 percent plus 30 cents per transaction. At $10,000 per month, this is $290 in processing fees before the per-transaction component. At $100,000 per month, it is $2,900. Dedicated merchant accounts with interchange-plus pricing pass the actual interchange cost through to the merchant and add a fixed margin. At meaningful volume, interchange-plus is materially cheaper than flat-rate aggregator pricing.

High-risk merchant account rates run higher than standard interchange-plus: typically 3 to 8 percent depending on the vertical, chargeback history, and reserve requirements. This premium reflects the underwriting risk rather than the cost structure of the payment rail. For merchants in categories that aggregators will not accept, the comparison is not between aggregator pricing and high-risk account pricing. It is between high-risk account pricing and no card processing at all.

What Aggregator Termination Does and Does Not Do

A merchant terminated by Stripe, Square, or PayPal does not receive a MATCH listing. MATCH entries are filed by acquiring banks for specific cause. An aggregator termination, even for chargeback violations, does not trigger a MATCH listing because the aggregator is not the acquiring bank. The merchant terminated by Stripe can apply to a dedicated high-risk acquirer without MATCH being the obstacle.

This distinction matters because merchants who are terminated by aggregators often believe they have been permanently flagged across the industry. They have not. They have been terminated by one company’s risk system. A dedicated high-risk acquirer that underwrites their vertical will review their file independently, and the Stripe termination appears as prior processing history context rather than a hard exclusion.

The exception is a merchant terminated by an aggregator that subsequently applies to another aggregator and is terminated there as well. Multiple aggregator terminations in a short period, combined with a pattern of elevated chargebacks, creates a processing history that dedicated acquirers will scrutinize carefully even without a MATCH listing.

When Each Model Makes Sense

An aggregator is the right starting point for a business in a standard low-risk category processing under $50,000 per month that needs fast setup and predictable flat-rate pricing. The structural limitations are real but manageable when the business is not in a restricted category and is not approaching volume thresholds where interchange-plus pricing would be meaningfully cheaper.

A dedicated merchant account is the right structure for any high-risk business, any business in a restricted or regulated category, any business processing above $50,000 per month where pricing at scale matters, and any business for whom account stability is operationally critical. A telemedicine clinic, a supplement seller, a subscription continuity business, or a merchant who has already been terminated by an aggregator all need a dedicated account underwritten for their specific vertical.

The full picture of how payment gateways connect to merchant accounts and what the technical infrastructure behind processing actually looks like is in the gateways hub of this site. The complete overview of what a dedicated high-risk merchant account involves, how underwriting works, and what happens after approval is in the high-risk merchant accounts hub.

For merchants who need processing and cannot wait for a traditional underwriting timeline, RiskPay operates on non-custodial rails that do not require the underwriting package a dedicated account requires. It does not hold funds in a custodial account and does not have the freeze risk inherent in the aggregator model. Settlement goes directly to a merchant wallet in USDC on Polygon.

Frequently Asked Questions

Is Stripe a merchant account?

No. Stripe is a payment aggregator. Merchants who process through Stripe are sub-merchants under Stripe’s master merchant account. They do not have their own dedicated MID or a direct relationship with an acquiring bank. The same is true of Square, PayPal, and Shopify Payments.

Does a Stripe or Square termination create a MATCH listing?

No. MATCH listings are filed by acquiring banks for terminations caused by specific violations such as excessive chargebacks, fraud, or AML issues. Aggregator terminations by Stripe, Square, or PayPal do not result in MATCH listings because these companies are not acquiring banks. A merchant terminated by an aggregator can apply to a dedicated high-risk acquirer without MATCH being the obstacle.

When should a merchant move from an aggregator to a dedicated merchant account?

When the business is in a restricted or regulated category that the aggregator does not support, when monthly volume exceeds $50,000 and interchange-plus pricing would be meaningfully cheaper than flat-rate, when account stability is operationally critical, or after an aggregator termination. High-risk merchants in categories the major aggregators restrict should start with a dedicated account rather than attempting aggregator processing.

What is the main risk of using a payment aggregator for a high-risk business?

Algorithmic termination without warning. Aggregators manage portfolios using automated risk systems. When a category triggers elevated risk signals, the aggregator’s response affects every merchant in the category regardless of individual performance. A merchant with a clean chargeback history can be terminated because other merchants in the same category drove portfolio-level risk metrics above the aggregator’s internal thresholds.