Payment Gateway vs Payment Processor: What They Are and How They Work Together
Any merchant that accepts card payments uses both a payment gateway and a payment processor. However, the difference between the two isn’t too clear on the surface, especially since both functions are often bundled into a single payment platform. Knowing what exactly a payment gateway and payment processor do becomes important when a transaction fails to authorize, a checkout integration breaks, or a business needs to evaluate a new payment setup.
Here’s the main difference: a payment gateway transmits payment data, while a payment processor authorizes and settles the transaction. Both play a critical role in card payments, whether they’re offered by separate vendors or bundled into a single platform.
In this article, we’ll explore what each component does in the payment chain, how they work together during a transaction, and what businesses should understand when evaluating payment infrastructure. We’ll also take a look at Slash, a platform that supports both business banking and credit card processing needs.¹ With Slash Payment Processing, you can add secure checkout components to your website’s checkout and/or let customers pay invoices by card. Slash also serves as a merchant of record, meaning the platform takes elements of financial and legal compliance off of your hands.
See the ROI behind your spend
Use this calculator to understand impact, then manage and track it all in Slash.
Key Takeaways
- The payment gateway transmits payment data, while the processor authorizes the transaction and settles the funds.
- The gateway is the only piece a customer ever touches, which is why most people don’t know the difference until an authorization fails or you're building custom payment infrastructure.
- Tokenization is a strong security measure, since raw card numbers never reach your servers, thus limiting the access bad actors could otherwise get.
- Gateway fees typically take the form of a monthly access charge plus a per-transaction fee, while processor costs break into interchange, network assessments, and markup.
- Card settlement generally lands one to two business days after authorization, though this can be different in cases like hotel holds and subscription billing.
What Is a Payment Gateway?
A payment gateway is the technology that captures and securely transmits payment information from the customer to the systems that process it. When a customer enters their card details on a website, taps their phone at a checkout counter, or submits payment through an invoicing link, the gateway is the layer that receives that information and moves it forward.
The customer-facing steps of a purchase are typically where you’ll encounter these gateways. This can include the checkout page on an ecommerce store, the embedded payment form in an invoicing platform, or a POS system at a storefront. The gateway is the tool that collects payment data from the customer and prepares it for the authorization process.
Payment gateways are also responsible for keeping customer data secure (though the merchant is responsible for staying on top of it as well). Card numbers and CVV codes shouldn’t travel across networks in plain text, which is why gateways encrypt this data before transmission. Modern systems can also tokenize this data by replacing the card number with a randomly generated token that’s worthless to an attacker if intercepted.
This encryption and tokenization allows businesses to accept credit card payments without storing raw payment credentials in their own systems, which would create PCI DSS (Payment Card Industry Data Security Standard) compliance problems.
Simply put, the gateway delivers payment information to the processor, and the actual money movement happens later on. You can think of it like the mail truck that picks up outgoing mail from your mailbox and brings it to the post office to be shipped.
What Is a Payment Processor?
A payment processor is the infrastructure that receives payment data from the gateway, sort of like the post office in the mailman analogy. From there, it routes the transaction through the relevant card network, communicates with the issuing bank for an authorization decision, and coordinates the settlement of funds between the issuing and acquiring banks.
When a customer's card is presented for payment, the processor is the piece that determines whether the transaction is approved or declined. Through the card network, it asks the issuing bank if the cardholder has sufficient available credit or funds, if the card has been reported lost or stolen, and if any fraud signals are present in the transaction context. When approved, the issuing bank responds with an authorization code. If declined, it sends a decline reason code. Either way, it’s then up to the processor to relay that response back through the payment chain.
Payment processors support the transaction flow behind credit card payments, debit card payments, and other electronic payment methods across ecommerce checkouts and POS systems. They also manage the settlement process by coordinating the movement of money through the card network from the issuing bank to the merchant account. For card transactions, settlement generally occurs one to two business days after authorization.
Unlike a payment gateway, the processor operates largely in the background. The customer never sees the processor directly, and a merchant with an all-in-one payment platform might not either. The distinction between gateway and processor comes up most often when you’re building custom payment infrastructure or diagnosing authorization issues.
Payment Gateway vs Payment Processor: Key Differences
While payment gateways and payment processors are closely connected, they handle different parts of the transaction lifecycle. Once you understand where each system fits into the payment stack, you may be able to evaluate providers, troubleshoot payment issues, and build payment flows for your business more easily.
1. Role in the Payment Flow
The payment gateway and payment processor are in charge of different parts of the journey. Your gateway is the entry point where payment data is captured from the customer and prepared for transmission. The processor appears in the next steps by routing the payment, requesting authorization, and coordinating the exchange of funds between banks.
Let’s picture another analogy: if the payment flow is a relay race, the gateway grabs the baton (payment data) from the customer and runs the first leg of the race. From there, it passes it securely to the processor, which carries it through the authorization and settlement phases.
2. Customer Interaction
Whether directly or indirectly, the customer interacts with the payment gateway during their purchase. In any transaction, they have to pass through a checkout page, the payment form, or POS system. After the customer submits their payment, the processor communicates with the issuing bank and authorizes the purchase, all behind the scenes.
3. Security and Data Handling
Data security between gateways and processors is a bit complex. While security responsibilities are divided between the two layers, gateways are ultimately in charge of protecting payment data during transmission. They can choose to either encrypt or tokenize data before sending it across networks.
Tokenization tends to be a safer approach than encryption, as raw card numbers never actually touch the merchant’s servers and can’t easily be intercepted by fraudsters. For businesses concerned about data breach liability or PCI DSS compliance, a gateway's security approach is important.
Afterwards, the processor handles security through fraud protection and authorization logic. When processing an authorization request, it evaluates transaction-level signals such as:
- Velocity patterns (multiple authorizations in rapid succession)
- Geographic anomalies (a card used in different countries within hours)
- Device signals in card-not-present environments (security signals that verify user identity)
- Card usage history (generally tracking for suspicious activity)
Processors can also apply the card network's own fraud rules if they’re configured to do so.
4. Infrastructure Responsibilities
The inner workings of gateways and processors are quite different. The gateway is the technical interface through which payment data enters the system, often as a software and API infrastructure. It can be hosted by a third-party provider and embedded in a payments platform, integrated directly into an ecommerce store through a plugin, or occasionally self-hosted by businesses with strong technical know-how.
The processor is financial and institutional infrastructure. It has formal registered relationships with card networks and acquiring banks, and it operates the systems that communicate with issuing banks. Becoming a payment processor requires sponsorship by an acquiring bank and compliance with card network and regulatory rules. Since processing relationships are more formally structured than gateway integration, many businesses access processing through a payment service provider or acquiring bank.
5. Fees and Business Setup Considerations
Gateways and processors each carry their own fee structures, though they can be bundled by providers into a single pricing model. Gateway fees typically take the form of a monthly access fee plus a per-transaction gateway fee. Processor fees can include interchange (paid to the card issuer, set by the card network), network assessment fees, and the processor's own markup.
If a business uses a bundled provider like Stripe, PayPal, or Square, all of these costs are consolidated into a single per-transaction rate that covers both gateway and processing functions. Slash, for example, charges a flat 3% plus 40 cents per transaction.
The standard in finance
Slash goes above with better controls, better rewards, and better support for your business.
How Payment Gateways and Payment Processors Work Together
Just like athletes running a relay, gateways and processors need each other to finish the race. Here's how they interact during a typical card transaction:
- Step 1: Payment data submission -The customer submits payment information (card number, expiration date, CVV, billing address) through the checkout interface or payment terminal. This is the only customer-facing part of the process.
- Step 2: Gateway encryption and transmission -The payment gateway immediately captures this data, applies encryption and/or tokenization, and transmits it securely to the payment processor.
- Step 3: Processor routing -The payment processor receives the encrypted payment data, identifies the relevant card network based on the card number's BIN (Bank Identification Number), and routes an authorization request through that network to the customer's issuing bank. The request includes the transaction amount, merchant details, and the tokenized card data.
- Step 4: Issuing bank authorization -The issuing bank reviews the authorization request in real time by checking available credit or funds, verifying card status, and evaluating fraud signals. From there, it returns an approval code or decline reason code through the card network to the processor. All of this can typically be done in a couple seconds.
- Step 5: Gateway response -The processor passes the authorization result back through the gateway, which relays it to the checkout interface. The customer sees "Payment Approved" or an error message, depending on the result. If declined, the specific reason (insufficient funds, card flagged for fraud, do not honor) may or may not be shown to the customer, depending on the gateway.
- Step 6: Capture and settlement -For approved transactions, the merchant's system captures the authorized payment. The processor then coordinates settlement, moving funds from the issuing bank through the card network and acquiring bank to the merchant's account, typically one to two business days after capture. In some situations, such as hotel holds or subscription billing, capture can be separate from authorization.
If you’re using a dedicated payment platform, you likely won’t interact separately with a gateway and a processor because your system bundles both. However, the gateway and processor are still doing their respective jobs behind the scenes.
How Slash Can Manage Your Payment Processing
As you can tell, different financial tools and pieces of software often need to have tight-knit relationships in order to function properly. With Slash, you don’t just get a payment processor and gateway – you get just about everything else you need.
Slash is a financial platform that comes with payment processing capabilities, business banking tools, accounting automations, corporate cards, and a lot more. That means your payment processing system directly connects the money coming into your business with the tools you already use to manage it. Our platform is also a merchant of record, meaning we manage the legal aspects while accepting liability for customer transactions on your behalf.
You can use Slash Payment Processing in two ways: add card payments to your invoices or build Slash into your existing checkout with the Slash SDK and Payment Elements. When a customer pays an invoice by card, Slash automatically connects the transaction to the correct invoice and gives you a live view of what you’ve collected. If you want to build your own checkout workflow, you can use Slash’s React SDK to access the secure, prebuilt payment components needed to add card and supported wallet entry to an existing online storefront.
Slash's transaction fee of 3% plus 40 cents is far below the average merchant of record charge you'll see elsewhere. With our payment processing solution, you get competitive fees without having to worry about regulatory compliance or managing a separate merchant account.
Here’s what else you get with Slash:
- Accounting & ERP integrations: Sync transaction data with QuickBooks Online, Xero, NetSuite, or Sage Intacct to streamline reconciliation, reporting, and month-end close.
- Native cryptocurrency support: Send and receive USD-pegged stablecoins USDC and USDT across 15 supported blockchains for faster, lower-cost global payments.⁴
- Diverse payment rails: Slash supports a wide range of payment methods, including card spend, global ACH, international wire transfers to over 180 countries via SWIFT, and real-time domestic payments through RTP and FedNow.
- Global USD: The Slash Global USD account is designed as an alternative for foreign founders who want access to USD without forming a US entity.³ Accounts are backed on Base by a balance held in USDC, which is designed to maintain a one-to-one value with the US dollar.
- Enterprise-grade protection: Business accounts are protected up to $150M through Column N.A.'s insured cash sweep network.² Approvals and controls are granular down to the individual card, and AI-assisted monitoring flags spend that falls outside your policy.
Apply in less than 10 minutes today
Join the 10,000+ businesses already using Slash.
Frequently Asked Questions
What's the difference between a merchant account and a payment processor?
A merchant account and a payment processor are completely different things, but they do work hand-in-hand. A payment processor is the technical service that verifies and moves the money, while a merchant account is the dedicated bank account that holds your funds from customer transactions before they are deposited into your actual business bank account.
Merchant Accounts: How Card Payments Work
What are merchant services?
"Merchant services" is another term for the financial infrastructure, hardware, and software that allow businesses to securely accept payments from their customers.
Are online payments processed differently than physical payments made at a card reader?
Yes, online payments are processed differently than physical transactions. Online purchases are classified as Card-Not-Present transactions, whereas credit card payments at a physical card reader are classified as Card-Present transactions. Card-Present transactions are overall safer, since the card and the card reader directly communicate and no sensitive data is typed out.
