# Payment Gateway vs Payment Processor: What's the Actual Difference? > Payment gateway vs payment processor explained. Where the line is drawn, why most modern providers do both, and what SaaS founders should actually care about. - **Author**: Aarthi Poonia - **Published**: 2026-06-06 - **Category**: Payments, Glossary - **URL**: https://dodopayments.com/blogs/payment-gateway-vs-payment-processor --- "Payment gateway" and "payment processor" sound interchangeable, and in most modern SaaS contexts they effectively are. But the original distinction is real, and understanding it explains why some payment products bundle features that others do not. This guide breaks down what each term meant historically, where the line is today, and what actually matters when picking a provider for a SaaS business. ## The original definitions In the legacy card payments world, the two roles were separate companies handling separate steps in a transaction: ### Payment gateway A payment gateway is the technology layer that captures payment information from a customer and securely transmits it onward. Its job is the front of the transaction: - Hosting or rendering a checkout form - Encrypting card data - Tokenizing the card number for storage - Forwarding the authorization request to the processor - Returning the approval or decline to the merchant Classic gateway examples: Authorize.Net, Cybersource (when used standalone). A gateway by itself does not move money. It only routes the message. ### Payment processor A payment processor is the financial layer that actually moves the money. Its job is the back of the transaction: - Submitting the authorization to the card network (Visa, Mastercard) - Receiving the approval or decline from the issuing bank - Handling settlement (the funds movement between the cardholder's bank and the merchant's bank) - Funding the merchant's bank account on the settlement schedule - Processing chargebacks and refunds Classic processor examples: First Data (now Fiserv), TSYS, Worldpay. A processor by itself usually does not present a checkout UI. It expects the data to come in through a gateway. ```mermaid flowchart LR A[Customer] -->|"Card data"| B[Gateway] B -->|"Auth request"| C[Processor] C -->|"Network auth"| D[Card Network] D -->|"Approve/Decline"| C C -->|"Response"| B B -->|"Response"| A C -.->|"Settlement"| E[Merchant bank] ``` In the legacy model, a merchant signed contracts with both a gateway and a processor. The two had to talk to each other through brittle integrations, and the merchant paid fees to both. ## What changed: the all-in-one PSP Stripe, PayPal, Square, Adyen, and similar modern providers collapsed the gateway and processor into one platform. They built the checkout UI, the tokenization, the processor relationships, the settlement, and the dashboard into a single product. From the merchant's perspective, there is one contract, one fee, one API. This is why people now use "payment gateway" and "payment processor" almost interchangeably. When someone says "we use Stripe as our payment gateway," they technically mean "Stripe is our gateway plus processor plus card-on-file vault plus reporting layer." The distinction has largely dissolved at the SaaS level. > The gateway vs processor split mattered when you had to pick both separately. Modern SaaS founders pick one provider that does both, plus tax, plus billing, plus dashboards. The interesting choice is no longer gateway vs processor. It is platform vs platform. > > \- Ayush Agarwal, Co-founder & CPTO at Dodo Payments ## What modern providers actually do A modern payment platform combines all of the following under one brand: | Layer | What it does | Legacy name | |---|---|---| | Checkout UI | Renders payment form, captures input | Gateway | | Tokenization | Stores card data securely (PCI scope) | Gateway / Vault | | Authorization | Sends auth to card network | Processor | | Settlement | Moves funds to merchant | Processor / Acquirer | | Dashboard | Reporting, refunds, disputes | Both | | Subscription billing | Recurring charges, dunning | Add-on | | Tax calculation | Sales tax / VAT at checkout | Add-on | | Fraud detection | Risk scoring, 3DS | Add-on | A SaaS founder evaluating providers is not comparing gateways to processors. They are comparing complete platforms across feature coverage, pricing, and integration depth. ## Where the distinction still matters There are three modern contexts where the old distinction is still useful: ### 1. Enterprise multi-acquirer strategies Very large merchants sometimes use a single gateway with multiple processor relationships behind it (called "smart routing" or "multi-acquiring"). The gateway routes each transaction to whichever processor offers the best approval rate, lowest cost, or local presence for the cardholder. This is invisible to most SaaS founders, but it is why some platforms (Adyen, Worldpay) emphasize "gateway-level" routing in their enterprise pitch. ### 2. White-label and platform models Marketplace and platform businesses sometimes need a gateway layer that hands off to their underlying merchants' processors. This is the [white-label payment gateway](https://dodopayments.com/blogs/white-label-payment-gateway) model: the platform owns the customer-facing checkout, but individual sellers maintain their own processor relationships. ### 3. PCI compliance scoping The gateway layer is where PCI DSS scope is determined. If you use a hosted or inline checkout that tokenizes cards before they touch your servers, your PCI scope is dramatically smaller (SAQ A or SAQ A-EP). If you collect raw card data and pass it to a processor yourself, you fall into much heavier PCI categories (SAQ D, full audits). ## Payment service provider (PSP) "Payment Service Provider" (PSP) is a useful umbrella term for any modern platform that bundles gateway and processor functionality. Stripe, Adyen, PayPal, Square, and similar are all PSPs. Some PSPs also offer subscription billing, tax, fraud, and reporting on top. When someone asks "is Stripe a payment gateway or a payment processor," the most accurate answer is "it is a PSP that does both." ## Merchant of record (MoR) is a different category This is where the modern terminology gets confused. A merchant of record (MoR) is not the same as a PSP, even though it often sits on top of one: - A PSP processes payments for you (you are still the legal seller) - An MoR is the legal seller (you are the underlying supplier) The MoR collects payment as the seller of record, handles sales tax and VAT registration and filing, owns the chargeback risk, and pays you out as a wholesale supplier. PSPs do none of those things by default. For SaaS, this matters because the tax and compliance burden of selling globally is enormous. A PSP leaves it on you. An MoR like [Dodo Payments](https://dodopayments.com) absorbs it, handling tax compliance in 190+ jurisdictions, supporting 30+ local payment methods, and serving customers in 220+ countries and regions on your behalf. ## What SaaS founders should actually compare Forget gateway vs processor. The real comparison axes for a SaaS payment platform are: ### 1. Pricing model and total cost - Flat-rate (Stripe, PayPal): predictable, slightly higher at scale - Interchange-plus (Adyen, enterprise Stripe): cheaper at very high volume - MoR fee bundle (Dodo Payments, Paddle): higher headline rate, but includes tax and compliance ### 2. Country and payment method coverage How many countries and currencies can you accept payments from? Which local payment methods (UPI, PIX, iDEAL, Boleto, etc.) are supported? This drives international conversion more than headline rates. ### 3. Subscription billing depth Native subscription billing (Stripe Billing, Dodo subscriptions), proration, trials, dunning, customer portal, usage-based metering. For SaaS, this is often more valuable than gateway/processor differences. ### 4. Tax compliance Tax calculation only (Stripe Tax) vs full tax registration and filing (MoR model). The distinction here can save a global SaaS hundreds of hours and tens of thousands of dollars per year in compliance work. ### 5. Developer experience API quality, documentation, SDK coverage, webhook reliability, dashboard usability. For a small team, this often matters more than rate. ### 6. Settlement timing Card payments typically settle in 1 to 3 business days. Some platforms offer faster settlement for a fee. Settlement to your specific bank account in your specific currency adds another variable. ## A simple decision tree ```mermaid flowchart TD A[Need to accept payments?] --> B{Selling globally?} B -->|No, US-domestic only| C{Need subscription billing?} B -->|Yes, want tax handled| D[MoR like Dodo Payments] C -->|Yes| E[Stripe] C -->|No, one-time payments| F[Stripe or Square] B -->|Yes, very high volume, dedicated finance team| G[Adyen or enterprise Stripe] ``` For most SaaS founders, the choice comes down to: PSP if you have the resources to handle tax and compliance, MoR if you do not. ## FAQ ### Is a payment gateway the same as a payment processor? Historically no, but in modern SaaS the terms are used interchangeably. All major modern providers (Stripe, Adyen, PayPal, Square) combine gateway and processor functionality into a single platform. The distinction only matters in enterprise multi-acquirer setups or white-label platform models. ### Is Stripe a payment gateway or a payment processor? Both. Stripe is a payment service provider (PSP) that handles gateway functionality (checkout UI, tokenization, PCI scope) and processor functionality (authorization, settlement) under one brand. Most modern PSPs work the same way. ### Do I need a separate gateway and processor for my SaaS? No. A modern PSP like Stripe, Adyen, or a merchant of record like Dodo Payments covers both roles in one integration. You only need separate vendors in legacy enterprise setups or in specific multi-acquirer routing strategies. ### What is the difference between a PSP and a merchant of record? A PSP processes payments for you, but you remain the legal seller responsible for sales tax, VAT, chargebacks, and global compliance. An MoR is the legal seller of record, absorbing tax and compliance burden on your behalf. PSPs are cheaper headline; MoRs are cheaper all-in for global SaaS. ### Which one should a SaaS founder choose? For US-domestic SaaS with a finance team that can handle tax: Stripe. For enterprise SaaS with very high volume: Adyen. For global SaaS that wants tax and compliance handled: a merchant of record platform like [Dodo Payments](https://dodopayments.com). ## Conclusion The gateway vs processor distinction is mostly historical. Modern SaaS founders pick a complete payment platform, not separate gateway and processor vendors. The interesting comparisons are between pricing models, country coverage, subscription billing depth, tax handling, and developer experience. If you are evaluating providers for a global SaaS and want tax and compliance absorbed for you, see [Dodo Payments](https://dodopayments.com) and [pricing](https://dodopayments.com/pricing). --- - [More Payments articles](https://dodopayments.com/blogs/category/payments) - [All articles](https://dodopayments.com/blogs)