Educational Guide
Merchant account and payment gateway are two of the most commonly confused terms in payment processing. They serve different roles — and understanding what each does helps you evaluate what your business actually needs and what you're already paying for.
Last updated: June 17, 2026
Quick Answer
A merchant account is a bank account that temporarily holds card payment funds before they transfer to your business account. A payment gateway is software that securely transmits card data to the processor. Modern processors like Stripe and Square bundle both into one product, so most small businesses don't need to manage them separately.
A merchant account is a type of bank account that allows a business to accept credit and debit card payments. When a customer pays by card, the funds from the transaction are deposited into the merchant account first — before being transferred to the business's primary operating bank account.
Merchant accounts are held by an acquiring bank (also called a merchant acquirer). The acquiring bank takes on the financial risk of processing card transactions on behalf of the merchant. This is why underwriting is required: the bank needs to evaluate whether the merchant's business type, volume, and history represent an acceptable level of risk.
There are two main types of merchant accounts: dedicated and aggregated. A dedicated merchant account is issued specifically to your business. An aggregated account (used by PayFacs like Stripe and Square) groups many businesses under one master account, with each operating as a sub-merchant.
A payment gateway is software that securely transmits payment data from a checkout form or point-of-sale terminal to the payment processor. It acts as the intermediary between the customer's card and the processor's authorization system.
The gateway handles three critical functions: encryption (protecting card data in transit), fraud screening (basic checks before sending to the processor), and authorization communication (sending the request and returning the approval or decline to the merchant's system).
Gateways can be hosted (the customer is redirected to the gateway's page to enter card details) or embedded (the card entry form appears on the merchant's own page, with data securely transmitted in the background). Hosted gateways reduce the merchant's PCI scope; embedded gateways offer a more seamless customer experience.
In a traditional payment setup, the gateway and merchant account are separate services. When a customer submits a card payment online, the flow is: customer → gateway (encrypts data) → processor (routes and authorizes) → card network → issuing bank → back through the chain. Settled funds land in the merchant account, then transfer to your operating bank.
In a modern bundled setup (Stripe, Square, Helcim, PayPal), the gateway, processor, and merchant account are all included in one product. You do not need to manage separate vendor relationships. This is one reason PayFacs and modern processors have become popular for SMBs.
Most small and mid-sized businesses today use a bundled solution where gateway, processing, and merchant account services are provided by one company. This simplifies setup, reduces vendors, and typically requires one contract.
Larger businesses with custom checkout requirements, specific hardware needs, or complex pricing structures may use separate gateway and merchant account providers. For example, a business might use Authorize.Net (gateway) with a traditional merchant acquirer — giving them more control over each component and the ability to switch one without changing the other.
Note: If you already have a merchant account through your bank or a traditional acquirer, you may need a compatible payment gateway. Verify compatibility before purchasing gateway services.
Before selecting a gateway, merchant account, or bundled solution, ask:
These errors cause merchants to overpay or make poor decisions when evaluating merchant accounts and gateways:
Use this checklist when evaluating your gateway and merchant account options:
Not as a separate product. Stripe, Square, and similar PayFacs provide bundled access to processing without requiring a separate dedicated merchant account. Your business processes under their master account as a sub-merchant.
A hosted gateway redirects customers to the gateway provider's page to enter card details, reducing the merchant's PCI scope. An embedded gateway shows a card entry form directly on the merchant's page, with data transmitted securely to the gateway in the background. Embedded gateways offer a more seamless checkout experience but require more technical implementation.
Often yes, if you have a separate gateway and merchant account. Check that your new gateway is compatible with your acquiring bank or merchant account provider before switching. If you use a bundled solution, switching processors typically changes both.
Some payment gateway providers charge a monthly fee for gateway access, in addition to per-transaction fees. In bundled solutions, gateway fees are typically included in the overall processing rate or monthly plan. Verify what gateway fees apply before signing up.
Use Fit Check to identify providers that may deserve closer research based on your business profile, or open the Cost Calculator to estimate your fees.