STACKWIRE

Finance and fintech

Payment gateway vs payment processor: what's the difference?

Published by Stackwire. Published 9 November 2026. Updated 10 November 2026.

A payment gateway securely captures and passes payment details. A payment processor handles the transaction communications that help move a payment through banks and card networks. Many modern providers bundle both jobs, which is why the terms are often confused.

Quick answer

A gateway is the secure connection between a checkout and the payment system. A processor carries out the transaction-processing work behind the scenes, including communicating with the relevant financial institutions and networks. A business may buy these services separately or use one payment service provider (PSP) that combines them. The exact division of responsibilities depends on the provider and payment method.

Comparison of payment gateway, payment processor and payment service provider roles
Gateways, processors and PSPs have different roles, although one provider may offer several of them.

What is a payment gateway?

A payment gateway is the technology that securely collects or receives payment details at checkout and sends the transaction information to the next part of the payment system. For an online store, it connects the website or app to the payment provider. In a physical shop, a point-of-sale terminal and its software perform a related role.

Think of the gateway as the secure entrance and routing layer. It helps transmit the payment request, and may support features such as hosted checkout pages, tokenization, payment-method selection and connections to more than one processor. The features included vary by provider; a gateway is not automatically a complete fraud, compliance or payment-management solution.

What is a payment processor?

A payment processor handles the technical work involved in routing and processing a payment through the payment ecosystem. For a card transaction, this can include communicating with the acquiring side, card network and issuing bank, receiving the authorization response, and supporting clearing and settlement processes.

The processor is part of a wider chain. The customer's bank (the issuer) decides whether to approve or decline the authorization request. The merchant's acquiring bank or acquirer provides the merchant's connection to the card system and receives transaction funds for settlement. The processor helps these parties exchange the information needed to complete the transaction.

Payment gateway vs payment processor: key differences

AreaPayment gatewayPayment processor
Main roleSecurely captures and transmits payment details from checkoutRoutes and processes transaction messages through the payment system
Where it sitsClose to the website, app or point-of-sale checkoutBehind the checkout, connected to acquirers, networks and banks
Typical functionsCheckout connection, data transmission, tokenization or hosted payment fields, depending on providerAuthorization routing, transaction processing and support for clearing and settlement
What it does not automatically meanIt is not necessarily the acquirer or the company holding merchant fundsIt is not necessarily the checkout interface the customer sees
How businesses buy itSeparately or bundled into a broader payment platformSeparately or bundled with gateway, acquiring and other services

Important: these are functional distinctions, not a universal map of every provider's product. Some providers use the word “processor” broadly, while others describe a full-stack platform as a PSP. Always check the actual service agreement and technical documentation rather than relying on the product label alone.

How an online card payment works

Simplified flow of an online card payment from checkout through gateway and processor to the issuing bank
A simplified authorization flow. The exact sequence depends on the provider, payment method and market.

Here is a simplified view of a typical online card payment. The exact message flow differs by provider, region, card scheme and checkout setup.

  1. The customer checks out. They enter card details or choose a saved payment method on the merchant's website or app.
  2. The gateway securely handles the payment data. It sends the payment request to the payment platform or processor. Hosted fields and tokenization can help reduce how much raw card data the merchant's systems handle.
  3. The processor routes the authorization request. The request travels through the acquiring side and card network to the cardholder's issuing bank.
  4. The issuer makes an authorization decision. The bank approves or declines based on its checks, available credit or funds, risk signals and other rules.
  5. The response returns to checkout. The response travels back through the payment chain so the merchant can show the customer whether the payment was approved.
  6. Capture, clearing and settlement follow. Depending on the transaction, the merchant captures the authorized payment. The transaction is then cleared and funds are settled through the relevant financial institutions according to their schedules and terms.

An authorization is not the same as money arriving in the merchant's bank account. A payment can be approved first and settled later. Some businesses capture immediately; others authorize first and capture when an order ships or a service is delivered.

Where does a payment service provider (PSP) fit?

A payment service provider, often shortened to PSP, offers a broader package that can combine gateway technology, processing, acquiring connections, payment methods, risk tools, reporting and merchant onboarding. The exact bundle differs between providers.

This is why a business using one integrated platform may not need to contract with a separate gateway and processor. The provider may manage several layers behind one API, dashboard and commercial agreement. That does not mean the gateway and processor have become the same technical function; it means the business is buying a bundled service.

Do you need both a gateway and a processor?

If you accept online card payments, the payment flow needs a way to collect and transmit payment details and a way to process the transaction through the payment system. But you do not necessarily need to select or manage two separate vendors.

Do not choose based on the label alone. Map the services your business actually needs and identify which provider is responsible for each one.

What should you compare before choosing a provider?

The gateway-versus-processor distinction explains the architecture. It does not tell you which provider is the better commercial choice. Compare the full operating cost and the parts of the payment experience that affect your customers.

