Payment gateways and payment processors are two distinct but interconnected components of the payments stack — yet most business owners use the terms interchangeably. Understanding the difference helps you make smarter decisions when choosing a payment solution and avoid paying for components you don't need. This guide explains what each component does, how they interact, the key differences between them, and the modern platforms that bundle both into one.
What Is a Payment Gateway?
A payment gateway is the software layer that securely captures and transmits payment data from the customer to the payment processor. Think of it as a digital equivalent of a physical card terminal — it encrypts card details, sends an authorization request, and returns an approval or decline response to the merchant's checkout. For online businesses, the gateway integrates with the website or app and handles PCI-DSS compliant data capture. Classic standalone gateways include Authorize.Net and NMI — they connect to a separately contracted payment processor and merchant bank account.
What Is a Payment Processor?
A payment processor handles the actual movement of money between the merchant's bank (acquirer) and the customer's bank (issuer) via the card network. It routes the authorization request, handles settlement batches, and manages the flow of funds. Processors have relationships with acquiring banks and card networks. Historically, merchants needed separate contracts with a gateway provider and a processor/acquirer. Payment facilitators like Stripe and Square disrupted this by bundling the gateway, processor, and merchant account under one contract — dramatically simplifying onboarding for small businesses.
Which Do You Actually Need?
For most modern businesses, this distinction is academic — platforms like Stripe, Square, and PayPal bundle gateway and processing in a single product with unified pricing. You only need to think about them separately if you're a high-volume merchant optimizing costs (in which case you might contract a gateway like NMI and negotiate interchange-plus with a processor directly), or if you're integrating into legacy enterprise infrastructure. The key decision is whether to use a payment facilitator (fast onboarding, flat-rate pricing, less control) or a traditional gateway + processor setup (more complexity, more cost control at scale).
Key Takeaways
- Payment gateways handle data capture and transmission; processors handle fund routing and settlement.
- Modern payment facilitators (Stripe, Square) bundle both under a single contract.
- Standalone gateway + processor setups offer more cost control at high volume.
- Payment facilitators put merchants on shared accounts — enabling instant onboarding but less stability.
- At >$1M/year in volume, reviewing the gateway/processor separation typically saves money.
Top Platforms
| Platform | Category | Key Feature | |
|---|---|---|---|
| Stripe | Gateway + Processor | Unified platform, best developer experience | View |
| PayPal / Braintree | Gateway + Processor | Widest consumer recognition globally | View |
| Authorize.Net | Payment Gateway | Established standalone gateway | View |
| Adyen | Gateway + Processor | Enterprise with global acquiring | View |
| Square | Gateway + Processor | Best for in-person SMB payments | View |
How to Choose a Platform
- Start with a bundled payment facilitator (Stripe, Square) for simplicity and fast setup.
- At >$500K annual volume, model the cost of interchange-plus vs. flat-rate pricing.
- Evaluate global payment method support if you sell internationally.
- Check fraud and dispute management tools — they directly affect your net revenue.
- Ensure the gateway supports 3DS2 for EU transactions under PSD2 requirements.
Frequently Asked Questions
Do I need both a payment gateway and a payment processor?
In practice, most businesses choose a single platform that handles both. Platforms like Stripe, Square, and PayPal eliminate the need to contract separately. You only need to think about them separately if you're a high-volume merchant optimizing for cost.
How much does a payment gateway cost?
Standalone gateways typically charge $25–50/month plus a per-transaction fee ($0.05–0.15). Bundled platforms include gateway functionality in their transaction-based pricing (e.g., Stripe's 2.9% + $0.30) with no separate gateway fee.
What is PCI compliance and why does it matter?
PCI DSS (Payment Card Industry Data Security Standard) is a set of security requirements for any business that processes, stores, or transmits cardholder data. Using a compliant gateway reduces your PCI scope significantly by handling card data capture in their secure environment.
What's the difference between Stripe and PayPal?
Stripe is developer-focused with a highly customizable API — better for custom checkout experiences and complex payment flows. PayPal is consumer-recognizable with a frictionless checkout for existing PayPal users — better for businesses where consumer trust at checkout is a priority.
Related Guides
What Is Fintech? A Complete Guide to Financial Technology
Read Financial InfrastructureWhat Is Open Banking? APIs, PSD2, and the Future of Finance
Read Payments InfrastructureHow Payment Processors Work: A Guide to Modern Payments
Read Payments InfrastructureWhat Is a Payment Processor? Complete Guide (2026)
ReadIs your company in the directory?
Reach thousands of fintech professionals and investors exploring the Digital.Finance directory.
Get Listed