---
title: "Merchant account vs payment facilitator: which one does your business need?"
seoTitle: "Merchant Account vs Payment Facilitator: Which to Choose"
description: "A merchant account gives you your own merchant ID and pricing. A payment facilitator lets you start faster as a sub-merchant. See control, holds and fit."
date: "2026-11-08"
updated: "2026-11-15"
category: "payments"
author: "BlindPay Team"
faq:
  - q: "Is Stripe a merchant account?"
    a: "No. A merchant account is an account with an acquiring bank that settles card sales to your business under your own merchant ID. Teams that sign up with Stripe use a model where Stripe's guide says sub-merchants are not required to register their own merchant IDs, because activity is pooled under the platform's master merchant ID. Dedicated accounts are a different, direct arrangement."
  - q: "What is a master merchant ID?"
    a: "A master merchant ID, or master MID, is the single merchant identifier a payment facilitator holds with its acquiring bank. Card payments from all of its sub-merchants run under it, so the sub-merchants do not register their own MIDs. The payfac carries the account-level obligations to the acquirer and the card networks, and settles funds onward to each sub-merchant."
  - q: "Can a payment facilitator hold or freeze my funds?"
    a: "Yes, it can. The payfac must monitor sub-merchant activity under card network rules and answers to its acquirer, so it may delay payouts, hold a reserve or pause processing when it sees risk or missing verification. Stripe's identity verification docs say it temporarily pauses charges and payouts when required information is not provided or verified in time. Read the hold terms before signing."
  - q: "What volume justifies a dedicated merchant account?"
    a: "There is no universal number. Card network rules and each provider set the point at which a sub-merchant must sign a direct agreement with the acquiring bank, and Stripe's payfac guide gives no figure. Ask your payfac for its threshold in writing, then compare it with your monthly card volume, chargeback record and need for control over pricing and holds."
---

A dedicated merchant account gives your business its own merchant ID (MID, the identifier an acquiring bank uses to track your card sales), its own underwriting and its own pricing. A payment facilitator lets you accept cards as a sub-merchant under its master MID. That is faster to start, but you get less control over pricing, holds and risk.

This guide compares the two models and explains when to move from one to the other, as of November 2026. BlindPay publishes this guide.

**Key takeaways**

