What is a payment gateway vs. a payment processor?

It's 9 p.m. and you're at the kitchen table comparing services to put your store online. Every website says "payments." None of them plainly say what they do. Here's the distinction that sorts most of it out: a payment gateway captures and securely forwards card details for approval, mostly in online sales, while a payment processor moves the transaction through the card networks and gets the money into your bank account.

At a physical counter, your terminal plays the capture role, so you may never think about gateways at all. The moment you sell online, the gateway question shows up.

What does a payment gateway actually do?

Think of the gateway as the online version of your card reader. When a customer types a card number into a checkout page, something has to collect that data securely, encrypt it, and hand it to the right place for approval. That something is the gateway.

It's a short job with high stakes. The gateway doesn't decide whether the card is good, doesn't move money, and doesn't send you a deposit. It's the armored handoff between the customer's browser and the approval machinery. Done well, it's invisible. Done poorly, it's where card data leaks, which is why gateways live under the PCI security standards like everything else in this industry.

What does a payment processor actually do?

The processor is the freight system. It takes the captured transaction, routes it through the card networks to the customer's bank, brings back the approval or decline in a couple of seconds, and later settles the money, batching the day's sales and depositing them into your business bank account. Your statement, your deposit schedule, and most of your fees come from this side.

When you sign a merchant agreement, you're mainly buying processing. The processor is also who answers when deposits look wrong or a chargeback arrives, which is a fancy way of saying: this is the relationship that matters most.

Does a counter-service store need both?

For in-person sales, no separate gateway is needed. The card reader or terminal captures the card, and the processor handles the rest; capture is built into the equipment. This is why a store can run for years without ever hearing the word gateway.

Selling online changes that. A web checkout needs gateway functions, and you'll either get them bundled by your processor or bolted on from a separate company. Bundled is simpler: one agreement, one statement, one phone number when something breaks. Separate can work too, but you inherit the job of making two companies point at each other when a transaction goes sideways.

If your register runs on a POS system, a point-of-sale system that manages sales and inventory, the same logic applies: the POS runs the sale, the payment path runs the card. With NRS POS and NRS Pay, those two jobs are handled together rather than stitched from parts.

Which questions cut through the sales talk?

Three direct ones. Who settles my funds and on what schedule? Will I get one statement or two? And who do I call when a payment fails, one company or a finger-pointing chain of them?

The answers tell you what you're actually buying, no matter what the marketing page calls itself. A company that answers all three plainly is worth a longer conversation. The NRS Pay team will answer all three before you sign anything.