The Core Difference

A payment processor is the company that handles the actual money movement — they talk to your bank, the customer's bank, and the credit card networks to move funds from one account to another. A payment gateway is the technology that collects the customer's payment information (card number, expiration date, CVV) and sends it securely to the processor.

Think of it this way: the gateway is the form on your website or the card reader in your store. The processor is the machinery behind the scenes that makes the transaction happen. Most businesses need both, and many payment companies now bundle them together so you only sign one contract.

The distinction matters because each one has different costs, different security rules, and different things that can go wrong. Understanding what each one does helps you choose the right service for your business and know who to call when something breaks.

Key Takeaways

  • A payment gateway collects and encrypts customer payment information; a payment processor moves the money between banks and charges you a fee for doing it.
  • You need both to accept card payments, but many providers now offer them as a single bundled service.
  • Payment processors charge per-transaction fees (usually 2 to 3 percent plus a flat fee per transaction) while gateways may charge a monthly fee, per-transaction fee, or both.
  • The processor handles disputes and chargebacks; the gateway handles data security and PCI compliance.
  • Choosing between them depends on your business type, sales volume, and whether you want one vendor or multiple vendors.

What a Payment Gateway Does

A payment gateway is software that sits between your customer and the payment processor. When a customer enters their card information on your website, in your app, or at a physical terminal, the gateway encrypts that data so it cannot be read in transit. It then sends the encrypted information to the processor and waits for a response — approved, declined, or needs more information.

The gateway also handles the format of the data. Different processors expect information in different shapes, and the gateway translates your customer's input into whatever format the processor needs. It keeps a record of the transaction and can send you a receipt or confirmation email.

Common payment gateways include Stripe, Square, PayPal, Authorize.Net, and Adyen. Some are standalone (you choose your own processor), and some are bundled with a processor as part of the same service.

What a Payment Processor Does

A payment processor is a company licensed to move money on behalf of merchants. When the gateway sends them encrypted payment information, the processor decrypts it, checks with the customer's bank to confirm the funds are there, and instructs both banks to move the money. The processor charges you a fee for this service — typically 2 to 3 percent of the transaction amount plus a flat fee per transaction (often 25 to 30 cents), though rates vary by card type and industry.

The processor also handles disputes and chargebacks. If a customer claims they never made the purchase or that the charge was fraudulent, the processor investigates, gathers evidence from you, and decides who keeps the money. They also manage the relationship with the card networks (Visa, Mastercard, American Express, Discover) and your acquiring bank — the bank that holds your merchant account.

Major payment processors include Chase Paymentech, First Data, Worldpay, and Stripe Payments. Some operate independently; others are owned by banks or larger financial services companies.

How They Work Together

In a typical transaction, the customer enters their card information into the gateway. The gateway encrypts it and sends it to the processor. The processor decrypts it, checks with the card networks and the customer's bank, and sends back a yes or no. The gateway displays the result to the customer (approved or declined) and logs the transaction. The processor then settles the funds — usually within one to three business days — into your merchant account at your acquiring bank.

If something goes wrong at any step, you need to know which company is responsible. If the customer's information was stolen, that is a gateway security issue. If the customer claims they never authorized the charge, that is a processor chargeback issue. If the money never arrived in your account, that is an acquiring bank issue. Most bundled services have one support team that can route your problem to the right place, but knowing the difference helps you explain the problem clearly.

Costs: Gateways vs. Processors

Payment processors charge per-transaction fees. A typical rate is 2.2 percent of the transaction amount plus 30 cents per transaction for online credit card sales. Rates are lower for in-person card-present transactions (often 1.5 to 2 percent plus 10 cents) and higher for card-not-present transactions like phone orders (2.5 to 3.5 percent plus 30 cents). Rates also vary by card type — American Express and Discover typically cost more than Visa and Mastercard.

Payment gateways charge differently. Some charge a monthly subscription (often $10 to $50 per month), some charge per transaction (usually 20 to 50 cents), and some charge both. A few charge nothing if you use their bundled processor, making money only on the processor's per-transaction fee.

When you compare services, add both costs together. A processor at 2.2 percent plus 30 cents plus a gateway at $25 per month is different from a bundled service at 2.9 percent plus 30 cents with no monthly fee. The right choice depends on your transaction volume — high volume makes monthly fees less painful, while low volume makes per-transaction gateway fees less painful.

Bundled Services vs. Separate Vendors

Many modern payment companies offer both the gateway and the processor as a single product. Stripe, Square, PayPal, and Toast all work this way — you sign one contract, pay one set of fees, and call one support team. This simplifies setup and support, but it also means you are locked into their processor if you want to use their gateway.

Some businesses prefer to choose their gateway and processor separately. This gives you more flexibility — you can switch processors without changing your gateway, or vice versa. But it requires more setup, you may pay higher fees because neither company has your full business, and you have two support teams to coordinate if something breaks.

For most small to medium businesses, a bundled service is simpler and cheaper. For large businesses with high transaction volume or specific industry needs, separate vendors may offer better rates or features.

Security and Compliance

Both the gateway and the processor handle sensitive payment information, so both must follow strict security rules. The main standard is PCI DSS (Payment Card Industry Data Security Standard), which sets rules for how payment data must be stored, transmitted, and protected.

The gateway is responsible for encrypting the customer's information before it leaves their device. The processor is responsible for decrypting it securely and protecting it while it is in their systems. Neither should ever store the full card number after the transaction is complete — they store a token (a random string of characters) that represents the card instead.

When you choose a payment service, check whether they are PCI Level 1 certified, which is the highest level of security. Most major providers are, but it is worth confirming. You are also responsible for following PCI rules on your end — for example, you cannot store a customer's full card number in your own database.

Frequently Asked Questions

Can I use a gateway without a processor?

No. The gateway collects the information, but the processor is what actually moves the money. You need both. Some gateways will let you choose your own processor, but you cannot use a gateway alone.

What happens if my processor goes out of business?

Your acquiring bank will assign you a new processor, usually within a few days. Your gateway may need to be reconfigured to work with the new processor, but your customer data and transaction history stay with your acquiring bank. This is rare but has happened — it is one reason some businesses prefer to separate their gateway and processor.

Why do some transactions get declined even though the customer has money?

The processor checks with the customer's bank, and the bank can decline for many reasons: the card is expired, the address does not match, the transaction looks fraudulent, or the account is frozen. The processor will tell you the decline code, but only the customer's bank can explain the real reason. Have the customer call their bank.

Do I need a different processor for in-person and online sales?

No. Most processors handle both. But they charge different rates — in-person is cheaper because the card is physically present and harder to counterfeit. You may use the same processor for both and pay different fees depending on how the transaction happens.

What is a merchant account?

A merchant account is a bank account held by your acquiring bank that receives the money from your sales. The processor deposits funds there, usually within one to three business days. You need a merchant account to accept card payments — it is separate from your regular business checking account.