Payment Gateway vs Payment Processor: What's the Difference?

A payment gateway and a payment processor do two different jobs, and to take card payments online you generally need both. A payment gateway is the software at checkout that securely captures your customer's card details and passes them on. A payment processor is the service that authorizes the transaction and moves the money between the customer's bank and yours. The gateway carries the data; the processor moves the money. The reason they get blurred is that one provider often supplies both at once.

This article zooms in on one comparison: the payment gateway vs the payment processor. For the closely related pieces, see merchant acquirer vs payment processor (who holds your account and settles your funds) and merchant account vs payment gateway. For the whole map, see our merchant acquiring guide.

The gateway carries the data; the processor moves the money.

Payment gateway vs payment processor: the short answer

A payment gateway is the software at checkout that captures your customer's card details and securely transmits them for authorization. A payment processor is the service behind it that authorizes the transaction and moves the money between the customer's bank and yours. The gateway carries the data; the processor moves the money.

"Messenger vs mover" is a common mental model, not a strict legal definition. Many providers do both, which is why the terms get used interchangeably.

The pricing row is the practical tell. A gateway sold on its own is priced like software: Authorize.net's Gateway Only plan is $25 a month plus 10¢ per transaction and a 10¢ daily batch fee, for businesses that already have a merchant account elsewhere. A bundled plan folds both jobs into one rate — Authorize.net's own all-in-one option is 2.9% + 30¢ per transaction plus the same $25 monthly fee. When you see one percentage-plus-fixed rate, you are looking at gateway and processing together.

What a payment gateway is

A payment gateway is the technology that captures a customer's card details and securely transmits them so a payment can be processed. Online, it's the checkout page or the embedded payment form; in person, the card terminal plays the role.

• It captures and encrypts card data at the point of payment.
• It transmits that data to the payment processor and on through the payment chain, then relays back the approval or decline.
• It doesn't move the money itself. The gateway is the secure channel for the information; the funds are moved by the processor and settled into your account.

What a payment processor is

A payment processor is the service that takes the transaction from the gateway, gets it authorized, and moves the money. It acts as the intermediary between the customer's bank (the issuer) and your side of the transaction (your acquirer/acquiring bank).

• It requests authorization — it routes the transaction through the card networks to the issuer, which approves or declines.
• It moves the funds — for approved payments, it helps move money from the issuer toward your account through clearing and settlement.
• It works with the banks, not the checkout page. The processor is the engine behind the scenes; the gateway is the doorway at the front.

How a gateway and a processor work together

In a single online card payment the two roles hand off to each other six times:

1. Capture — at checkout, the payment gateway collects the customer's card details.
2. Encrypt and transmit — the gateway encrypts the data and sends it to the payment processor.
3. Route — the processor sends the request through the card network to the customer's bank (the issuer).
4. Decide — the issuer approves or declines and returns the answer to the processor.
5. Respond — the processor passes the result to the gateway, which shows "approved" or "declined" at checkout within seconds.
6. Settle — for approved payments, the processor and the acquiring side move the funds through clearing and settlement until your net amount lands in your account, typically days later.

The gateway is visible only at steps 1, 2 and 5; the processor does everything between the banks. Both are needed for a card payment to complete — but you may get them from one provider.

The gateway is visible only at steps 1, 2 and 5; approved payments move through clearing and settlement at step 6.

Do you need both?

Functionally, yes — a card payment needs a way to capture the card (a gateway) and a way to authorize it and move the money (a processor). What's optional is whether you assemble them separately.

• All-in-one provider. Many modern providers bundle the gateway and the processor (and often the acquiring/merchant-account side too) into one signup, so you never wire them together yourself.
• Separate components. You can also use a standalone gateway with a separate processor — more moving parts, but more flexibility to swap one without the other.

Neither is universally "right"; it's a trade-off between simplicity and flexibility (see "When the difference matters").

How to tell what you already have

Not sure whether you've got a gateway, a processor, or a bundled provider? A few checks usually tell you:

1. How did you sign up? One provider, one dashboard, one signup usually means a bundled gateway + processor (often a full PSP).
2. Who authorizes and settles? If the same provider that hosts your checkout also shows you authorizations and pays you out, it's acting as both gateway and processor.
3. Did you connect a separate gateway? If you plugged a checkout/gateway into a different processing account, you're running them as separate components.

If you can't tell from the marketing, ask: "Do you provide both the gateway and the processing, or do I bring my own for either?"

Stripe, PayPal, Authorize.net, Zelle: gateway, processor, or both?

The question people actually type is rarely abstract — it names a company. Here is where the familiar names sit, from each company's own materials:

Many other familiar names follow the same bundled pattern. For any provider not in the table, sixty seconds and three questions settle it:

Check all three answers: a gateway-only product can be one component of a separate gateway and processor setup.

