The payment gateway captures the card and asks the question. The payment processor carries the question to the banks and brings the money back. One handles information, the other handles funds, and every card sale you take runs through both.
The distinction sounds academic until you are comparing two quotes, reading a statement with four different line items on it, or trying to work out who to call when a customer disputes an order that went out three weeks ago. Then it matters quite a lot, because the answer is a different company depending on the problem.
This post sorts out which component does what, whether you need to buy them separately, and how each one shows up in your costs. If you need the how-to instead (connecting a gateway to your checkout and getting the timing right), that is covered in the guide to payment gateway integration.
The Bottom Line
- The gateway is the digital equivalent of the card terminal: it collects card details, encrypts them, tokenizes them and transmits them. The processor moves the transaction and the funds between you, the customer’s bank and your bank.
- You need both. Every online transaction requires both, and they are interdependent (Stripe, retrieved September 2026). What you get to choose is whether you buy them as one account or two contracts.
- Neither of them owns your chargebacks. The acquiring bank carries legal responsibility for the funds and submits your case to the card network; the processor is the one that notifies you and gives you the dashboard to respond in (Chargeflow, retrieved September 2026).
- The fees are separate things. Gateway fees pay for the checkout technology; processing fees pay for moving money and carry interchange set by the card networks (IXOPAY, retrieved September 2026).
- If you sell online and deliver, the gateway is the part you will interact with daily, because holding and adjusting a charge between checkout and handoff is a gateway-side job.
Save 80% of delivery management time
We handle everything:
- Dedicated operations manager
- Real-time tracking dashboard
- Automated customer notifications
- Urgent issue resolution
The difference between a payment gateway and a payment processor
One is a data pipe, the other is a money pipe. Everything else follows from that.
| Payment gateway | Payment processor | |
|---|---|---|
| Primary job | Capture, encrypt and transmit card data | Move the transaction and the funds between banks |
| Physical analogy | The card terminal, in software | The armored truck and the clearing house |
| When it acts | At checkout, in the two seconds before approval | At approval, and again at settlement |
| What it touches | Information | Money |
| You deal with it when | Building or changing your checkout | Reconciling deposits, disputing a chargeback, renegotiating rates |
| Typical fee shape | Monthly platform fee plus small per-transaction fee | Percentage of the sale plus a fixed amount, including interchange |
A useful test: if the problem is on the customer’s screen, it is a gateway question. If the problem is in your bank account, it is a processor question.
What a payment gateway does at checkout
The gateway’s job is to get card details out of the customer’s browser and into the banking system without those details landing on your servers.
It does four things in sequence. It presents the card fields, usually inside an iframe it controls. It encrypts what the customer typed. It tokenizes the card, replacing the number with a reference string that is useless to a thief but that you can store and reuse. Then it transmits the authorization request onward to the processor.
A gateway also holds the controls for what happens to a charge after approval: placing a hold instead of taking payment, increasing that hold, capturing a different final amount, and refunding. For a business whose orders change between checkout and the door, those controls are the whole reason the integration gets built carefully.
What a gateway generally does not do is give you money. It also does not, on its own, resolve disputes or manage fraud liability, though many modern providers bundle fraud screening into the same product.
If most of your volume still crosses a counter, the equivalent decisions sit in your terminal rather than a gateway, which is a different set of trade-offs: what a coffee shop’s payment system has to get right is speed at the register, not holds and captures.
What a payment processor does after the card is approved
The processor is the party that actually moves value, and it works both sides of the transaction.
On the way out, it receives the authorization request from the gateway, routes it through the card network to the customer’s issuing bank, and returns the approval or decline. It verifies payment details, runs compliance and fraud checks, and authorizes or declines the transaction. On the way back, it handles settlement: batching the day’s captured transactions and moving funds from the issuing bank, through your acquiring bank, into your account.
The processor is also the party whose rates you are negotiating when you talk about “card fees,” because interchange, the portion that goes to the customer’s bank, flows through it.
Do you need both a payment gateway and a payment processor?
Yes, every card-not-present sale uses both. The question is how many companies you contract with to get them.
Two models exist, and most businesses that deliver use the first:
- All-in-one (payment service provider). Stripe, Square, PayPal and similar providers bundle the gateway, the processing and the merchant account into one signup, quoting a single blended rate. You are onboarded under their master merchant account, which is why approval takes minutes instead of weeks.
- Separate contracts. You hold a merchant account with an acquiring bank, contract a processor, and connect a standalone gateway such as Authorize.net on top. More moving parts, more paperwork, and typically better economics once your volume is high enough that interchange-plus pricing beats a flat rate.
The all-in-one model trades margin for simplicity, and the trade is usually correct while you are growing, especially if you are still getting a new business venture off the ground and cannot afford weeks of underwriting before your first sale. The signal to look at unbundling is not a feeling that fees are high. It is volume consistent enough that a processor will quote you interchange-plus and you can do the arithmetic.
One thing to check before you sign either kind of deal: whether the gateway is portable. Some providers’ gateways only work with their own processing, so switching processors later means rebuilding your checkout rather than repointing it.
Where the acquiring bank fits, and who owns a chargeback
Neither the gateway nor the processor carries the financial risk on a disputed order. The acquiring bank does.
This is the part most gateway-versus-processor explainers skip, and it is the one that costs money. When a customer disputes a charge, the acquirer receives the chargeback from the card network, debits the funds from your merchant account, and represents you in the dispute. Card networks hold the acquirer, not the processor, accountable for the dispute and fraud ratios across its whole portfolio, which is also why an acquirer is the party that can impose a rolling reserve on your account (Chargeflow, retrieved September 2026).
The processor’s role in a dispute is operational: it alerts you, forwards the dispute data, and provides the dashboard you upload evidence into, while the acquirer is the party that submits the case to the card network (Chargeflow, retrieved September 2026). The gateway’s role is to have recorded a clean transaction in the first place.
For a delivery business, that maps onto something practical. Your best defense in a dispute is evidence tied to the transaction: what was ordered, what was substituted, when it was handed over, and to whom. That evidence lives in your order system, and it is only useful if the charge and the order share a record.
How gateway fees and processing fees appear on your statement
Two distinct charges, and bundled providers hide the seam between them.
Gateway fees cover the technology that captures and transmits payment data at checkout: typically a monthly or subscription fee, sometimes a small per-transaction fee, sometimes a setup cost. Processing fees cover the movement of money and include interchange set by the card networks (IXOPAY, retrieved September 2026).
What the numbers look like in 2026:
- Flat-rate bundled pricing lands near 2.9% plus $0.30 per online transaction, usually with no monthly fee on a standard account (Stripe, retrieved September 2026).
- Across processors generally, per-transaction rates run roughly 1.5% to 3.5% plus a fixed $0.10 to $0.30 (MyPayAdvisor, retrieved September 2026).
- Event-based fees sit on top of both: chargeback fees, refund fees, cross-border and currency conversion charges, and surcharges for faster settlement.
When you compare two quotes, make sure you are comparing the same stack. A gateway-only quote of “$25 a month plus 10 cents a transaction” is not cheaper than a bundled 2.9% plus 30 cents. It does not include the processing at all.
Which one matters more if you deliver your own orders
The gateway, day to day. The processor, when you look at the numbers.
The gateway is where the delivery-specific behavior lives. Holding an authorization at checkout and capturing the real total when the driver hands the order over, incrementing for a tip, capturing less for a substitution, refunding a drop that did not happen: all of that is gateway-side API work. Choose a gateway that supports manual capture and incremental authorization, or you will be issuing partial refunds all week.
The processor determines the things you notice monthly rather than hourly: your effective rate, how fast funds settle, and what happens to your cash flow in a week with a lot of refunds. Ask about settlement timing directly if you pay suppliers on short terms.
And the acquiring relationship, bundled or not, decides how much friction a dispute carries. Ask how disputes are surfaced and how long you get to respond before you need the answer.
Frequently asked questions
Is Stripe a payment gateway or a payment processor?
Both, plus the merchant account. Stripe, Square and PayPal are payment service providers: they bundle the gateway, the processing and the underwriting into one account at one blended rate. That is why you can start taking cards in an afternoon.
Can I keep my gateway and switch processors?
Sometimes. An independent gateway like Authorize.net is designed to sit in front of different processors, so you can renegotiate processing without rebuilding checkout. A bundled provider’s gateway usually only works with its own processing, so switching means a migration. Check it before you integrate, not after.
Which one declines my customers’ cards?
Neither. The declining party is the customer’s issuing bank, which checks available funds and runs its own fraud scoring. The processor relays that decision and the gateway displays it, so the message your customer sees is the gateway’s, but the decision is not.
Do I need a merchant account as well?
You need one, but not necessarily your own. With an all-in-one provider you operate under theirs. With separate contracts you hold your own merchant account at an acquiring bank, which means underwriting, documentation and a longer wait, in exchange for a direct relationship and usually better rates at volume.
What is a payment gateway if I only take orders by phone?
The same thing, reached differently. Card-not-present orders taken over the phone or invoiced to wholesale customers still need a gateway, usually through a virtual terminal in your provider’s dashboard or a hosted payment link you email to the customer.
Sorting out which one you are actually buying
The short version: gateway for information, processor for money, acquiring bank for risk. When a checkout breaks, start with the gateway. When a deposit is short or late, start with the processor. When a chargeback lands, the acquirer is where the liability sits, whoever emailed you about it.
If you are running one bundled account, all three conversations start with the same support line, which is convenient right up until you want to change one part without touching the other two. Know which piece you are unhappy with before you start shopping.
