Everything the customer touches at checkout is the payment gateway: the software that collects card or account details, encrypts them, and passes the transaction to the rails behind it for authorization. The short payment gateway definition is a messenger with a form attached — it is the merchant's edge of the payment system, and the one part of it that never holds money.
How does a payment gateway work
A gateway does not decide whether a payment is approved and does not keep the proceeds. The payment gateway meaning stops at transmission: it formats and sends, the processor moves the message through the schemes, the issuing bank approves or refuses it, and the acquirer settles the money days later.
Merchants who blame the gateway for a falling approval rate are usually looking at issuer behavior that the gateway merely reported back to them.
Tokenization and how much PCI scope you keep
Storing a card is the feature merchants actually buy. Teams asking what is payment gateway tokenization are asking about this: the gateway replaces the card number with a token it holds, so saved cards, subscriptions and one-click reordering work without card data touching the merchant's servers, which keeps PCI DSS obligations at self-assessment rather than full audit.
How details are collected decides that scope. A hosted payment page puts collection entirely on the gateway's domain and takes the merchant almost out of scope; fields embedded in your own checkout give more design control and leave more responsibility with you.
The checks that run before the request leaves
Gateways apply velocity and fraud rules, trigger 3-D Secure where strong authentication is required, and claim an SCA exemption where a transaction qualifies for one. Each decision moves conversion in both directions: an exemption the issuer challenges anyway costs a customer, and an unauthenticated transaction that should have been challenged shifts dispute liability onto the merchant.
Local methods you do not have are orders you never see
Coverage is a gateway question before it is a marketing one. Selling into the Netherlands without iDEAL, or into Poland without BLIK, loses orders that no checkout tuning recovers, because the payment method the customer expects simply is not offered. Ask which alternative payment methods are live per market today, not which are on the roadmap.
Why some merchants keep the gateway separate
Buying gateway, processing and acquiring as one bundle from a payment service provider is now the default, and it is simpler to run. A standalone gateway earns its place when a merchant wants a single checkout integration in front of several acquiring banks, so that changing bank does not mean rebuilding the payment flow, and a problem on one connection does not stop sales.