A payment gateway is the technology that authorizes a card transaction by securely passing payment data between your customer, your business, the card networks (Visa, Mastercard, Discover, American Express), and the banks that move the money. Every time a shopper enters a card number on a website, taps a phone at a counter, or pays an emailed invoice, a gateway encrypts that data, requests approval, and returns an approved or declined response in roughly two to three seconds.
ProTech Payments, based in Katy, Texas, sets up and supports payment gateways for businesses across Houston, Fort Bend County, and the rest of the state. The right gateway controls your authorization rates, your PCI scope, and how much you pay per transaction, so picking the wrong one can quietly cost a growing merchant thousands of dollars a year in declined sales and inflated fees. Understanding the gateway is the first step to controlling those costs.
This guide defines the gateway, walks through the exact authorization sequence, breaks down what gateways cost, compares hosted versus self-hosted setups, and covers the security rules (PCI DSS, EMV, tokenization) that apply to any Texas merchant accepting cards.
What a payment gateway is
A payment gateway is a software layer that captures card data, encrypts it, and routes an authorization request to the card networks for approval. It is the digital equivalent of the old card-swipe terminal, except it works across websites, mobile apps, virtual terminals, and physical card readers from a single connection.
The gateway does not hold your money and does not set your processing rates. Its job is narrow and specific: validate the card, protect the data in transit, request approval from the issuing bank, and hand back a yes or no. Familiar names include Authorize.Net (now part of Visa), NMI, Stripe, and the gateway built into Clover devices that run on the Fiserv (formerly First Data) network.
Where the gateway sits
In a card-present setting, the gateway lives inside the terminal or point-of-sale hardware. In a card-not-present setting, it lives behind your checkout page, your payment gateway integration, or a virtual terminal where staff key in phone orders. Either way, the customer never sees the gateway directly. They see a checkout form or a card reader, and the gateway runs underneath.
How a payment gateway works
A single approved transaction moves through six steps, all in about two to three seconds.
- Capture. The customer enters or taps a card. The gateway collects the card number, expiration, and security data.
- Encryption. The gateway encrypts the data (TLS in transit, often tokenized at rest) so the raw card number never sits exposed on your server.
- Authorization request. The gateway sends the request to your processor, which forwards it through Visa or Mastercard to the cardholder’s issuing bank.
- Approval or decline. The issuing bank checks funds, fraud signals, and the address (AVS) and card security code (CVV), then returns an approved or declined code.
- Response. The gateway relays that code back to your checkout or terminal in real time.
- Settlement. At day’s end, the gateway batches approved transactions, and funds move from the issuing bank through the networks to your merchant account, usually landing in one to two business days.
Authorization vs capture vs settlement
These three terms are not interchangeable. Authorization confirms the card is valid and places a hold. Capture tells the processor to actually collect the held amount, which is why restaurants authorize a check then capture the tip-adjusted total. Settlement is the batch step that moves money. If you want the full mechanics, our guide on how credit card payments work breaks down each handoff, and credit card authorization explained covers the hold-and-capture distinction in detail.
Gateway vs processor vs merchant account
Merchants often blur these three pieces, but they do different jobs.
| Component | What it does | Example |
|---|---|---|
| Payment gateway | Encrypts and transmits card data, requests authorization | Authorize.Net, NMI, Stripe |
| Payment processor | Routes the transaction through the card networks, moves funds | Fiserv (First Data), TSYS, Worldpay |
| Merchant account | The bank account that holds settled card funds before payout | Issued by an acquiring bank |
| Card networks | Set interchange and route between banks | Visa, Mastercard, Discover, Amex |
A gateway without a merchant account cannot deposit money, and a merchant account without a gateway cannot accept online or keyed payments. ProTech Payments configures all three together through its merchant services setup so the pieces are tuned to work as one system rather than bolted together from separate vendors.
What a payment gateway costs
Gateway pricing has three common shapes, and the structure matters more than any single rate.
| Pricing model | Typical gateway cost | Best for |
|---|---|---|
| Per-transaction gateway fee | $0.05 to $0.15 per transaction | High-ticket, low-volume merchants |
| Monthly gateway fee | $10 to $25 per month, unlimited transactions | Steady mid-volume merchants |
| Bundled into processing | Folded into the per-transaction rate | Merchants who want one flat bill |
These gateway fees sit on top of interchange, the non-negotiable rate the card networks charge. Interchange ranges from roughly 0.05% on a regulated debit card under the Durbin Amendment to over 3% on a premium rewards credit card. Our breakdown of interchange fees explained shows why two cards in the same wallet can cost very different amounts to accept.
Cutting gateway and processing cost
Two pricing models save Texas merchants the most. Interchange-plus pricing passes through the true network cost plus a fixed markup, so you see exactly what the gateway and processor add. A dual-pricing or cash discount program shifts the card-acceptance cost to the customer who chooses to pay by card, which can take card processing close to zero for the business. You can estimate the impact with the dual-pricing savings calculator before changing anything.
Hosted, self-hosted, and API gateways
The integration style you choose changes both your PCI scope and your customer experience.
Hosted gateways
A hosted gateway redirects the customer to a page hosted by the gateway provider to enter card data, then sends them back. Because the card data never touches your server, your PCI scope shrinks to the simplest SAQ-A questionnaire. The tradeoff is less control over branding and flow.
Self-hosted and API gateways
A self-hosted or direct-API gateway captures card data on your own checkout, then transmits it through the gateway’s API. This gives full control over the experience and is common for custom storefronts and online payments on platforms like WooCommerce. It raises your PCI obligations, which our payment gateway setup guide walks through step by step.
In-person gateways
For in-store payments and mobile payments, the gateway is embedded in EMV chip readers and tap-to-pay terminals. The card data is encrypted at the point of capture, which keeps the merchant’s POS environment outside most of the PCI scope.
Security: PCI DSS, EMV, and tokenization
Every business accepting cards must meet the Payment Card Industry Data Security Standard (PCI DSS). The gateway is central to staying compliant because it determines how much cardholder data your systems ever touch.
Tokenization and encryption
Modern gateways replace the card number with a token, a random string that is useless if stolen. The real number stays in the gateway’s vault. Tokenization also enables recurring billing and one-click repeat purchases without storing actual card numbers on your side.
EMV and PCI scope
EMV chip technology shifted counterfeit-fraud liability to whichever party is least secure, so a merchant using a non-EMV terminal can be held responsible for fraudulent charges. Pairing EMV hardware with a tokenizing gateway is the cleanest way to reduce both fraud exposure and PCI scope. ProTech Payments handles PCI compliance directly, and our PCI compliance for small business guide explains which SAQ applies to your setup.
Choosing a gateway by business type
The right gateway depends on how you take payments.
Retail and restaurants
Counter-service and table-service businesses need a gateway tied to fast EMV and tap hardware. Clover, running on Fiserv, is a common fit for restaurant merchant services and retail merchant services because the gateway, terminal, and reporting come as one unit.
Service and professional businesses
Auto shops, salons, clinics, and law firms often invoice or take card-not-present payments, so a gateway with a strong virtual terminal and stored-card recurring billing matters most. ProTech serves auto repair, salon and spa, medical and dental, and professional services merchants with gateways built for those flows.
E-commerce and B2B
Online and wholesale sellers need API-grade gateways, address verification, and Level 2 and Level 3 data handling that lowers interchange on commercial cards. Our B2B payment processing guide covers the data fields that unlock those lower rates for B2B and wholesale merchants.
Common gateway mistakes
Three errors cost merchants the most money.
First, ignoring decline rates. A gateway that is not tuned for AVS and CVV mismatches can decline good cards. Reviewing your authorization rate is part of a free statement analysis.
Second, paying duplicate gateway fees. Some merchants pay a standalone gateway fee plus a processor markup that already includes gateway access. A statement review catches the overlap.
Third, the wrong integration for the PCI scope. Choosing a self-hosted gateway when a hosted one would do can multiply your compliance burden for no benefit. Match the integration to how you actually sell.
Payment gateways for Texas businesses
Texas merchants have a specific advantage: state law allows credit card surcharging and dual pricing when disclosed correctly, which lets a gateway shift card-acceptance cost to the customer who chooses card. A gateway that supports compliant surcharging at checkout is the mechanism that makes those programs work.
ProTech Payments installs and supports gateways for merchant services in Katy, Houston, Sugar Land, and surrounding cities, with local setup, in-person training, and statement reviews. For businesses adding a website or invoicing, that includes connecting the gateway to your storefront, your virtual terminal, and your in-person terminals so reporting stays unified.
Frequently asked questions
Is a payment gateway the same as a payment processor?
No. The gateway captures and encrypts card data and requests authorization, while the processor routes the transaction through Visa and Mastercard and moves the funds. You usually need both, and ProTech Payments configures them together so they work as one system.
Do I need a payment gateway for in-person sales?
Yes, though it is built into the terminal. EMV chip readers and tap-to-pay devices contain a gateway that encrypts the card data at the moment of capture, so even card-present sales pass through gateway technology.
How much does a payment gateway cost?
Gateways typically cost $0.05 to $0.15 per transaction, $10 to $25 per month, or are bundled into your processing rate. That gateway fee is separate from interchange, the network cost that ranges from about 0.05% on regulated debit to over 3% on premium credit cards.
Does a payment gateway make me PCI compliant?
Not automatically, but it determines how much work compliance takes. A hosted gateway keeps card data off your servers and limits you to the simplest SAQ-A questionnaire, while a self-hosted gateway increases your PCI obligations. ProTech Payments helps you pick the integration that matches your scope.
Can a payment gateway lower my processing fees?
Indirectly, yes. A gateway tuned for AVS, CVV, and Level 2/3 data can reduce declines and qualify commercial transactions for lower interchange. Pairing it with interchange-plus or a dual-pricing program is where Texas merchants see the largest savings.
Which gateway works with Clover?
Clover devices run on the Fiserv (formerly First Data) network with an integrated gateway, so the gateway, terminal, and reporting come as a single unit. ProTech Payments sets up Clover for retail and restaurant merchants across Houston and Fort Bend County.
Talk to ProTech Payments
A payment gateway only saves you money when it is matched to how you sell and priced without hidden overlap. Start with a free statement analysis and we will show you exactly what your current gateway and processing setup cost, line by line. When you are ready to move, get started with ProTech Payments and we will configure the gateway, merchant account, and hardware for your Katy, Houston, or Texas business.
