BlogPayments & POS2 min read

Merchant Account vs Processor vs Gateway, Untangled

By Calvin E., Director of BatchOut

The short answer

A merchant account is where card funds settle before reaching your bank. A payment processor moves the transactions between banks and card networks. A payment gateway is the secure online pipe into that system. Modern providers bundle all three, which is why the terms blur, and unbundling them explains every line on your statement.

What Does Each Piece Actually Do?

Three jobs, three terms, one transaction.

PieceJobYou interact with it when
Merchant accountHolds settled card funds under your business before depositUnderwriting, deposits, holds, and reserves
ProcessorRoutes authorizations and settlements across networks and banksRates, statements, batch times, support
GatewayEncrypts and carries online payments to the processorEcommerce checkout, invoicing, virtual terminal

Why Does the Distinction Matter on Your Statement?

Because each layer can charge you. A legacy stack pays a merchant account provider, a processor markup, and a gateway fee, Authorize.net's published $25 a month plus 10 cents per transaction is a clean example of the third layer priced separately. A bundled platform like Square or Stripe collapses everything into one published rate, 2.6% plus 10 cents in person or 2.9% plus 30 cents online, with the merchant account function aggregated under the platform's own master account.

That aggregation is the trade: instant onboarding and one bill, in exchange for less individual underwriting, which is why holds on aggregated platforms make headlines and why established merchants often graduate to dedicated merchant accounts with interchange-plus pricing.

Which Setup Fits Which Business?

A new or small seller wants the bundle: one provider, published flat rates, running today. An established merchant past roughly $20,000 to $30,000 a month wants a dedicated merchant account on interchange plus, where the published wholesale tables plus a thin markup beat flat rates, with a gateway added only if online volume warrants. High risk categories skip the choice: aggregated platforms exit them, so a dedicated high risk merchant account at the published 2.5% to 5% range is the path. The wrong setup is usually a size mismatch: a $100,000-a-month business on starter flat rates, or a weekend seller carrying $25 in monthly gateway fees it never uses.

How Do You Audit Your Own Stack?

Twenty minutes with one statement answers all of it.

  • Identify who holds the merchant account: your name on a dedicated MID, or aggregated under a platform
  • Find every layer charging you: processing rate, monthly fees, gateway line, PCI fee
  • Compute the effective rate: total fees divided by total volume
  • Over $25,000 a month on flat rate: get an interchange-plus quote
  • Paying separate gateway fees on trivial online volume: consolidate into the bundle

Commonly Asked Questions

Is Square a merchant account?
Functionally you process under Square's aggregated master account rather than your own dedicated MID. That enables instant onboarding at published flat rates, with less individual underwriting than a dedicated merchant account provides.
Do I need all three pieces?
Every card-accepting business uses all three functions, but you only shop them separately in legacy or high-volume setups. Bundled platforms deliver the trio under one published rate, which serves most businesses until volume justifies unbundling.
Why did my funds get held?
Holds live at the merchant account layer: risk reviews on spikes, anomalies, or chargebacks. Aggregated accounts run automated risk at platform scale; dedicated accounts put a named underwriter and support desk between you and a freeze.
Who does BatchOut set merchants up with?
BatchOut places merchants on the setup that fits the volume: bundled platforms for simple starts, dedicated merchant accounts on interchange plus as volume grows, and specialized high risk acquirers when the category requires it.

Keep reading

BatchOut

Put This to Work in Your Business.

This is the thinking behind BatchOut. One conversation makes it specific to you.