Payment gateway vs. merchant account: two jobs, one payment.

A payment gateway is the technology that securely carries card details from your website, invoice or virtual terminal to the processor, while a merchant account is the processing relationship that approves the payment and deposits the money into your business bank account. Businesses that take payments online or by keyed entry usually need both, and they can come from different providers.

Knowing which is which helps you read your statement, compare quotes and switch providers without rebuilding your website. It also explains why two separate lines can show up on your statement for what feels like one payment. Here is the plain version.

What a payment gateway does

Think of the gateway as the secure courier for payments that don’t go through a physical terminal. It:

• Collects card details on a checkout page, payment link or virtual terminal.
• Encrypts the data and sends it to the processor for approval.
• Returns the approval or decline to your website or software.
• Stores cards securely as tokens for recurring billing and repeat customers.
• Often adds fraud filters, reporting and invoicing tools.

Examples of gateways include Authorize.net, eProcessing Network, CyberSource and Paya. For in-person payments, many card terminals connect straight to the processor and don’t need a gateway at all.

What a merchant account does

A merchant account is your account with a processor and its sponsor bank that lets you accept card payments. It:

• Sends payments through the card networks to the customer’s bank for approval.
• Groups the day’s approved payments into a batch and settles them.
• Deposits the money, less fees, into your business bank account.
• Handles refunds, chargebacks and your monthly statement.
• Sets your pricing: interchange, card-network fees and the processor’s margin.

The merchant account is where most of your processing cost lives. See what is a merchant account for more detail.

Side by side

	Payment gateway	Merchant account
Main job	Carry card data securely from your site or software	Process the payment and deposit the funds
Needed for	Online, invoice, keyed and recurring payments	Every card payment
Typical fees	Monthly gateway fee and per-transaction gateway fee, depending on provider	Interchange, card-network fees and processor margin
Who you deal with	A gateway provider	A processor and its sponsor bank
Switching	Can often stay while you change processors	Can change while you keep your gateway

One online payment, start to finish

1. A customer enters their card on your checkout page or invoice link.
2. The gateway encrypts the details and sends them to your processor.
3. The processor, through your merchant account, asks the card network and the customer’s bank to approve it.
4. The approval travels back through the gateway to your website, and the customer sees a confirmation.
5. At the end of the day, the batch settles and your merchant account deposits the funds, less fees, into your bank.

The gateway also affects your security work. A gateway with a hosted payment page or secure fields keeps card numbers off your own servers, which usually makes PCI compliance simpler. If your website collects card numbers directly, more of your systems fall under PCI rules. See what is PCI compliance.

Gateway fees and processing fees should be listed separately on your statement. If they are blended into one number, ask for a breakdown.

Bundled providers and payment facilitators

Some providers bundle the gateway and processing into one sign-up. Many flat-rate platforms work as payment facilitators: you become a sub-merchant under their master account instead of getting your own merchant account. That is quick to start and can suit small or occasional sellers. The trade-offs usually include:

• A flat rate that doesn’t show interchange, so you can’t see what the card networks charge versus the provider’s margin.
• Less flexibility to move: your checkout and stored cards may be tied to that provider.
• Account holds or reviews that can be harder to resolve without a dedicated contact.

As volume grows, many businesses move to their own merchant account with a separate gateway for more transparent pricing. Our guide on merchant account vs. payment facilitator compares them in depth.

Why the difference matters when you switch

Because the gateway and merchant account are separate, you can often change one without touching the other:

1. Keep your gateway, change processors. If your website, cart or invoicing connects to the gateway, switching processors can be a settings change in the gateway rather than a website rebuild. Stored cards may stay in place.
2. Keep your processor, change gateways. Useful if you need better features, such as recurring billing, Level 2 and Level 3 data or invoice links.
3. Check compatibility first. Not every gateway works with every processor, and not every cart works with every gateway. A quick check before you commit saves a lot of rework, especially if you sell through several channels.

For the full process, see what happens when you switch processors. If you bill business customers online, read payment links and invoicing and recurring billing too.

What PayZoom does

PayZoom provides the merchant account and connects it to a payment gateway, either the one you already use or one of our gateway partners: Authorize.net, eProcessing Network, CyberSource or Paya. We are platform-agnostic, so we fit your existing POS, gateway or cart. We also handle Level 2 and Level 3 setups, ACH and custom API work. We recommend Interchange-Plus pricing, with our margin on its own line and never increased, in writing. No early termination fees, and a real person answers when you call.