Payment Gateway vs Payment Processor — What's the Difference? (Plain English)

The terms "payment gateway" and "payment processor" are used interchangeably so often that many merchants assume they're the same thing. They're not — and understanding the difference between a payment gateway and a payment processor is important for making informed decisions about your payment infrastructure, negotiating fees, and troubleshooting issues when transactions fail.

This guide clearly defines each component, explains how they work together in a transaction, discusses when you need one or both, and helps you decide between using separate providers or an all-in-one solution.

What Is a Payment Processor?

A payment processor (also called a credit card processor or merchant acquirer) is the company that handles the actual movement of funds between the cardholder's bank and your merchant account. When a customer pays with a credit card, the payment processor is the engine that makes the money move.

What a Payment Processor Does

The payment processor's role includes:

Routing transactions — Sends the transaction data to the appropriate card network (Visa, Mastercard, etc.) and then to the issuing bank for authorization
Obtaining authorization — Receives the approval or decline from the issuing bank and relays it back
Settlement — At the end of each business day (when you "batch out"), the processor initiates the actual transfer of funds from the issuing bank to your merchant account
Funding — Deposits the transaction proceeds (minus fees) into your business bank account, typically within 1-2 business days
Chargeback management — Routes chargeback notifications and representment documents between you and the issuing bank
Compliance — Ensures transactions comply with card network rules and regulations

Types of Payment Processors

Traditional processors (merchant acquirers): These companies provide you with a dedicated merchant account and process transactions on your behalf. Examples include:

Fiserv (formerly First Data)
Global Payments (formerly TSYS)
Worldpay
Heartland
Elavon

Payment facilitators (PayFacs): These companies aggregate many merchants under their own master merchant account, simplifying signup but giving you less control. Examples include:

Square
Stripe
PayPal
Toast

The distinction matters: traditional processors give you your own merchant ID (MID) and potentially better rates, while PayFacs offer faster setup and simpler onboarding but may hold funds or terminate accounts more readily.

What Is a Payment Gateway?

A payment gateway is the technology that securely captures and transmits payment card data from the point of sale (whether online or in-person) to the payment processor. Think of the payment gateway as the digital equivalent of the physical credit card terminal in a store.

What a Payment Gateway Does

The payment gateway's role includes:

Data capture — Securely collects the cardholder's card number, expiration date, CVV, and billing information
Encryption — Encrypts the sensitive card data so it can be safely transmitted over the internet
Data transmission — Sends the encrypted transaction data to the payment processor
Response relay — Receives the authorization response (approved/declined) from the processor and passes it back to the merchant's website or POS system
Fraud screening — Many gateways include basic fraud detection tools (AVS, CVV verification, velocity checks)
Tokenization — Replaces sensitive card data with a non-sensitive token for secure storage and recurring billing

When Do You Need a Payment Gateway?

You need a payment gateway whenever card data needs to travel over the internet to reach the processor:

E-commerce websites — Every online store needs a gateway to accept card payments
Mobile apps — In-app payments require a gateway
MOTO (mail order/telephone order) — Virtual terminals (which include a gateway) are used to key in card information
Recurring billing — Gateways store tokenized card data for automated future charges

You generally don't need a separate gateway for:

Card-present retail — Physical card terminals connect directly to the processor's network. The terminal itself handles the data capture and encryption functions.
Mobile card readers — Devices like Square Reader or Clover Go have the gateway functionality built into the hardware and app

How a Payment Gateway and Payment Processor Work Together

Let's trace a complete online transaction to see exactly where the gateway and processor each play their role.

Step-by-Step: Online Credit Card Transaction

Step 1: Customer enters card information. The customer fills in their card details on your checkout page. The payment gateway is responsible for the form that collects this data (either a hosted payment page or embedded form elements).

Step 2: Gateway encrypts and transmits data. The payment gateway encrypts the card data using SSL/TLS and transmits it securely to the payment processor. This happens in milliseconds.

Step 3: Processor routes to card network. The payment processor receives the transaction data and routes it to the appropriate card network — Visa, Mastercard, American Express, or Discover — based on the card number.

