Skip to main content
what is a payment gateway technology turnstile security checkpoint
Payment Technology

The Part of Every Transaction Nobody Talks About

Every time a customer hands over a card — in your store, on your website, through your virtual terminal — something has to move that card data from them to your bank. Securely. Instantly. Without exposing the account number to anyone who should not see it.

What is a payment gateway? It is the piece in between — the secure channel that makes everything else work. It is not the terminal. It is not the processor. It is not your merchant account. It sits between all of those things and connects them.

Most merchants never think about their payment gateway until something breaks. A transaction gets declined for no reason. A customer cannot check out online. A new POS system will not connect. Here is how it works — and what is a payment gateway in practical terms for your business.

The Definition

What Is a Payment Gateway, Exactly?

A payment gateway is the technology layer that securely captures and transmits payment data between your customer, your processor, and the card networks. Think of it as the digital equivalent of a secure armored tunnel — card data goes in one end, gets encrypted immediately, travels through the tunnel, and comes out the other side as an approval or decline.

According to PCI Security Standards Council guidelines, any system that captures, stores, or transmits cardholder data must meet specific security requirements — and your payment gateway is the first line of that defense.

1.
Captures card data — from a terminal, a website checkout form, a virtual terminal, or a mobile reader.
2.
Encrypts it immediately — so the raw card number is never transmitted in the clear.
3.
Routes it to the processor — who sends it to the card network (Visa, Mastercard) and then to the issuing bank.
4.
Returns the response — approved, declined, or flagged for review — back to your point of sale in seconds.
What a payment gateway is not

It is not the merchant account where your money lives, and it is not the processor that settles your funds at end of day. Those are separate systems. The gateway is strictly the secure transmission layer.

The Analogy

A Payment Gateway Is Like a Subway Turnstile — But for Money

When you tap your card at a subway turnstile, a few things happen in under a second: the reader captures your card data, validates it against a database, confirms you have funds or a valid pass, and either lets you through or keeps the gate closed. The turnstile does not hold your money — it just decides whether to open the gate.

A payment gateway works the same way. When your customer swipes, dips, taps, or types in their card number, the gateway reads that data, encrypts it, checks it against the card network’s database, gets confirmation from the issuing bank, and returns an approval or decline — all before the customer has finished putting their wallet away.

The key insight

A payment gateway is a checkpoint, not a vault. Your money does not live there. It travels through there.

The Types

Not All Payment Gateways Work the Same Way

The answer to what is a payment gateway depends entirely on how your customers pay you. Understanding what is a payment gateway for your specific setup is the starting point.

Hosted payment gateway

Redirects your customer to a separate page to complete payment — think PayPal checkout or Stripe’s hosted page. Your website never touches the card data, which simplifies PCI compliance, but the customer leaves your site during checkout, which increases cart abandonment.

Integrated payment gateway

Keeps the customer on your site. The gateway handles encryption in the background through tokenization, so your server never sees the raw card number. More technical setup but cleaner checkout experience and typically higher conversion rates.

In-person payment gateway

Built into your POS terminal or card reader. When a customer dips or taps their card, the terminal acts as the payment gateway — capturing and encrypting the data before it ever leaves the hardware. Most brick-and-mortar merchants are using one without realizing that is what it is called.

Virtual terminal gateway

Lets you key in card numbers manually through a browser-based interface for phone orders, invoice payments, or recurring billing. See virtual terminal payment processing for how this works in practice.

Why It Matters

Your Gateway Choice Affects Speed, Security, and Cost

Most merchants choose their payment gateway by default — whatever came with their POS system or was bundled into their Square or Stripe account. That is fine until it is not.

For merchants who have outgrown flat-rate aggregators, Square alternatives built on real merchant accounts typically cut effective rates by 20–35%.

Transaction speed

Understanding what is a payment gateway includes understanding speed. A slow gateway adds latency to every checkout. In a busy restaurant or retail environment, seconds matter. A gateway that consistently takes 4–5 seconds to return an approval creates lines, frustration, and the occasional declined-but-actually-approved confusion that leads to chargebacks.

Security and PCI scope

Part of understanding what is a payment gateway is knowing how it determines how much card data handling your business is responsible for. A properly configured gateway with tokenization and point-to-point encryption (P2PE) can dramatically reduce your PCI compliance scope — which reduces your liability and your annual compliance cost.

Compatibility

Not every gateway works with every processor or every POS system. When merchants switch processors, gateway compatibility is one of the first things to verify. A mismatch means either replacing hardware, rebuilding an e-commerce integration, or keeping a legacy gateway your new processor does not prefer.

Monthly fees

Some gateways charge a flat monthly fee ($10–$25 is common). Others bundle the cost into a per-transaction fee. If you are on interchange-plus pricing, knowing what you are paying separately for the gateway versus the processing is important — otherwise you cannot accurately calculate your true effective rate.

Clearing Up Confusion

Frequently Asked Questions

Do I need a separate payment gateway and merchant account?

Yes — these are different things. A payment gateway is the secure transmission layer. Your merchant account is where your settled funds live before they hit your business bank account. Some processors bundle both; others keep them separate.

Can I use any gateway with any processor?

No. Gateways and processors need to be compatible. Most major processors support the leading gateways (Authorize.net, NMI, Stripe’s API), but not all combinations work. This is especially relevant for e-commerce businesses with custom integrations built on a specific gateway’s API.

Is Stripe a payment gateway?

Stripe is both a payment gateway and a payment processor — they handle the transmission layer and the settlement layer under one roof. Same with Square. The distinction matters because when you use a bundled provider, you cannot switch processors without also rebuilding your gateway integration. With a standalone gateway connected to a separate processor, you can switch processors without touching your checkout.

What happens if my gateway goes down?

Transactions fail. This is why gateway uptime and redundancy matter — especially for high-volume businesses. The major standalone gateways (Authorize.net, NMI) publish uptime statistics. Your processor’s gateway should be no different.

Common Questions

Frequently Asked Questions

What is a payment gateway?

A payment gateway is the technology that transmits card data from your point of sale or website to the payment processor and card networks for authorization. It encrypts the card information, routes the transaction request, receives the approval or decline, and returns the result — all in a few seconds. Every card transaction passes through a gateway whether you see it or not. That is what is a payment gateway at its core.

Do I need a separate payment gateway for my business?

It depends on your setup. Most merchant accounts include gateway access. If you are processing in person, the terminal handles gateway communication automatically. If you are processing online, you will need a gateway that integrates with your website — either through a hosted checkout page or a direct API integration.

What does a payment gateway cost?

Most gateways charge a monthly fee of $10–$25 plus a small per-transaction fee of $0.05–$0.10. Some processors include gateway access at no additional charge as part of the merchant account. Under interchange-plus pricing, gateway fees appear as a separate line item on your statement so you can see exactly what you are paying for each component.

Next Step

Not Sure What Gateway You Are Using or What It Is Costing You?

Send us your last processing statement and we will break down exactly what you are paying — payment gateway fees, processor markup, interchange costs, all of it. Most merchants we review are paying for things they did not know were on the bill. If your gateway setup is not working for your business, we will tell you what would.

Request a Free Statement Review

No obligation • No pressure • Response within one business day

(833) 382-1992  |  hello@brooksidepayments.com

Share this post
LinkedIn Facebook X
✏️
Kevin wrote this. But if he's wrong, we'll make it right — and demote Kevin to sharpening pencils. BeBetter@brooksidepayments.com