A payment gateway is the pipe: front-end software that collects card data, encrypts it, and sends an authorization request. A processor is the engine: the back-end that talks to the card networks and banks so the sale can be authorized, captured, and settled. An acquirer is the bank-side network member that sponsors your merchant ID (MID) and is the party the brands can hold liable. Visa describes the same split: the gateway as front-end checkout technology, the processor as the back-end that moves authorization data, and the acquiring bank as the business's bank that holds the merchant account (Visa Acceptance Solutions, Payments guide, accessed August 2026). Software, POS, and sales contracts often print one brand across all three jobs. The work is still three jobs.
In 2024, cards were 79 percent of U.S. noncash payments by number and 8 percent by value (Federal Reserve Payments Study, released 1 Jul 2026). Every one of those card payments still needed a capture path, a switching engine, and an acquiring member. Remembering one brand is not the same as knowing which of those you hired. The full map of networks, ISOs, and software is the payments ecosystem. This page zooms in on the three names that get collapsed most often.
The pipe. Front-end software that captures and encrypts card data and sends the authorization request.
The engine. Back-end systems that talk to the networks and banks to authorize, capture, and settle.
The bank-side network member that sponsors the merchant ID and is liable to the brands.
The three jobs, without the sales language
Gateway. On a website or in an app it is the form, the token vault, the encrypted post to somewhere else. Visa calls it the front-end technology built into websites or apps to collect and protect card details. It does not sponsor your MID and does not, by itself, deposit money. A monthly "gateway" line is usually software access, sometimes plus a per-authorization fee. Treat it as a pipe rental, not as your processing rate.
Processor. The processor takes the gateway's request, sends it into the network, receives the issuer's yes or no, later captures the approved amount, and submits the batch so the networks can move value. When a statement says "processing," this is that work plus the fees wrapped around it. In speech, people call the whole vendor "the processor." In the four-party model, processor is a job, not a brand.
Acquirer. The acquirer (acquiring bank, merchant bank) is a card-network member. It sponsors the MID, is the counterparty the brands can fine or terminate, and receives settlement so it can fund you. It is not the issuing bank, which is the customer's bank, the one that approved the card. Mixing those two is how "my bank" becomes a useless answer on a funding delay.
An ISO is none of the three: it originates and supports merchants for a registered acquirer or ISO/MSP. An ISV is none of the three either: it is the POS, invoicing, or checkout product that captured the card. Both get called "our processor" in a hallway. Ask which job they actually do.
How one sale uses all three
Take a $50 card-not-present checkout. This is the path, not a quote.
- The customer enters a card (or a wallet token) on your site or in your app.
- The gateway authenticates and encrypts that data and sends an authorization request. The PAN should not sit on your server.
- The processor sends the request into the card network.
- The network routes it to the issuing bank, which approves or declines against the cardholder's credit or deposit account.
- The answer travels back in a few seconds: authorization. That is a yes, not a deposit.
- Later, usually when a batch closes, the processor captures the authorized amount and submits it for settlement.
- Settlement is when the networks move value. The issuer pays. The acquirer receives. Your bank is funded, minus the fees the contract allows to be withheld.
Card-present is the same stack with different hardware. A terminal or POS still builds an authorization, still needs an engine that talks to the networks, and still settles to an acquirer. The gateway job may live inside the device or its host. Absence of a gateway logo is not absence of the job.
Authorization is not money. Capture is a claim. Settlement is the money. Tips, delayed capture, voids, and refunds live in the gaps between those clocks.
Why software bundles the labels
Checkout, invoicing, and POS products sell "payments" as one feature. Behind the logo they still rent or own a gateway, sit in front of a processor, and need an acquirer (or a payfac that already has one). The logo on the pay button is often the software, not the bank. If you sell or buy that layer, the map is in embedded payments.
A payment facilitator is a different shape of acquiring, not a synonym for gateway. Visa describes a payfac as operating under a shared account with an acquiring bank so a business can accept cards without setting up its own merchant account. You sit as a sub-merchant. Boarding is usually faster. Switching cost, statement access, and who owns the MID live in that difference. The payfac still uses a pipe and an engine.
Sales language collapses the stack the other way. An agent says "I'm with X processor." X may be an ISO. The processor may be a second name on page four of the merchant agreement. The acquiring bank may be a third. The receipt shows a network brand the customer brought. Four logos, three jobs, one hallway noun.
The test is whether you can name who captures the card, who switches authorization and settlement, and which bank-side member sponsors the MID. If you cannot name all three, you do not yet know who you hired.
What you actually have a contract with
Read the merchant agreement for those names. The gateway may have a separate software click-through. The processor and acquirer usually sit in the merchant processing agreement. If the agreement is silent, ask in writing. The terminal firmware and the checkout footer will not give you a complete map.
When software "includes payments," ask whether you own the MID. A MID you own is an account the networks know you by, underwritten to you, with a statement in your legal name. A payfac sub-merchant ID is someone else's master account. Both can run the same gateway. They do not behave the same when you switch, when risk holds a reserve, or when you need last year's statements for a loan.
You almost never contract with Visa or Mastercard directly. The networks set brand rules and interchange schedules that the acquirer and processor must follow. The logo on the plastic is the brand the customer brought, not your counterparty.
Gateway fees are not processing fees
Every card fee is still one of three layers, no matter which logo captured the card: interchange, assessments, and markup. Interchange goes to the issuer. Assessments go to the networks. Markup is what the processor and sales organization add. A gateway fee is usually software: monthly access, per-auth, sometimes tokenization. It is not interchange, and it is not a discount that replaces markup.
Typical processing fees are often described as 1.5 percent to 3.5 percent of the transaction plus a per-item fee (U.S. Chamber of Commerce, 4 Jun 2026). Treat that as a range check on the processing stack, not as a target, not as a Relyon rate, and not as a gateway quote. A cheap gateway on an expensive plus still produces an expensive month. Compare effective rate on a real month: add every processing line, including gateway and monthly extras, divide by gross card volume, multiply by 100. If two quotes both say "2.5 percent" and only one includes the gateway, they are not the same quote.
How to tell which you have
Pull last month's statement and the merchant agreement. Ask four questions.
Who is listed as the acquiring bank or member? That is the acquirer.
Who switches the transactions? That is the processor. Batch times, funding clocks, and many statement formats come from this layer.
What software captured the card? That is the gateway, or the POS or terminal doing the gateway job. Recurring tokens and checkout UX live here.
Whose name is on the MID? If it is yours, you have a merchant account. If it is a platform's, you are likely a sub-merchant.
You can often change the pipe without changing who acquires: new checkout, same MID, same processor, new token vault. You cannot change the acquirer without new underwriting. Tokens may not follow you. "We're just switching gateways" is a software cutover. "We're switching processors" is a new account.
A gateway that vaults cards can shrink where PAN lives and cut PCI scope. It does not erase PCI. A PCI line item on the statement is not the same as being validated.
When a sale does not fund, start with the clock, not the logo. Was it authorized, captured, batched, or held by the acquirer? Gateway support cannot release a bank risk hold. The acquiring bank cannot debug your pay form. Call the layer that owns the failure.
Name the three jobs and the statement stops looking like a single vendor. The next page for that audit is how to read your merchant statement.
FAQ
What is the difference between a payment gateway and a processor? The gateway is the pipe: front-end software that captures and encrypts card data and sends an authorization request. The processor is the engine: the back-end that routes that request through the card networks, gets an issuer decision, and later captures and settles. A checkout brand that calls itself a processor is often only the pipe.
What is an acquirer in credit card processing? The acquirer is the bank-side card-network member that sponsors your merchant ID and is liable to the brands. It is not the issuing bank (the customer's bank) and not, by itself, the checkout software. Contracts often print one logo on both acquirer and processor.
Do I need both a payment gateway and a merchant account? Online and in-app checkout need a capture path (a gateway or equivalent) plus someone who acquires. A gateway without an acquiring relationship cannot settle funds to you. Card-present terminals still have both jobs; they may not show a separate gateway brand.
Can one company be my gateway, processor, and acquirer? Yes. Many products bundle the three jobs under one logo. Ask for three names anyway: who captures the card, who switches the transaction, and which bank is the network member. The merchant agreement, the MID, and the statement still have those answers if the sales deck does not.
Is a payment facilitator a gateway or an acquirer? Neither, exactly. A payfac lets you accept cards as a sub-merchant under its master account with an acquirer, instead of holding your own MID. It still uses a gateway and a processor. Boarding is usually faster. Who owns the merchant relationship is the trade.
Why is there a gateway fee and a processing rate on the same statement? The gateway fee is usually software: monthly access and sometimes a per-authorization charge. Processing is interchange, assessments, and markup on settled volume. Add both, plus the other monthly extras, before you compute effective rate.
Sources
- Visa Acceptance Solutions, "Payments: understanding the components and solutions" (gateway, processor, acquiring bank), accessed August 2026
- Federal Reserve, "Federal Reserve issues initial findings from its 2025 triennial payments study," 1 Jul 2026
- Federal Reserve Payments Study, National Payment Volumes, Top-Line Data (CY 2015-24), last update 1 Jul 2026
- U.S. Chamber of Commerce, "How to Calculate Credit Card Processing Fees," 4 Jun 2026
Questions about how this applies to your business?
Talk it through