- A dedicated merchant account means your own MID, your own underwriting file and a contract with an acquiring bank. It takes longer to set up and gives you the most control.
- A payment facilitator (payfac) pools its sub-merchants under one master MID, so sub-merchants do not register their own MIDs and can start quickly.
- Under card network rules a registered payfac must do due diligence on each sub-merchant, monitor activity, maintain PCI compliance and use settlement funds only to pay sub-merchants (per Stripe's payfac guide).
- A sub-merchant above a volume threshold must sign a direct merchant agreement with the acquiring bank. That threshold is set by card network rules and each provider, so ask for yours in writing.
- Becoming a payfac yourself is a regulated build, not a checkbox: the guide counts network registrations, risk systems, PCI validation and licenses.

## What is a dedicated merchant account?

A dedicated merchant account is a contract between your business and an acquiring bank (the bank that accepts card payments for merchants and settles them to you). It carries your own MID, so your sales, chargebacks and fees are tracked under your name rather than under a platform's.

To get one, you go through full underwriting: the acquirer reviews your owners, your business model and your finances. We cover that process in [merchant underwriting and onboarding](/resources/more/merchant-underwriting-onboarding-process). In return you can negotiate pricing, choose your processor and gateway, and keep your processing history if you change providers.

You also take on more work. You maintain the relationship, respond to the acquirer's requests, and follow PCI rules yourself. For the roles around the account, see [acquirer vs processor vs gateway vs PSP](/resources/more/merchant-acquirer-vs-payment-processor-vs-gateway-vs-psp).

## What is a payment facilitator (payfac)?

A payment facilitator is a company that holds one master merchant account and lets many smaller businesses, called sub-merchants, accept cards under it. Stripe's payfac guide says sub-merchants are not required to register their own MIDs.

The payfac sits between the sub-merchants and the acquiring bank. It signs up sellers through a short online form, verifies them, and pools their transactions under its master MID. That is why a new business can often accept a first payment within a single onboarding session, instead of waiting for a bank to underwrite it.

A **sub-merchant** is simply a business that processes cards through a payfac instead of holding its own acquirer contract. An aggregator is a close variant: the platform holds the MID and settles to you, with fewer controls on your side.

## How do onboarding speed, pricing, fund holds and control compare?

A payfac wins on speed and simplicity. A dedicated account wins on control, price negotiation and portability. Holds are the sharpest difference: a payfac manages risk for its whole portfolio, so it can act on your funds faster than an acquirer that knows you directly.

| | Dedicated merchant account | Payment facilitator (sub-merchant) |
| --- | --- | --- |
| Merchant ID | Your own MID | Shared under the payfac's master MID |
| Onboarding | Full underwriting by the acquirer, often with documents and review time | Short application and automated checks, with review when risk is flagged |
| Pricing | Negotiated, often interchange-plus (see [pricing models](/resources/more/interchange-plus-vs-flat-rate-break-even-by-volume)) | Usually standardized, often a flat rate set by the payfac |
| Fund holds | Set in your contract, typically with notice | Payfac can hold or pause under its own terms and network rules |
| Control over risk | Your history sits under your MID | Payfac monitors all activity and may act at portfolio level |
| Portability | Your processing history belongs to your MID | History sits under the payfac's MID, so it is harder to carry |
| Effort to run | Higher: contract, PCI and acquirer relationship | Lower: the payfac carries most obligations |

On holds, the evidence in provider documentation is concrete. Stripe's payouts documentation says the first payout is typically scheduled 7 to 14 days after the first successful live payment, depending on industry, country and risk. Its identity verification documentation says Stripe temporarily pauses charges and payouts if required information is not provided or verified in time. Treat both as examples of how a payfac can manage funds, not as a statement about every payfac. For the mechanics, read [rolling reserves and payout holds](/resources/more/rolling-reserves-payout-holds-frozen-funds).

## When does a sub-merchant need a direct merchant agreement?

When its volume passes a threshold. Stripe's payfac guide says that if a sub-merchant exceeds a certain threshold of transaction volume, it must enter into a direct merchant agreement with the acquiring bank.

The guide gives no number, and we do not invent one. Card network rules and each provider set the threshold, and it can differ by network and by acquirer. Ask your payfac three questions: what is the threshold, how is it measured, and what happens to your pricing and payout schedule when you cross it. Get the answers in writing before you grow into it.

This rule is one reason a payfac suits early volume and not forever. Once a direct agreement is required, you are in the dedicated-account model anyway, so it is better to plan the move than to be surprised by it.

## When should a business move from a payfac to its own merchant account?

Move when the payfac's limits cost you more than a dedicated account's effort would. The common triggers are a volume threshold, a hold that hurt cash flow, pricing you want to negotiate, or a need for your own processing history.

Use this checklist before you switch:

1. Ask your payfac for the direct-agreement threshold and any exit terms in writing.
2. Pull 6 to 12 months of processing statements, including chargeback and refund counts, to show an acquirer your history. Your payfac may hold it under its own MID, so request it early.
3. Prepare your underwriting file: owner IDs, business registration, bank statements, website and policies.
4. Collect quotes from at least two acquirers and compare them on the same inputs, as shown in [how to choose a merchant acquirer](/resources/more/how-to-choose-a-merchant-acquirer).
5. Ask the new acquirer about reserves, payout timing and chargeback limits before you sign.
6. Plan the gateway or processor change, and a parallel-run period so checkout is never down.
7. Move saved customer payment tokens by agreement between the old and new processor, if you store cards for repeat billing. Confirm token portability first, because some providers do not export tokens.
8. Close the payfac account only after chargebacks on past sales have run their course.

Step 8 matters because disputes can arrive weeks after a sale. See [chargebacks explained](/resources/more/chargebacks-explained-ratios-vamp-ecm) for the timelines.

## What does it take for a platform to become a payfac?

It takes network registration, risk operations, security validation and licensing, so most platforms rent the capability. Stripe's guide says a payfac must register with each card network in each country, and lists initial fees of $5,000 each for Visa and Mastercard, with annual re-registration.

The same guide lists the rest of the build: due diligence and monitoring systems for every sub-merchant, PCI validation each year, fraud tooling, dispute handling, payout operations and, in some cases, money transmitter licenses. Those are the guide's own estimates for a traditional payfac build, and it is a document from a company that sells a managed alternative, so read the cost figures as a picture of scope rather than a quote.

The practical choice for most software platforms is between being a payfac (high control, high obligation) and embedding a provider's payfac product (faster, less control, less revenue share). The obligations in the previous paragraph are what you are buying out of with the second route.

## What is an ISO or reseller?

An ISO (independent sales organization) is a company that sells acquiring services on behalf of an acquiring bank or a processor, usually earning a share of the fees. It does not hold the MID itself as a payfac does.

With an ISO, you still get your own MID under the acquirer, so the contract and underwriting follow the dedicated-account model. The ISO is your sales and support contact. A reseller is a similar distribution role, often for a software vendor that bundles processing.

The practical difference from a payfac is who carries the obligations. With an ISO, the acquiring bank and your own MID carry them. With a payfac, the payfac carries them under its master MID. When you evaluate an offer, ask which of the two you are being sold, because the same sales brochure can describe either.

## How do I decide?

Choose by volume stability, risk profile and business model, then confirm with your provider's own thresholds. There are no universal cutoffs: each provider sets them, so the table uses descriptions, not numbers.

| Situation | Better starting point | Why |
| --- | --- | --- |
| New business, low or unpredictable volume | Payfac | Fast start, little paperwork, no contract negotiation |
| Steady, predictable monthly volume and a clean record | Dedicated merchant account | Negotiated pricing and your own history can pay off |
| Higher chargeback or refund risk, or a category some providers restrict | Check both; expect more underwriting either way | A payfac may decline or hold; an acquirer may price risk or require a reserve |
| Marketplace or platform paying many sellers | Payfac or an embedded payfac product | Sellers need quick onboarding under your platform |
| Multi-country sales needing local acquiring | Dedicated accounts per region, or an orchestration layer | Local MIDs can help approval rates (see [local vs cross-border acquiring](/resources/more/local-acquiring-vs-cross-border-acquiring)) |
| Need to negotiate fees or choose your processor | Dedicated merchant account | Only a direct contract gives you that lever |

If more than one row fits, start with the faster model and plan the move: payfac first, dedicated account when your volume and history justify the extra work.

## What if my platform pays sellers across borders?

If you pay out sub-merchants or sellers in other countries, the payout leg is a separate problem from card acceptance. A payfac or acquirer settles card sales to you; moving money onward to sellers in several currencies needs its own rails.

BlindPay is not a card acquirer, payment gateway or card processor, and it has no merchant IDs. It works alongside an acquirer as the cross-border payout, collection and stablecoin settlement layer, so you do not have to build that leg yourself. See [cross-border payouts for marketplace sellers and contractors](/resources/more/cross-border-payouts-marketplace-sellers-contractors), the [payouts docs](/docs/payouts) and the [global payments overview](/global-payments).

If you sell digital products and are weighing a merchant of record, read [merchant of record vs payment facilitator](/resources/more/merchant-of-record-vs-payment-facilitator).

## Methodology and sources

External sources, all read in November 2026: [Stripe's payfac guide](https://stripe.com/guides/payfacs) (undated page, copyright 2026; the source for master MID, payfac duties, the direct-agreement rule and registration fees), [Stripe payouts documentation](https://docs.stripe.com/payouts) (undated; first-payout timing), [Stripe identity verification for connected accounts](https://docs.stripe.com/connect/identity-verification) (undated; pauses on charges and payouts) and [Adyen onboarding guidelines](https://docs.adyen.com/platforms/verification-requirements/onboarding-guidelines) (copyright 2026, undated; verification and its effect on onboarding delays).

BlindPay docs: [Payouts](/docs/payouts). We did not find a source that states the sub-merchant volume threshold as a figure, so this page does not give one.

## What to do next

Read [how to choose a merchant acquirer](/resources/more/how-to-choose-a-merchant-acquirer) for the comparison questions to ask once you know which model you want. For the foundations behind both models, start with [what merchant acquiring is](/resources/more/what-is-merchant-acquiring).

*This article is general information, not legal, tax, or financial advice.*
