Merchants setting up WooCommerce payments quickly run into three terms that sound interchangeable: payment gateway, payment processor, and merchant account. They’re not the same thing, but they’re frequently bundled together, which is why the distinction gets blurry.
This guide clarifies exactly what each component does, when you need them separately, and when a single integration handles all three.
Skip the three-vendor setup. ConvesioPay combines gateway, processor, and merchant account into one WooCommerce-native integration as a certified Adyen partner. Get started →
1. What a Payment Gateway Does
A payment gateway is the component that securely transmits transaction data from your store to the payment processor. It sits between your WooCommerce checkout and the broader payment network.
Specifically, a gateway handles:
- Encryption — card data is encrypted before it leaves the customer’s browser, using TLS and often tokenization (replacing the card number with a non-sensitive token)
- Transmission — the encrypted data is sent to the processor for authorization
- Response delivery — the approval or decline result is returned to your store
- PCI scope reduction — a hosted gateway keeps raw card data off your server entirely, dramatically reducing your PCI DSS compliance burden
In traditional setups, the gateway was a separate vendor, companies like Authorize.net or NMI sold gateway services independently of processing. Today, most modern payment solutions bundle the gateway with processing, but the gateway function still exists within that bundle.
2. What a Payment Processor Does
A payment processor handles the actual routing of transactions between your acquiring bank and the card networks (Visa, Mastercard). Where the gateway is about secure transmission, the processor is about transaction execution.
A processor handles:
- Routing authorization requests through Visa/Mastercard to the issuing bank
- Receiving and relaying approval or decline responses
- Batching captured transactions for settlement
- Managing the flow of funds between card networks and the acquiring bank
- Fraud screening and risk management (in modern processors)
The processor works in milliseconds and is largely invisible to merchants, until a transaction fails, a decline rate spikes, or a chargeback arrives.
3. What a Merchant Account Is
A merchant account is a specialized bank account that holds funds from card transactions during the settlement process — the 1–2 day window between when a transaction is authorized and when funds reach your business bank account.
Traditional merchant accounts required a formal application to a bank, underwriting review, and an ongoing relationship with that acquiring bank. The merchant account was separate from both the gateway and the processor.
Today, many merchants use a payment facilitator (PayFac) model instead. Under this model, the PayFac holds a master merchant account and onboards merchants as sub-merchants — eliminating the need to apply for a dedicated merchant account. This is how Stripe, Square, and PayPal work. It’s also how ConvesioPay works: merchants access Adyen’s acquiring infrastructure through ConvesioPay without needing their own direct Adyen merchant account.
4. How They Relate: A Side-by-Side Comparison
| Component | Primary function | Who sees it | Separate vendor needed? |
|---|---|---|---|
| Payment gateway | Encrypts and transmits card data | Merchant (integration) and customer (checkout form) | Rarely in modern setups |
| Payment processor | Routes transactions through card networks | Merchant (reporting, declines) | Yes — always required |
| Merchant account | Holds funds during settlement | Merchant (payouts) | Not under the PayFac model |
The simplest way to think about it: the gateway is the pipe, the processor is the engine, and the merchant account is the holding tank. You need all three functions to accept card payments, but they don’t need to come from three different vendors.
5. Traditional Setup vs. Modern Bundled Setup
Traditional Three-Vendor Setup
Until the mid-2010s, most WooCommerce merchants needed:
- A merchant account from a bank or ISO (independent sales organization) — required underwriting, monthly fees, and a multi-year contract
- A payment gateway contract (e.g., Authorize.net) — monthly fee plus per-transaction gateway fee
- A processor contract — often bundled with the merchant account but sometimes separate
This meant three vendors, three contracts, three monthly fees, and three support relationships to manage when something broke.
Modern Bundled Setup (PayFac Model)
Modern payment facilitators bundle all three functions:
- Gateway functionality is built into the checkout widget or API
- Processing runs through the PayFac’s acquiring infrastructure
- Merchant accounts are aggregated under the PayFac’s master account
The trade-off is that under the PayFac model, the processor has more control over your funds — which is why account freezes and holds (common complaints about Stripe and PayPal) happen more frequently than under a dedicated merchant account arrangement.
6. Which Do You Actually Need?
| Situation | What you need |
|---|---|
| WooCommerce store, getting started | A bundled PayFac solution (gateway + processor + merchant account in one) |
| High-volume merchant ($500K+/year) seeking lower rates | A processor offering interchange++ pricing with direct acquiring relationships |
| Regulated or high-risk industry | A processor with dedicated high-risk merchant account support and underwriting |
| Needing multi-currency or international payments | A processor with direct acquiring in target markets (not just FX conversion) |
7. How ConvesioPay Handles the Gateway/Processor/Merchant Account Stack
ConvesioPay is a certified Adyen partner that provides all three functions through a single WooCommerce integration:
- Gateway — ConvesioPay’s checkout widget handles tokenization, encryption, and Apple Pay / Google Pay at product page, cart, and checkout. No separate gateway contract or configuration required.
- Processing — transactions route through Adyen’s payment infrastructure — the same network used by Uber, eBay, and Airbnb — with built-in 3DS routing, fraud rules, and intelligent authorization logic.
- Merchant account — ConvesioPay operates as a PayFac on Adyen’s infrastructure. Merchants don’t need to qualify for a direct Adyen account to access Adyen-level acquiring.
The result: one integration, one support relationship, and interchange++ pricing instead of blended flat rates. For a detailed look at how this affects your fees, see What Is Payment Processing? and Credit Card Processing Fees Explained.