---
title: "Payment gateway vs payment processor: what’s the difference, and do you need both?"
slug: payment-gateway-vs-payment-processor
excerpt: "Every card payment needs a gateway and a processor. Here’s what each one does, and when you need to choose them separately."
customExcerpt: "Every card payment needs a gateway and a processor. Here’s what each one does, and when you need to choose them separately."
metaTitle: "Payment gateway vs payment processor: what’s the difference?"
metaDescription: "A payment gateway collects card details; a processor moves the money. Learn the difference, what each costs, and when your business needs both."
featureImage: "https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/10/payment-gateway-vs-processor.jpg"
status: published
publishedAt: "2026-10-15T09:23:47.000Z"
updatedAt: "2026-10-15T09:23:47.000Z"
createdAt: "2026-10-13T01:10:19.453Z"
tags:
  - { name: Payments, slug: payments }
  - { name: "#Payment Processing", slug: hash-paymentprocessing }
authors:
  - { name: Keisha Singleton, slug: keisha }
  - { name: Colin McDermott, slug: colin }
---

# Payment gateway vs payment processor: what’s the difference, and do you need both?

On June 23, 2026, England played Ghana in the World Cup, and pubs across the UK were packed. 

World Cup matches are *huge* moneymakers for pubs. According to market researchers the Oxford Partnership, pubs sold 77% more draft beer and cider that day than on a typical Tuesday.

And it could have been more. But, partway through the match, card payments stopped working.

So what happened?

