A payment gateway is the software that sits at the checkout and captures the customer's card or payment details, then securely passes them onward to the processor and acquirer for authorization. Think of it as the front door of a payment: it collects the information and routes the request, but it does not move the money itself. Gateways usually handle encryption and tokenization so the raw card number is protected in transit. In many setups the gateway and the processor are bundled by the same provider, which is why people often blur the two.
In a flow
The gateway is a message leg, not a money leg. At checkout it captures the card details and forwards an authorization request toward the processor and acquirer; the actual funds move later during settlement, and banks move that money, not the gateway.
Common misconceptions
Myth: The payment gateway charges the card and moves the money.
Reality: The gateway only captures and routes the payment message. Authorization is decided by the issuer, and the money is moved by banks during clearing and settlement.
Myth: A gateway and a processor are the same thing.
Reality: They are different roles that are often bundled. The gateway captures and forwards details at checkout; the processor connects to the card networks and handles the authorization and clearing traffic. One vendor may provide both.
Related terms
See it in a guide
Sources
- Visa Core Rules and Visa Product and Service Rules ↗ · Visa (operator). Network rules governing how card transactions are accepted and routed.
- Mastercard rules and standards ↗ · Mastercard (operator). Roles in the card acceptance chain.
- EMVCo tokenization and 3DS specifications ↗ · EMVCo (operator). Standards a gateway uses to protect card data at checkout.
Educational, plain-English explainers. Not legal, compliance, tax, or financial advice. These cover fundamentals, not current fees, limits, or rates (which change). Rails and parties vary by program and country, so verify specifics against primary sources. Last reviewed June 2026.