If you’ve ever researched payment solutions for your WooCommerce store, you’ve almost certainly encountered both “merchant account” and “payment gateway”, often in the same sentence, sometimes used interchangeably. They’re not the same thing, and understanding the difference helps you make a better decision about your payment setup.
Not sure which you need? ConvesioPay handles both, one WooCommerce-native integration as a certified Adyen partner, no separate accounts required. Get started →
1. What a Merchant Account Is
A merchant account is a specialized holding account that sits between a customer’s card payment and your business bank account. When a transaction settles, funds move from the issuing bank into your merchant account first, then your acquirer transfers the net amount (after fees) to your regular bank account on a scheduled basis, typically every 1–2 business days.
Merchant accounts come in two forms:
| Type | How it works | Who it’s for |
|---|---|---|
| Dedicated merchant account | Your business has its own account with an acquiring bank. Requires underwriting approval. | Higher-volume merchants, regulated industries, businesses wanting full control over funds |
| Aggregated merchant account (PayFac) | You’re a sub-merchant under the payment facilitator’s master account. Instant approval, no underwriting. | New businesses, lower volume, merchants prioritizing speed of setup |
The practical difference: a dedicated merchant account gives you more stability and typically lower rates at volume. An aggregated account is faster to open but gives the PayFac (Stripe, PayPal, Square) more leverage over your funds, including the ability to hold or freeze them.
2. What a Payment Gateway Is
A payment gateway is the technology layer that securely captures card data at your checkout, encrypts it, and transmits it to your payment processor for authorization. It’s the interface between your WooCommerce store and the payment network.
Key gateway functions:
- Displaying the checkout form (hosted or embedded)
- Tokenizing card data so raw numbers never touch your server
- Encrypting and transmitting authorization requests
- Returning the approval or decline result to your store
- Supporting payment methods like Apple Pay, Google Pay, and BNPL at checkout
The gateway is what your customers actually interact with when they enter card details. A well-optimized gateway, one that loads fast, supports express checkout buttons, and minimizes form fields, directly affects conversion rates. ConvesioPay Q1 2026 data shows that Apple Pay, enabled through ConvesioPay’s gateway, delivers a decline rate less than half that of regular card payments, and accounts for 13.7% of all settled transactions on the network.
3. The Core Difference
| Merchant Account | Payment Gateway | |
|---|---|---|
| What it is | A financial account for holding funds | A technology layer for capturing and transmitting data |
| Primary role | Receives settled funds from card networks | Transmits transaction data securely to the processor |
| Who provides it | An acquiring bank or PayFac | A payment technology company (often bundled with processing) |
| What happens without it | No way to receive card payments | Card data can’t be transmitted securely |
| Separate vendor? | Not always — PayFac model aggregates this | Rarely standalone today — bundled with processors |
4. Do You Need Them Separately?
In most modern WooCommerce setups, you don’t manage a gateway and merchant account as separate relationships. Payment facilitators bundle both, along with the processor into a single integration. This is how Stripe, PayPal, Square, and ConvesioPay work.
The scenarios where you might manage them separately:
- You already have a dedicated merchant account and want to add a gateway that connects to your existing acquirer, common for large enterprises with existing bank relationships
- You operate in a regulated industry where your merchant account requires specialized underwriting that a generic PayFac won’t provide
- You’re building a custom checkout and need to integrate a gateway API directly into your platform
5. How the PayFac Model Changed Everything
Before payment facilitators existed (pre-2010), every merchant needed a dedicated merchant account from a bank, a separate gateway contract, and a processor agreement. This meant weeks of underwriting, multiple monthly fees, and three vendors to call when something broke.
Payment facilitators simplified this by aggregating thousands of merchants under one master merchant account. The trade-off was control: the PayFac can hold funds, request additional documentation, or terminate accounts, as many Stripe and PayPal merchants have discovered.
ConvesioPay operates as a certified Adyen partner using a similar model, but with dedicated onboarding, a named account manager, and a support team that responds directly rather than through automated queues. Merchants get the simplicity of a PayFac setup with the support model of a dedicated account relationship.
6. PCI Compliance Implications
Your gateway choice directly affects your PCI DSS compliance scope, how much security work you’re responsible for.
| Gateway type | How card data is handled | PCI scope |
|---|---|---|
| Hosted gateway (redirect) | Customer leaves your site to complete payment | SAQ A — lowest possible scope |
| Embedded hosted fields | Card fields load from the gateway provider’s servers, not yours | SAQ A-EP — still low scope |
| Self-hosted | Card data passes through your server | SAQ D — full PCI compliance required |
ConvesioPay’s checkout widget uses embedded hosted fields — card data is captured and tokenized on Adyen’s infrastructure before it ever reaches your server. This keeps WooCommerce merchants in SAQ A-EP territory without custom development work. For more on managing PCI scope, see PCI Compliance for Small Business.
7. Which Setup Is Right for Your WooCommerce Store?
| Situation | Recommended approach |
|---|---|
| New store, getting started quickly | Bundled PayFac (gateway + processor + merchant account in one) |
| Scaling past $500K/year, concerned about fees | Processor with interchange++ pricing and dedicated support |
| Regulated or high-risk vertical | Processor with high-risk underwriting and dedicated merchant account |
| Already have a merchant account | Gateway that integrates with your existing acquirer |
For most WooCommerce merchants, a bundled solution is the right answer — the question is which one. ConvesioPay is built specifically for WooCommerce: a certified Adyen partner offering a single integration that covers gateway, processing, and merchant account infrastructure, with interchange++ pricing and support from Convesio’s team.