A power disruption hit Worldpay, one of the biggest [payment processors](https://whop.com/blog/payment-processors/) in the world. Pubs had to switch to cash only, with fans queuing at ATMs during one of the best trading nights of the summer.

Worldpay pushed the blame elsewhere, saying *"A third-party power disruption is causing intermittent transaction authorization issues and tokenisation requests errors on some Worldpay platforms."*

Put simply, two different jobs in the payment chain had broken – one handled by the payment processor, and one usually handled by the [payment gateway](https://whop.com/blog/what-is-a-payment-api-or-payment-gateway/).

If your business takes card payments, it needs both jobs done, but you’ll only have to choose them separately if you hold your own merchant account. Here’s what each one does, how they work together, and when you need to choose them separately.

## Payment gateway vs payment processor at a glance (the TL;DR)

A payment gateway is the part of a card payment that your customer sees. It collects their details at checkout, encrypts them, and sends them on.

A payment processor works behind the scenes, carrying the authorization request through the card networks to the customer's bank, then moving the money to your account.

<table>
  <thead>
    <tr>
      <th></th>
      <th>Payment gateway</th>
      <th>Payment processor</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><strong>Role</strong></td>
      <td>Captures, encrypts and sends payment details, then returns the approval or decline to your checkout</td>
      <td>Sends the authorization request through the card networks to the customer’s bank, then handles settlement</td>
    </tr>
    <tr>
      <td><strong>Where it sits</strong></td>
      <td>At checkout: your online payment form, or the card terminal in person</td>
      <td>Behind the scenes, between your business and the banks</td>
    </tr>
    <tr>
      <td><strong>What it touches</strong></td>
      <td>Card details as they’re entered, plus tokens that replace them</td>
      <td>Authorization messages, transaction data and the movement of funds</td>
    </tr>
    <tr>
      <td><strong>Fraud and disputes</strong></td>
      <td>Collects security data like the CVV and billing address, and can screen payments with rules</td>
      <td>Passes disputes between the card networks, the acquiring bank and you; many also offer fraud screening</td>
    </tr>
    <tr>
      <td><strong>Typical fees</strong></td>
      <td>If standalone: a monthly fee and/or a small per-transaction fee</td>
      <td>A percentage plus a fixed fee per transaction, or interchange-plus pricing</td>
    </tr>
    <tr>
      <td><strong>Examples</strong></td>
      <td>Authorize.net, NMI</td>
      <td>Fiserv, Worldpay (Global Payments), Elavon</td>
    </tr>
      <td><strong></strong></td>
    </tr>
  </tbody>
</table>

In a hurry? That's the quick need-to-know version. 

For a deeper look at how gateways and processors work, how a payment travels from checkout to settlement, and how to decide which setup is right for your business, keep reading.

> **Quick definitions**
>
> - **Acquirer (acquiring bank):** a bank that holds your merchant account and receives card payments on your behalf.
> - **Card networks:** Visa, Mastercard and the other networks that connect your side of the payment to the customer’s bank, and set the rules both sides follow.
> - **PSP (payment service provider):** an umbrella term for any company that lets you accept payments. Many bundle the gateway and processor into one product.
> - [Payment orchestration](https://whop.com/blog/payment-orchestration/)**:** software that routes payments across multiple providers, for example to improve approval rates or keep payments running if one provider goes down. During the Worldpay outage, businesses set up to route card payments through multiple providers could have kept taking cards while the pub down the road went cash-only.



## What is a payment gateway?

A payment gateway takes a customer's card details at checkout, encrypts them and sends them to the processor, then tells your checkout whether the payment was approved.

Online, a payment gateway is your payment form. It's where customers enter their card details, or choose an alternative payment option like [Buy Now, Pay Later](https://whop.com/blog/buy-now-pay-later-on-whop/).

![](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/10/image-1-1.png)

Gateways come in two main types: hosted and integrated. With a hosted gateway, customers enter their details on the provider's page, so card data *never* touches your servers and most PCI work stays off your plate. 

With an integrated ([API](https://whop.com/blog/best-payment-apis/)) gateway, you build checkout into your own site. You get more control, but also more responsibility. 

![checkout.com payment api](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/10/checkout.com-payment-api.png)
*<i><em class="italic" style="white-space: pre-wrap;">Checkout.com's payment API</em></i>*

How much more responsibility? It comes down to which PCI form you have to fill out. A hosted checkout usually means filling out the shortest self-assessment questionnaire, SAQ A. 

If your own site controls the payment page, you’ll likely move to SAQ A-EP, which comes with far more requirements. 

And if card numbers pass through or are stored on your own servers, you’re into SAQ D, the longest of them all.

Just starting out? Go hosted. It’s faster to set up and keeps most of the security work off your plate. You can always move to an integrated checkout once you need more control over the experience.

Either way, most payment gateways use tokenization – which means swapping the card number for a token so you can charge returning customers without storing their details. 

> **Card tokenization is more important than you may think:**
> According to Visa Acceptance, online payments in Europe made with Visa network tokens see a 6% increase in approval rates and almost 50% less fraud than payments made with the card number itself, so when you’re comparing providers, ask whether they support network tokens.

### How does a payment gateway stop fraud?

We've mentioned that gateways and processors are both involved in [fraud screening](https://whop.com/blog/ecommerce-fraud-prevention-tools/), but it all starts with the gateway. As your first line of defense against fraud, the gateway collects the CVV and billing address, runs your fraud rules (like blocking repeated attempts or high-risk countries) and can trigger [3D Secure](https://whop.com/blog/whop-3d-secure/) checks.

### Do you need a standalone payment gateway?

Most businesses get a gateway bundled in with a processor and a merchant account on one provider (more on merchant accounts later). But some gateways are sold on their own, like Authorize.net and NMI. 

A standalone gateway can't take payment by itself. You must connect it to a processor and a merchant account (which is why at sign-up you're asked which processor you use). 

So why bother? Flexibility. You get to keep the same checkout even if you switch processors or negotiate a better rate, so you're not locked in.

But before you count on that flexibility, ask yourself one question: can you take your customers’ saved cards with you if you leave? If your stored cards are locked in one provider’s vault, switching means asking every customer to re-enter their details. 

Stripe, for example, will transfer your customers’ card data to another PCI-compliant processor on request. Check that any gateway you’re considering does the same.

## What is a payment processor?

A payment processor is a company or service that acts as the middleman in a transaction. It authorizes, clears, and settles card payments between buyer, seller, and bank or financial institution.

![Video thumbnail](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/Gif-Ohana-2-3_thumb.jpg)
[Watch video](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/Gif-Ohana-2-3.mp4)

It doesn’t work alone. It connects the card networks with your acquiring bank, getting you an answer in seconds, then moving the money over the following days. 

Processing is technically split into front-end (connecting to card networks) and back-end (settling funds), but most businesses never deal with the split directly. If you *do* want to know more about the inner workings of payment processing, read [what is a payment processor](https://whop.com/blog/what-is-a-payment-processor/).

### Should you care about who processes your payments?

Yes. Your processor takes the lion's share of your transaction fees and decides how quickly you get paid. And, **when a processor goes down, your sales go down**.

And the disruption doesn’t always end when service comes back. After the World Cup outage, Worldpay and its owner Global Payments told American Banker that some merchants on its Worldpay Total platform would receive their funds a day later than expected.

Don’t count on compensation for your losses, either. Most merchant agreements limit what processors owe for outages, which is why having a backup matters.

Maddie Cohen, on the Growth team at Whop, speaks about what happens when your payment processor goes dark.

> "A lot can happen in the world of payment processing. If anything does happen to one of your PSPs or payout partners, you want to make sure you have something to fall back on." 
> 
> *— Maddie Cohen*

### What are some popular payment processors?

Some of the biggest processors are Fiserv, Global Payments (which completed its acquisition of Worldpay in January 2026) and Elavon. Many of them also act as acquirers (through sponsor banks), so the company processing your payments and the one holding your merchant account are often the same.

But instead of dealing with payment processors directly, many businesses use payment providers like [Stripe](https://whop.com/blog/what-is-stripe/), [Square](https://whop.com/blog/square-payments/) and [PayPal](https://whop.com/blog/paypal-for-business/), which handle processing and the gateway in one product, often working with processors like these behind the scenes.

## The difference between a payment processor and a payment gateway

The payment gateway is the messenger; the payment processor is the one that gets things done.

Think of it this way: **the payment gateway is a waiter, and the payment processor is the chef.**

When a guest wants to order a meal, they order with the waiter (gateway). The waiter takes down the order in a shorthand that only the chef can read (encrypted card details) and relays it to the chef (processor).

The chef doesn't have every single ingredient on hand, so they call the supplier (customer's bank) to check if they're in stock (funds or credit). If the supplier says yes, they make the meal (authorize the payment) and hand it to the waiter to bring it out. If not, the waiter goes back to the guest with a message that the meal is unavailable (declined). 

And at the end of the night, the takings still need to get to the restaurant owner’s bank account. That’s settlement, and it’s the processor’s job too.

## How does a card payment move through the gateway and processor?

Let's go back to that unfortunate Worldpay World Cup example. Worldpay blamed '*transaction authorization issues and tokenisation requests errors*' – two separate parts of the payment flow.

To see where things went wrong – and where they could go wrong for you – let's follow a payment from tap to bank account.

### 1. Your customer pays

Online, your customer enters their card number, expiration date and CVV, plus their name and billing address.

In person, that same customer either [taps to pay](https://whop.com/blog/tap-to-pay-guide/) or inserts a card in a terminal. Depending on the amount and the card, they might enter a PIN, sign, or (for small contactless payments) do nothing at all. 

![Video thumbnail](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/07/gif_tapping_1920x1080--1-_thumb.jpg)
[Watch video](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/07/gif_tapping_1920x1080--1-.mp4)


Either way, the card terminal does the gateway’s job, and the rest of the journey is identical. That’s why one provider can usually handle both your online and in-person sales.

### 2. The gateway keeps customer details secure

The gateway encrypts the customer's card details, swaps the card number for a token, and passes everything to the processor. **This is the step where Worldpay's tokenization errors would have hit**: if the details can't be secured, the payment stops here.

### 3. The processor asks for permission

The processor sends an authorization request through the card network (Visa, Mastercard and so on) to the customer's bank.

### 4. The bank makes a decision

The customer's bank checks the CVV and billing address, confirms there is enough money or credit, runs its own fraud checks, and approves or declines. If approved, it places a hold on the funds – but nothing has actually moved yet.

### 5. Your customer gets an answer

The bank's decision returns through the card network, to the processor, to the gateway, and to your checkout. Your customer sees a 'payment successful' or 'payment declined'.

All of the steps up until now take just a couple of seconds. Visa *alone* processed 257.5 billion transactions in its 2025 financial year, roughly 700 million a day. That’s an average of more than 8,000 every second.

**Steps 3-5 are where Worldpay's authorization issues came into play**, and once those requests got stuck in the flow, the payments could not be processed.

### 6. The money moves

Later – usually at the end of the day – your approved transactions are sent off in a batch for clearing. The customer’s bank releases the funds, they travel through the card network to your acquiring bank, fees are taken out, and the rest lands in your account. That’s settlement.

Running a marketplace? There's one more step after this: deciding when your sellers get their share. Read our [marketplace payouts guide](https://whop.com/blog/marketplace-payouts/) for more information.

### 7. Sometimes, money moves back again

If a customer disputes a charge weeks later, the whole journey runs backward. It goes from their bank through the card network to your processor and acquiring bank, and the money can be pulled *back* out of your account while the dispute is resolved.

Whether money is coming in or being pulled back out, it *always* moves through a merchant account at an acquiring bank. So who holds that account? 

That depends on how you got your gateway and processor.

## How do you get a gateway and processor? Merchant accounts, payment facilitators and PSPs explained

For card payments, every business gets its gateway and processor through one of four routes, and which route you’re on comes down to one question: who holds that merchant account?

This is an important choice that ultimately determines how fast you can start selling, the size of your fees, and how much control you have when something goes wrong.

### Option 1: Get your own merchant account, then add a gateway

This is the old-school route. You apply for a merchant account with a bank, acquirer, or reseller, go through underwriting, then connect a gateway (either one that your provider bundles or a standalone one).

What does this look like? In the US, that might mean an acquirer like Fiserv, Worldpay or Elavon, using either the gateway they offer or a standalone one like Authorize.net or NMI. Outside the US, banks offer the same thing; in Australia, for example, it’s called a merchant facility. 

So why bother with all this paperwork? Leverage. With your own account, you can negotiate your rates (often on interchange-plus pricing), and when you're processing at a high volume, that small fraction of a percent can add up to a large chunk of revenue. 

But the price for this leverage is more paperwork, a slower setup, and, if you use a standalone gateway, a second set of fees to pay on top of processing. Plus, more PCI responsibility.

#### Best for:

Established, high-volume businesses, enterprises routing payments across multiple processors, and high-risk industries that need a specialist processor.

### Option 2: Use a payment facilitator

This is the shortcut route that most founders take, often without even realizing it. 

With this option, a [payment facilitator](https://whop.com/blog/what-is-a-payfac/) holds one master merchant account and signs you up underneath it as a sub-merchant. This means that you don't have to wait for underwriting, and can usually take your first payment the same day, with a payment processor and gateway bundled in. 

![payfac diagram](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/images/2026/10/payfac.png)

Some of the most common examples of this are Stripe, Square, and PayPal.

**The catch here is that you're living in someone else's house**. The facilitator carries the risk for everyone on its account, so if your sales suddenly spike or look strange, the facilitator can hold or freeze your funds while it investigates. You'll also pay a flat rate, with little room to negotiate.

Derek Wilmer, Head of Ecommerce at Whop, found that out the hard way. Back in 2019 he was running his own ecommerce brand when [PayPal froze $264,000 of his money](https://whop.com/blog/gen-z-financial-layer/) without warning.

> "That moment showed me how little power small businesses actually have. One processor makes a decision and your entire livelihood is on hold – you don’t get a say, and you don’t get a human to talk to."

#### Best for:

Most new and small businesses selling online.

(**PS:** if you’ve seen 'PSP' on a pricing page, it’s not a fifth route. It’s the umbrella term for any company that lets you accept payments, and most of the ones small businesses use are payment facilitators.)

### Option 3: Use a platform with payments built in

Here, payments are not a separate decision to make. They come built into the platform you're running your business on, with payment providers working behind the scenes.

[Shopify Payments](https://whop.com/blog/shopify-payments/) and website builders (like [Whop Blueprints](https://whop.com/blog/whop-blueprints/)) with built-in checkout work this way. You never sign up with a gateway or processor directly, just the platform itself.

When I set up Squishy Swap, a marketplace I’m building on Whop, I was never asked for a merchant account application. Setup asked for identity verification and payout details, and that was it. I could start accepting payments in minutes.

![Video thumbnail](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/10/squish_thumb.jpg)
[Watch video](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/10/squish.mp4)

For founders, the appeal here is fewer moving parts. Payments, storefront, and payouts all live in one place.

Building a platform or marketplace yourself? The same idea applies one level up: a [marketplace payments provider](https://whop.com/blog/marketplace-payment-platform/) handles the gateway and processor for every seller on your platform (more on that below). 

#### Best for:

Founders who want to run the whole business in one place, including marketplaces.

### Option 4: Use a merchant of record

This final route takes the most responsibility off your hands. A merchant of record (MoR) is legally the seller in every transaction, so it owns the whole payment stack and usually handles tax, refunds, and chargebacks too. If you've ever had to work out sales tax or VAT across multiple countries, you can see the appeal of an MoR.

Merchant of record providers include Paddle and FastSpring.

So what's the downside? That varies by provider. Some MoRs charge more than a payment facilitator to cover the tax and compliance work. Others limit how much you can customize checkout. Compare MoRs before choosing one.

#### Best for:

Businesses selling internationally that want tax handled for them.

## Do you need both a payment gateway and a payment processor? It all depends on how you sell

For card payments, yes. Every card payment needs both a gateway and a processor to go through – but that doesn't mean that you have to deal with two separate providers. You'll only have to choose them as two separate providers if you set up your own merchant account (Option 1). 

But if you use a payment facilitator, a platform with payments built in, or a merchant of record, the gateway and processor come bundled together.

### What about payments that aren't cards?

Accepting payments via bank debit, wallet balance, or BNPL? The gateway still works the same way whether a customer uses card or Apple Pay. What changes is where the payment goes next. 

Instead of a card processor and the card networks, the payment travels on a different system.

- **Bank debits** run on bank networks instead of card networks (ACH in the US, or direct debit elsewhere).
- **Wallet balance payments** (PayPal, Venmo) are processed by the wallet provider itself.
- **Apple Pay and Google Pay** are the exception here: they're card payments underneath, so they follow the same card flow covered earlier.
- With **BNPL**, your gateway hands the payment to the BNPL provider (Afterpay, Klarna, Affirm) instead of a card processor. The provider decides whether to approve your customer, then pays you upfront, minus its own fee.

> **Offering more than just cards can make a big difference to your sales.**
> In Baymard’s 2026 survey, 9% of shoppers who abandoned checkout said it was because the site didn’t offer enough payment methods.

### When don't you need a processor and a gateway?

Is there ever a time you don’t need both? Only if you don’t take cards at all. If you only accept bank transfers, card processing doesn’t come into it.

Selling in person is a little different. You still *need* both, but your card terminal has the gateway built in. The terminal and the processor usually come from the same provider, too.

### What about platforms and enterprises?

If you're running a platform or a marketplace you still need both a gateway and a processor, but you need them for *every* seller, not just yourself. And a gateway and processor alone aren’t enough. You also need a way to verify your sellers, split each payment between you and them, and pay them out.

That’s a *lot* to build on top of your own gateway and processor, and it also means handling your sellers’ money, which can bring licensing requirements like money transmitter rules in the US. 

So most platforms don’t build it themselves. They use a payments provider built for marketplaces, which bundles the gateway and processor with seller verification, split payments and payouts.

Whichever provider you choose, check who the merchant of record is. That decides who handles refunds, disputes and tax: you, or your provider.

**Enterprises are a different story.** They’re the businesses most likely to choose their gateway and processor separately, and often more than one processor.

Why more than one processor? Well, remember the Worldpay outage? Routing payments across several processors through an orchestration layer means one outage doesn’t stop your sales. 

It can also push your approval rates up, since each payment can be sent wherever it’s most likely to go through.

## Payment gateway vs payment processor fees

Accepting card payments isn't cheap – US merchants paid a record $198.25 billion in card processing fees in 2025, according to the Nilson Report. But how much of that comes out of *your* revenue depends on which route you take, and how your provider charges you.

Here are the three main ways you will be billed for processing and gateway fees:

### Bundled flat-rate pricing

Using a payment facilitator? You'll pay one rate that covers both the gateway and processing fee. Stripe's standard rate for domestic cards, for example, is 2.9% + 30¢ per successful transaction, with no monthly fees. 

That one rate covers everything: the gateway, the processing, the card network’s fees and the provider’s margin. The 2.9% and the 30¢ aren’t separate gateway and processing charges; they’re one blended price.

It's simple, and you always know what a sale will cost you. But you pay the same rate on every card, whether it's a basic debit card that's cheap to process or a premium rewards card that costs more.

### Separate gateway and processing fees

Using your own merchant account and a standalone gateway? That's two providers, so you'll get two bills. Authorize.net’s gateway-only plan, for example, costs $25 a month, plus $0.10 per transaction and a $0.10 daily batch fee for sending each day’s payments off to be settled. And that’s before your processor takes its cut.

What about the processor fee? There's no one standard fee to reference here, but based on the Nilson Report’s figures ($198.25 billion in fees on $12.5 trillion of card spending), US merchants paid around 1.6% of their card sales in fees in 2025, across all card types. And that grows quickly if most of your customers pay by credit card.

### Interchange-plus pricing

With interchange-plus you see exactly what each payment costs. You pay for three things: the interchange fee (set by the card network and paid to the customer's bank), the card network's own fees, and your processor's markup.

Adyen, for example, publishes its pricing this way: one fixed processing fee per transaction, plus interchange, plus a markup on Visa and Mastercard payments.

### When does your own merchant account start to pay off?

Which works out cheaper: one flat rate, or your own merchant account with interchange-plus? 

Let's take a look with a worked example.

Say you're selling $50,000 a month at an average of $60 per order. That works out to be about 833 transactions. To keep things simple (and give Option 1 – your own merchant account and separate gateway – a tough test), let’s assume every single customer pays online with a standard Visa Traditional credit card.

On Stripe's flat rate, you'd pay 2.9% + 30¢ per transaction, which comes to **about $1,700 a month**.

With your own merchant account and a standalone gateway, you’d pay:

- **Visa’s interchange fee** of 2.05% + $0.10 (its rate for Visa Traditional credit cards used online, in the card-not-present 'Product 1' category, as of April 2026): *about $1,108*
- **Your processor’s markup**, using Adyen’s published 0.60% + $0.13: *about $408*
- **Authorize.net’s gateway fees** of $25 a month, $0.10 per transaction and a $0.10 daily batch fee: *about $111*

That’s **around $1,628 a month**, plus Visa’s own network fees on top. So all that extra setup saves you only $70 per month, and Visa's network fees would eat most of that. 

Your own merchant account starts to pay off once you’re processing at high volume. On its own, volume doesn’t save you much, because the gap per transaction is only a few cents. But what it does give you is leverage to negotiate a lower markup than the published rate, and processors compete hard for big merchants. 

It also pays off sooner if many of your customers pay by debit, because debit interchange is a fraction of what credit costs. Until then, a flat rate costs about the same, with far less hassle.

### Selling low-cost products? Watch your fixed fees

Most payment fees have two parts: a percentage of the sale, and a fixed fee (a flat amount like 30¢) charged on every transaction.

That fixed fee hits the smallest orders hardest. On a $100 sale, 30¢ is just 0.3% of the sale. But on a $5 sale, it’s 6%, and once you add the percentage on top, you could be losing almost 9% of every order to fees. Ouch.

I had to plan around this for Squishy Swap, my online marketplace, where most sales will be small. So I let buyers bundle multiple items into one order. One order means one payment, and one payment means the fixed fee is only charged once.

For a full breakdown of what you’ll pay and how to bring it down, read our guide to [payment processing fees](https://whop.com/blog/payment-processing-fees/).

## How to choose the right payment setup for your business

Now you know what a gateway does, what a processor does, how a payment gets to your bank account, and the four routes you can go down for getting both a gateway and processor.

But which setup is right for you?

Start by finding the row in this table that sounds most like your business.

### Decision matrix

<table><thead><tr><th scope="col">Situation</th><th scope="col">Route</th><th scope="col">Choose separately?</th><th scope="col">Fund-hold risk</th><th scope="col">Tax handling</th></tr></thead><tbody><tr><td>New or small business selling online</td><td>Option 2: payment facilitator</td><td>No</td><td>Higher</td><td>Usually yours</td></tr><tr><td>Building a marketplace or platform</td><td>Option 3: platform with payments built in, or a marketplace payments provider</td><td>No</td><td>Depends on the platform</td><td>Depends on the platform’s settings</td></tr><tr><td>Want tax and compliance handled, especially selling globally</td><td>Option 4: merchant of record</td><td>No</td><td>Depends on the provider</td><td>Handled or partly handled by the provider, depending on settings</td></tr><tr><td>High volume, wanting negotiated pricing</td><td>Option 1: own merchant account</td><td>Yes</td><td>Lower</td><td>Yours</td></tr><tr><td>Enterprise processing high volume across multiple markets</td><td>Option 1: own merchant accounts, with multiple processors through an orchestration layer</td><td>Yes</td><td>Lower</td><td>Yours</td></tr><tr><td>High-risk industry</td><td>Option 1: own merchant account with a specialist processor</td><td>Usually yes</td><td>Depends on the processor</td><td>Yours</td></tr><tr><td>In-store only</td><td>Terminal provider</td><td>No (the gateway is built into the terminal)</td><td>Depends on the provider</td><td>Usually yours</td></tr><tr><td>Bank transfers only</td><td>Bank payment provider</td><td>No card processor needed</td><td>Depends on the provider</td><td>Usually yours</td></tr></tbody></table>

If you landed in a ‘no’ row, the good news is you don’t need to source a gateway or processor at all. 

You just need the right provider.

## Accept payments with Whop

![Video thumbnail](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/wpn_thumb.jpg)
[Watch video](https://storage.ghost.io/c/12/7b/127b828b-bdc2-4972-9cf2-de857df9c324/content/media/2026/03/wpn.mp4)

Whop is the end-to-end platform for building a business, and taking payments is a huge part of that. You don’t need to source a gateway, apply for a merchant account, or connect a processor – Whop works with payment providers behind the scenes, so you can start selling without building the infrastructure yourself.

When you accept payments with Whop, you can:

- Take payments online with a hosted checkout, or embed checkout into your own site or app.
- Accept payments in person with tap to pay on iPhone.
- Build a marketplace or platform, with seller verification, split payments, and payouts built in.

Whop goes well beyond payments. You can launch fast with a Whop Blueprint, run your business programmatically with the Whop CLI, grow with Whop Ads, and use economic intelligence to make smarter decisions about your business. 

Whatever you’re selling, Whop gives you everything you need to run your business – payments included.

**[Whop](https://whop.com/network/)**

---

## FAQs

### Is Stripe a payment gateway or a processor?

Both. Stripe bundles the gateway and processing into one product, so you get a checkout, authorization, and settlement from a single provider.

### Is PayPal a payment gateway or a processor?

Both. Like Stripe, PayPal works as a payment facilitator for most businesses, bundling the gateway and processing so you can start taking payments without a merchant account.

### Can a gateway work without a processor?

Not for card payments. A payment gateway collects and secures payment details, but it can't get a payment approved or move the money by itself – that's the processor's role.

### What’s the difference between a processor and an acquiring bank?

The acquiring bank holds your merchant account, receives your card payments, and takes on the risk of you as a merchant. The processor handles the technical work of sending authorization requests through the card networks and moving the money during settlement.

### What’s the difference between a payment gateway and a merchant account?

A payment gateway is the technology that collects and secures your customer's payment details at checkout. A merchant account is where card payments land at an acquiring bank before reaching your business bank account. You always need a gateway, but you don’t always need your own merchant account. With a payment facilitator or platform, you use theirs.