Step 4: Card network routes to issuing bank. The card network forwards the authorization request to the issuing bank (the bank that issued the customer's credit card).

Step 5: Issuing bank approves or declines. The issuing bank checks the account for available credit, fraud indicators, and any restrictions. It sends an approval or decline response back through the card network.

Step 6: Processor relays response to gateway. The payment processor receives the authorization response from the card network and passes it to the payment gateway.

Step 7: Gateway displays result to customer. The payment gateway receives the response and displays it on your website — "Payment Approved" or "Payment Declined."

Step 8: Settlement and funding. At the end of the day, the payment processor batches all approved transactions and initiates settlement. The issuing bank transfers funds through the card network to the processor, which deposits the money (minus fees) into your bank account.

The Full Transaction Flow

Customer → Payment Gateway → Payment Processor → Card Network → Issuing Bank
                                                                      ↓
Customer ← Payment Gateway ← Payment Processor ← Card Network ← Authorization

The entire authorization process — steps 1 through 7 — typically takes 1 to 3 seconds.

Key Differences Between Payment Gateways and Payment Processors

| Aspect | Payment Gateway | Payment Processor | |--------|----------------|-------------------| | Primary function | Captures and transmits card data securely | Routes transactions and moves money | | Analogy | The card reader at the counter | The bank's back-office system | | Who interacts with it | Customer and merchant's website | Card networks and banks | | Security role | Encrypts data, tokenizes cards | Ensures compliance with network rules | | Fee structure | Monthly fee + per-transaction fee | Percentage of transaction + per-transaction fee | | PCI scope | Heavily impacts your PCI scope | Less direct PCI impact for merchants | | Needed for e-commerce | Always | Always | | Needed for in-person | Rarely (built into terminals) | Always | | Examples (standalone) | Authorize.net, NMI, USAePay | Fiserv, Global Payments, Worldpay | | Examples (bundled) | Stripe, Square, PayPal, Adyen | Stripe, Square, PayPal, Adyen |

All-in-One vs. Separate Gateway and Processor

One of the most important decisions in setting up your payment infrastructure is whether to use a single provider that bundles both gateway and processing, or to use separate specialized providers.

All-in-One Providers

Companies like Stripe, Square, PayPal, and Adyen provide both the payment gateway and payment processing in a single integrated service. You sign up once, integrate once, and deal with one company for everything.

Advantages of all-in-one:

Simplicity. One account, one integration, one support contact, one statement. Setup is dramatically easier — Stripe takes minutes, while a traditional gateway + processor setup can take days to weeks.
Cohesive experience. Since the gateway and processor are built by the same company, they work seamlessly together. Features like tokenization, recurring billing, and fraud detection are tightly integrated.
Modern APIs and documentation. All-in-one providers (especially Stripe) tend to offer superior developer documentation, SDKs, and API design compared to legacy gateway/processor combinations.
Faster updates. New features (like Apple Pay support, 3D Secure 2.0, or local payment methods) roll out faster when one company controls both the gateway and processor.

Disadvantages of all-in-one:

Less pricing flexibility. All-in-one providers typically offer flat-rate pricing (2.90% + $0.30, for example) which is non-negotiable at lower volumes. A separate gateway + processor on interchange-plus pricing may be cheaper.
Vendor lock-in. Your tokenized card data (vault) is tied to the provider. Switching from Stripe means re-collecting card information from all your recurring billing customers, unless you use portable network tokens.
Account risk. PayFacs like Stripe and Square can hold funds or terminate accounts with limited recourse, since you don't have your own merchant account.

Separate Gateway and Processor

Using a separate gateway (like Authorize.net or NMI) paired with a separate processor (like a traditional merchant account through Fiserv or Global Payments) gives you more control but adds complexity.

Advantages of separate providers:

Better pricing at volume. With a dedicated merchant account and interchange-plus pricing, you'll pay less per transaction than flat-rate all-in-one providers. The savings become meaningful above $20,000-$30,000/month.
Processor portability. If you want to switch processors (for better rates, for example), you can keep the same gateway. Your integration doesn't change — only the backend processor does. This is a powerful negotiation advantage.
Account stability. A dedicated merchant account with a traditional processor provides more stability than a PayFac sub-merchant account. Holds and terminations are far less common.
Customization. You can choose the best gateway for your technical needs and the best processor for your pricing needs independently.

Disadvantages of separate providers:

Complexity. Two accounts to manage, two support contacts, two contracts, and potentially two sets of fees (gateway monthly fee + processor fees).
Integration overhead. Setting up and maintaining the integration between gateway and processor requires more technical work.
Slower innovation. Legacy gateways and processors often lag behind all-in-one providers in adopting new payment methods and technologies.

Decision Framework

| Scenario | Recommendation | |----------|---------------| | Just starting out, <$10K/month | All-in-one (Stripe or Square) | | E-commerce, $10K-$50K/month | All-in-one (Stripe) or separate for savings | | E-commerce, $50K+/month | Evaluate separate gateway + processor for interchange-plus savings | | Subscription/SaaS business | All-in-one (Stripe) for integrated billing | | High-risk business | Separate; specialized high-risk processor + compatible gateway | | Multi-channel (online + in-person) | All-in-one if same provider covers both; otherwise, separate processors is common | | Enterprise / complex needs | Adyen (all-in-one at enterprise scale) or separate with custom integrations |

Common Examples of Gateways and Processors

Standalone Payment Gateways

These companies provide gateway services only — you pair them with a separate payment processor:

Authorize.net (owned by Visa)

One of the oldest and most widely used gateways
Monthly fee: $25/month + $0.10/transaction + $0.10 daily batch fee
Compatible with most traditional processors
Features: Recurring billing, fraud detection, virtual terminal
Ideal for: Businesses with existing merchant accounts wanting a reliable gateway

NMI (Network Merchants Inc.)

Popular with ISOs and resellers
White-label gateway used by many processor-branded gateways
Features: Tokenization, recurring billing, Level II/III data, mobile SDK
Pricing: Varies by reseller (typically $0.05-$0.15/transaction)

USAePay

Favored by businesses needing POS + e-commerce gateway in one
Features: Virtual terminal, recurring billing, mobile processing
Pricing: Typically $10-$20/month + per-transaction fees

Standalone Payment Processors

These companies provide processing (merchant accounts) but require a separate gateway for e-commerce:

Fiserv (First Data)

Largest payment processor in the US
Owns the Clover POS platform
Can pair with Authorize.net, NMI, or their own gateway
Pricing: Interchange-plus or tiered, negotiable

Global Payments (TSYS)

Major processor serving millions of merchants
Owns Heartland and TSYS
Pricing: Interchange-plus, competitive for mid-size merchants

Worldpay (FIS)

Global processor with strong international presence
Pricing: Interchange-plus, competitive for high-volume merchants

All-in-One Providers (Gateway + Processor)

| Provider | Gateway | Processor | Best For | |----------|---------|-----------|----------| | Stripe | Stripe.js / Elements / Checkout | Stripe (PayFac) | Developers, SaaS, e-commerce | | Square | Square Web Payments SDK | Square (PayFac) | Small businesses, omnichannel | | PayPal / Braintree | Braintree SDK / PayPal Checkout | PayPal / Braintree (PayFac) | PayPal-heavy customer bases | | Adyen | Adyen Web Drop-in / Components | Adyen (direct acquirer) | Enterprise, global commerce | | Helcim | Helcim.js | Helcim (PayFac) | SMBs wanting interchange-plus |

Switching Gateways or Processors: What to Know

Switching Processors (Keeping Same Gateway)

If you use a standalone gateway like Authorize.net, switching processors is relatively straightforward:

Set up the new merchant account with the new processor
Configure the gateway to route transactions through the new processor
Test the integration
Go live — transactions now flow through the new processor
Your tokenized cards in the gateway vault continue to work

Impact: Minimal. Customers don't notice anything. Your integration code doesn't change.

Switching Gateways (Keeping Same Processor)

Switching gateways is more involved because it affects your integration:

Implement the new gateway's SDK or API in your website/application
Migrate stored card tokens (this is the hard part — tokens are gateway-specific and generally can't be transferred)
Test thoroughly
Go live with the new gateway

Impact: Requires development work. Stored cards may need to be re-collected from customers.

Switching All-in-One Providers

Switching from one all-in-one provider to another (e.g., Stripe to Adyen) is the most involved migration:

Implement the new provider's entire integration (gateway + processing)
Migrate customer data and subscriptions
Handle stored card migration (network tokens can help here)
Run both systems in parallel during transition
Wind down the old provider

Impact: Significant development project. Plan for 2-8 weeks depending on complexity.

Portable Network Tokens

One emerging solution to the vault lock-in problem is network tokenization. Visa Token Service (VTS) and Mastercard Digital Enablement Service (MDES) create tokens at the network level that are portable across gateways and processors. If you request network tokens through your current provider, those tokens can theoretically be used with any provider that supports them, making future migrations easier.

Both Stripe and Adyen support network tokenization, and adoption is growing across the industry.

How Fees Break Down: Gateway vs. Processor

Understanding which fees come from the gateway and which come from the processor helps you identify where to negotiate.

| Fee | Charged By | Typical Amount | Negotiable? | |-----|-----------|----------------|-------------| | Interchange fee | Card networks (via processor) | 1.5-3.5% | No | | Assessment fee | Card networks (via processor) | 0.13-0.15% | No | | Processor markup | Processor | 0.10-0.50% + $0.05-$0.15 | Yes | | Gateway monthly fee | Gateway | $10-$25/month | Sometimes | | Gateway per-transaction fee | Gateway | $0.05-$0.15 | Sometimes | | Tokenization/vault fee | Gateway | Often included | N/A | | PCI compliance fee | Processor | $79-$120/year | Sometimes | | Chargeback fee | Processor | $15-$100 | Rarely | | Monthly statement fee | Processor | $5-$15 | Yes |

When you use an all-in-one provider, all of these fees are consolidated into a single rate (like Stripe's 2.90% + $0.30). This is simpler but makes it impossible to negotiate individual components.

Frequently Asked Questions

Can I use a payment gateway without a payment processor?

No. The gateway captures and transmits the data, but it doesn't move money. You always need a processor (or an all-in-one provider that includes processing) to actually settle transactions and deposit funds into your account.

Can I use a payment processor without a gateway?

For in-person, card-present transactions — yes. A physical card terminal connects directly to the processor's network without needing a separate gateway. For online transactions — no. You need a gateway (or all-in-one provider) to securely capture card data from your website.

Is Stripe a gateway or a processor?

Both. Stripe is an all-in-one provider that combines a payment gateway (Stripe.js, Elements, Checkout) with payment processing (Stripe is a registered payment facilitator that processes transactions through its banking partnerships). Customers don't need a separate gateway or merchant account.

Is PayPal a gateway or a processor?

Both, through different products. PayPal Checkout handles the gateway functions, and PayPal processes the transactions. Through their Braintree subsidiary, they offer a more traditional gateway + processing service that's popular with developers.

What about payment service providers (PSPs)?

"Payment service provider" is a broader term that can encompass gateways, processors, or both. In practice, PSP is often used as a synonym for all-in-one providers like Stripe, Adyen, and PayPal. The term doesn't have a rigid industry definition.

Do I need a payment gateway for a WordPress/WooCommerce site?

Yes. WooCommerce requires a payment gateway plugin to accept card payments. Popular options include WooCommerce Stripe (all-in-one), WooCommerce PayPal (all-in-one), or a plugin for your standalone gateway like Authorize.net. The gateway plugin handles the checkout form on your site and communicates with the processor.

Making Your Decision

For most businesses in 2026, an all-in-one provider is the right starting point. The simplicity, modern developer experience, and integrated features outweigh the modest pricing premium for businesses processing under $50,000 per month.

As your volume grows beyond that threshold, evaluate whether the savings from a separate gateway and processor on interchange-plus pricing justify the additional complexity. For a business processing $100,000/month, the difference between Stripe's flat 2.90% + $0.30 and a competitive interchange-plus setup could be $300-$800/month — meaningful enough to warrant the operational overhead of managing separate providers.

Regardless of which path you choose, understand which component is performing which function. When a transaction fails, knowing whether the issue is at the gateway level (data capture, encryption, transmission) or the processor level (authorization, routing, settlement) is the difference between diagnosing the problem in minutes versus days.