What is a Payment Gateway?

What is a Payment Gateway?

A payment gateway is the technology layer that sits between a merchant and the financial institutions processing a transaction. When a customer enters card details at checkout, the gateway encrypts that data, routes it to the acquiring bank, receives the authorisation decision from the issuing bank, and returns an approval or decline to the merchant in a matter of seconds. The customer never sees any of this - but the whole transaction depends on it working correctly.

Payment gateways are sometimes confused with payment processors. The processor handles the actual movement of money between banks. The gateway handles the communication: capturing the transaction data, validating it, and passing it along securely. Most modern payment providers bundle both functions, which is why the distinction gets blurry in practice.

What a Payment Gateway Actually Does

The gateway performs several distinct functions within a single transaction. First, it encrypts the card data at the point of capture, preventing sensitive information from travelling across the network in readable form. Second, it routes the authorisation request to the correct card network like Visa, Mastercard, Amex which forwards it to the issuing bank. Third, it receives the authorisation response and passes it back to the merchant's checkout system. Fourth, and often overlooked, it stores tokenised payment credentials for future transactions so returning customers don't have to re-enter their card details and merchants don't have to store raw card numbers.

This tokenisation function matters significantly for subscription businesses. Recurring billing requires storing a payment credential and charging it on a future date. The gateway's token is what makes that possible while keeping the business outside the scope of storing raw cardholder data.

Payment Gateways and Billing Infrastructure

Where gateways sit in the billing stack

A billing system tells the gateway what to charge. The gateway tells the networks. The networks tell the issuing bank. The answer comes back the same way. When that chain breaks (when the gateway returns a decline, a timeout, or an ambiguous response) the billing system needs to know how to handle it. Retry logic, dunning flows, and revenue recovery all depend on the gateway communicating failure states clearly.

Multi-gateway architectures

Enterprise businesses often route transactions through multiple gateways depending on geography, payment method, or currency. A European customer paying in euros might route through Adyen; a US customer on ACH might route through Stripe. The billing layer needs to know which gateway to call for which transaction type, and reconcile the results from multiple providers into a single revenue ledger.

Gateway fees and their billing complexity

Gateways charge per transaction, often with interchange-plus pricing that varies by card type, geography, and volume tier. These fees affect net revenue and need to flow into margin reporting accurately. Billing systems that treat gateway fees as an afterthought rather than as a cost component in the revenue waterfall produce gross revenue figures that don't reflect what the business actually collects.

What to Look for in a Payment Gateway