What to compareQuestions to ask
Total feesWhat are the percentage and fixed transaction fees, monthly charges, gateway fees, cross-border costs, currency conversion charges and dispute fees?
Payment methodsDoes it support the cards, wallets, bank payments and local methods your customers actually use?
Authorization performanceCan it help improve approval rates with network tokens, account updater tools or intelligent routing? Ask how performance is measured.
Security and complianceWhich party handles card-data security responsibilities, tokenization, authentication and PCI DSS requirements? Confirm your own obligations.
IntegrationAre there reliable APIs, plugins, test environments, webhooks and documentation for your platform?
Settlement and cash flowWhen are funds paid out? Are reserves, rolling holds, payout minimums or settlement delays possible under the contract?
Disputes and supportWho provides evidence tools, chargeback notifications and support when a payment fails or is disputed?
Exit and portabilityCan you export customer tokens or payment records where permitted? What happens if you change providers?

Example: choosing between separate services and an all-in-one PSP

Imagine a growing online retailer that already uses a checkout platform but wants to change how card payments are routed. It could keep its current gateway and connect a different processor, if the contracts and integrations support that setup. Alternatively, it could move to a PSP that bundles checkout, processing and acquiring services.

The separate setup may offer more flexibility or preserve an existing checkout, but it can mean more integrations, contracts and support handoffs. The bundled option may simplify operations, but the retailer should check whether it can use the payment methods, routing controls, reporting and commercial terms it needs.

There is no universal winner. Compare the total cost, approval performance, operational workload and ability to change providers. For a related breakdown of pricing models, read how to choose a payment processor.

Compare two payment setups for the same business

Consider an online retailer that sells in its home market and plans to expand internationally. It has two broad options. The right choice depends on the retailer's integration needs, supported markets and operating model, not on whether a provider calls itself a gateway or processor.

Decision areaSeparate gateway and processing partnersIntegrated PSP
Integration workMay require coordinating separate APIs, credentials, contracts and technical support teams.May provide one integration and dashboard for several payment functions.
Routing controlCan offer flexibility if the gateway supports multiple processor connections and the merchant has the required agreements.Routing options depend on the PSP's platform, markets and commercial terms.
International expansionMerchant can select partners for particular markets, but must manage the extra relationships and integrations.One provider may simplify expansion where it supports the target countries, currencies and local payment methods.
Support and accountabilityResponsibility may be split, so the merchant should map who handles checkout, authorization, settlement and disputes.A single provider may reduce handoffs, but the contract still determines responsibility and escalation paths.
Cost comparisonAdd gateway, processing, acquiring, cross-border, currency conversion, dispute and other applicable charges.Review the complete fee schedule and any additional charges; a bundled price is not automatically cheaper.

Before signing, ask each provider to walk through one real transaction from checkout to payout, including a decline, refund and dispute. Request a written fee schedule and confirm which entity is responsible for each operational step. This makes competing proposals easier to compare than headline transaction rates alone.

Common misconceptions

Frequently asked questions

Is a payment gateway the same as a payment processor?

No. A gateway securely captures and transmits payment information from checkout. A processor handles transaction processing and communications through the payment ecosystem. Some providers offer both in one platform.

Can I use a payment gateway without a processor?

A gateway alone does not complete a card payment. The transaction still needs processing through an acquirer, processor or integrated payment provider. A gateway vendor may connect you to those services through partners.

Is PayPal a payment gateway or a payment processor?

Product descriptions can cover several roles. PayPal offers a range of payment products, and the functions included depend on the product and market. Check the specific service documentation and agreement to see whether gateway, processing and other services are bundled.

What is the difference between a PSP and a payment gateway?

A gateway is one component that securely transmits payment data. A PSP is a broader provider that may combine gateway, processing, acquiring, payment methods, risk tools and other services.

Does a payment gateway handle refunds and chargebacks?

It depends on the product. A gateway or payment dashboard may provide buttons and APIs for refunds or dispute information, but the actual refund and dispute processes involve the payment provider, acquirer, card network and banks. Confirm who is responsible for each step.

Which is better for a small business?

Many small businesses prefer an integrated PSP because it can reduce setup and vendor management. The right choice depends on supported countries and payment methods, total fees, payout terms, integration needs and support quality.

Bottom line

A payment gateway connects checkout to the payment system and securely transmits payment information. A payment processor handles transaction processing through the relevant financial institutions and networks. A PSP may combine both, along with other services. For a business, the best choice is the setup that provides the payment methods, security, reliability, support and total cost it needs—not simply the product with the most familiar label.

Sources and further reading

This article is for general educational purposes. Payment terminology, responsibilities and regulatory requirements vary by provider, payment method and country. Check your provider's current documentation and contract before making a business decision.

Explore more in Finance and fintech, or read our guide to choosing a payment processor.