• Who deposits money into your bank account? If it is the same company whose code runs your checkout, they are at minimum your gateway and your settlement provider.
• Did you sign a separate merchant account agreement? If yes, your "gateway" is likely gateway-only, and the processing lives with whoever issued that merchant account.
• When a payment fails, who do you call? If one support team can see both the checkout error and the settlement file, you are on a bundled provider; if they route you elsewhere, you have found the seam between your gateway and your processor.

Gateway vs processor vs payment aggregator

You will also see "payment aggregator" or payment facilitator — a provider that lets you process under its own master merchant account instead of opening one yourself. That is a statement about the merchant account, not about the gateway-versus-processor split: an aggregator still supplies (or plugs into) both a gateway and a processor. We explain the model in our payment facilitator guide.

Where the gateway and the processor sit — the bigger picture

The gateway and the processor are two pieces of a slightly larger set of roles. Two more come up constantly alongside them:

• The merchant acquirer (acquiring bank) — the partner that holds your merchant account, settles your funds, and carries the risk. The processor often works with an acquirer; they're not the same role. We break that down in merchant acquirer vs payment processor.
• The merchant account — the account your card funds land in before payout, and how it differs from the gateway. See merchant account vs payment gateway.

Put simply: the gateway carries the data, the processor authorizes and moves the money, the acquirer holds your account and settles your funds, and the merchant account is where those funds land. One provider may cover several of these at once — when it bundles them into one signup, that's a payment service provider (PSP). For the full map, see our merchant acquiring guide.

Payment processor vs payment network

One more label worth separating: the card networks. Visa and Mastercard are neither gateways nor processors — they run the rails between issuing and acquiring banks, set interchange, and standardize the message formats everyone else uses. A processor transmits transactions across those rails; the network owns them. When a provider says it "connects directly to the card networks", that is the layer it is talking about.

If you are choosing a gateway for cross-border sales rather than defining one, the international payment gateway comparison applies this split to nine providers' eligibility, pricing and settlement.

When the difference matters — and when you can ignore it

Often, it doesn't matter. If you use one all-in-one provider and you're happy with your checkout, your payouts and your pricing, you can treat "gateway" and "processor" as one box and move on.

It starts to matter when:

• You want to switch one part without the other — e.g., keep your checkout but change who processes and settles. That's only possible if you know which provider owns which role.
• You sell across borders. Where and how your transactions are processed and acquired can affect approval rates and cost, though the size of any effect depends on your markets, card mix and setup. The processing/acquiring relationship is the lever here, not the checkout page.
• You run multiple processors to route transactions by market or to add redundancy — which only makes sense once you separate the gateway from the processing layer.

The distinction shows up hardest on your invoice: gateway fees and processing fees are priced differently, and bundled providers fold both into one rate. Our payment gateway fees guide breaks down which fee belongs to which layer.

Where HaiPay fits

HaiPay provides both sides of this setup — the checkout tools that capture payments and the acquiring and cross-border processing behind them — for businesses that sell into multiple markets. If you're weighing a gateway vs a processor because you're setting up or expanding card payments internationally, it's worth understanding which part does what.

To see whether it fits your markets, explore HaiPay checkout and HaiPay acquiring, or talk to our team.

And once payments are flowing, the gateway-versus-processor split reappears in your bookkeeping — the settlement report your provider issues is the bridge between the two. Our payment gateway reconciliation guide shows how to match it to your orders and your bank.

The same split shows up in timing. Our payment settlement time guide separates the settlement schedule from the payout schedule and bank transit, and lists the tier we settle on in each market.

Sources

• Stripe — Payment processor vs. payment gateway: Page updated May 11, 2026. Accessed 2026-09-09.
• Wikipedia — Payment gateway: defines the gateway as the service that authorizes/transmits payment at checkout, the e-commerce equivalent of a POS terminal. Accessed 2026-08-12.
• Wikipedia — Payment processor: defines the processor as the company that handles transactions between the merchant's and customer's banks, including authorization and settlement. Accessed 2026-08-12.
• Fiserv Merchant Services — Payment Gateway vs. Payment Processor describes the gateway as the virtual equivalent of a POS terminal for card-not-present transactions, and the processor as transmitting payment data among the four parties. Accessed 2026-08-31.
• Zelle — What is Zelle?  Homepage self-description: "Send and receive money directly to and from your bank account". Accessed 2026-09-09.
• What is a payment gateway? — PayPal. States that both a processor and a gateway are needed for online sales and that PayPal provides both. July 17, 2026. Accessed 2026-09-09.
• Pricing — Authorize.net. Gateway Only plan ($25/month + 10¢ per transaction + 10¢ daily batch fee) and all-in-one plan ($25/month + 2.9% + 30¢, subject to eligibility). Accessed 2026-09-09.