Payment Gateway vs Payment Processor

A payment gateway is the software that captures, encrypts, tokenizes, and screens a card transaction at the point of sale. A payment processor — also called the acquirer — is the back-end financial institution that routes the transaction through Visa or Mastercard to the issuing bank and settles funds into the merchant's account. Gateway is the software layer the merchant interacts with; processor is the banking layer that moves money. Most confusion comes from products like Stripe and Square that bundle both, blurring the distinction.

Who does what

How a transaction actually flows

1. Cardholder enters card. The checkout (your website or POS) posts card data to the gateway over HTTPS.
2. Gateway encrypts/tokenizes the card and packages an authorization request.
3. Gateway forwards to the processor. Over a secured connection.
4. Processor routes through the card network. Visa, Mastercard, Discover, or Amex receives the request.
5. Card network forwards to the issuing bank. The bank that issued the card to the cardholder.
6. Issuer approves or declines based on funds, fraud rules, etc.
7. Response flows back through the card network, then the processor, then the gateway, and finally to the merchant's checkout.
8. End-to-end: ~2-3 seconds. Funds settle 1-3 business days later via ACH from acquirer to merchant.

People also ask about gateway vs processor

Do I need both?

Yes — to accept cards online or with a virtual terminal you need both, though they're often bundled. A processor without a gateway has no way to capture transactions from a website or app. A gateway without a processor has nowhere to route the transaction to. The question is usually whether to buy them bundled (Stripe, Square) or separately (NMI in front of Fiserv, for instance).

Can one company be both?

Yes — Stripe, Square, PayPal, and Adyen are vertically integrated: they own the gateway and the processing relationship (often partnering with a bank-sponsor for the licensed acquiring side). Larger merchants frequently separate them: an independent gateway like NMI in front of a processor like Fiserv or Worldpay, so they can switch the back-end processor without re-engineering the checkout.

Why does this distinction matter for pricing?

Your statement may itemize a gateway fee (paid to the gateway software vendor — monthly + per-transaction) separately from processing fees (interchange + assessments + processor margin). Bundled providers like Stripe lump them into a single rate. Separating them often saves money above ~$15K monthly volume because you can negotiate the processor margin independently. See credit card processing fees.

What does a merchant account have to do with this?

The merchant account is the bank account at the acquirer (processor) that receives settled funds. It is underwritten — you're approved (or declined) based on your business risk profile. A processor and merchant account come together; the gateway is the software that connects to them. ISOs and PayFacs distribute merchant accounts on behalf of processors.

Why people use a separate gateway

• Processor flexibility. A processor-agnostic gateway like NMI connects to 200+ acquirers — switch processors without changing your software stack.
• Multi-channel unification. One gateway for e-commerce, in-person, and mobile means unified reporting across channels.
• Tokenization independence. Tokens belong to the gateway's vault — you keep card-on-file relationships even if the processor changes.
• Reseller/white-label branding. ISOs and software platforms brand the gateway under their own name while reselling underlying processing. See white-label payment gateways.

FAQ

Related