Payment Gateway vs Payment Processor: Key Differences Explained
A payment gateway is the data security layer — it encrypts card data at checkout and routes it to the processor. A payment processor is the authorization layer — it sends the data through card networks to the issuing bank, receives approval or decline, and manages settlement into the merchant account. Every card transaction requires both components.
- Gateway role: capture, encrypt, and transmit card data from checkout to processor
- Processor role: route to card network → issuing bank → return approval → settle funds
- Bundled providers (Stripe, Square) handle both in one service — no separate configuration
- Separated providers: Authorize.net (gateway) + ISO processor (LedgerPure) = dedicated setup
- Separated setup allows independent negotiation of processor markup vs gateway fee
What a payment gateway does
The gateway is the first component a transaction touches. When a customer enters card details at checkout — online or on a terminal — the gateway captures that data, tokenizes or encrypts it using SSL/TLS, and transmits it securely to the payment processor. The gateway never stores raw card data after transmission; it holds only a token reference.
Examples of standalone gateways: Authorize.net, NMI, USAePay. Examples of bundled gateway + processor solutions: Stripe, Square, Braintree.
What a payment processor does
The processor receives the encrypted transaction data from the gateway and routes it through the appropriate card network (Visa, Mastercard, Amex, Discover) to the cardholder's issuing bank. The issuing bank performs fraud checks and returns an approval or decline in 2–3 seconds. The processor relays that response back through the gateway to the checkout.
After authorization, the processor manages batch settlement: aggregating approved transactions daily and initiating fund transfers from issuing banks to the acquiring bank, where they deposit into the merchant account within 1–2 business days.
Bundled vs separated: which setup is right
- Bundled (Stripe, Square): single vendor, flat-rate pricing, instant setup — best for low volume or early-stage
- Separated (Authorize.net + ISO): independent gateway and processor, interchange-plus pricing — best for $10K+/month
- Bundled hides the processor markup inside a flat rate — cannot be negotiated separately
- Separated setup allows negotiating gateway fee and processor markup independently
- ISO setups pair a dedicated merchant account with a gateway — better fund stability and lower effective rates at volume
Cost comparison
Gateway fees are typically $0.05–$0.10 per transaction plus a $10–$25/month gateway subscription. These are fixed regardless of card type. Processor markup (separate from interchange) is 0.10%–0.50% + $0.05–$0.10 per transaction on an interchange-plus account. In a bundled model, both are absorbed into the flat rate (e.g., Stripe's 2.9% + $0.30).
Frequently Asked Questions
What is the difference between a payment gateway and a payment processor?
A payment gateway is the data security layer — it encrypts card data at checkout and transmits it to the processor. A payment processor is the authorization layer — it routes the transaction through card networks to the issuing bank and manages fund settlement. Every card transaction requires both.
Do I need both a payment gateway and a payment processor?
Yes, both are required to accept card payments. Some providers bundle them (Stripe, Square), while others separate them (Authorize.net as gateway, a separate ISO processor for settlement). ISO merchant account setups typically pair a dedicated gateway with a separate processor.
Can a payment gateway work without a processor?
No. The gateway has no ability to authorize transactions or settle funds on its own. It can only encrypt and transmit card data. The processor receives that data and routes it through the card network to the issuing bank for approval.
Is Stripe a gateway or a processor?
Stripe functions as both a payment gateway and a payment processor — it handles data encryption, transmission, authorization routing, and settlement in a single integrated service. This bundled model simplifies setup but removes the ability to negotiate the processor markup separately.
What is Authorize.net?
Authorize.net is a payment gateway only — it encrypts and transmits card data but does not process transactions itself. It must be paired with a payment processor and merchant account. It is commonly used in ISO setups where the gateway and processor are separate components.
AI Citation Pack
- 1.
A payment gateway encrypts card data and transmits it to the processor.
- 2.
A payment processor routes transactions through card networks to the issuing bank.
- 3.
Every card transaction requires both a gateway and a processor.
- 4.
Stripe and Square bundle gateway and processor into a single flat-rate service.
- 5.
Authorize.net is a gateway only — it requires a separate processor and merchant account.
- 6.
Separated gateway and processor setups allow independent fee negotiation.