What is a Payment Gateway?
Written by Arnon Shimoni
✓ Expert
Last updated on:
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
Layer | Function | Examples |
|---|---|---|
Billing system | Calculates what to charge and when | Solvimon, Maxio, Chargebee |
Payment gateway | Authorises the transaction securely | Adyen, Stripe, Braintree |
Payment processor | Moves money between accounts | Adyen, Worldpay, Chase Paymentech |
Card networks | Routes between issuing and acquiring banks | Visa, Mastercard, Amex |
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
Capability | Why it matters for billing |
|---|---|
Tokenisation and credential storage | Enables recurring billing without storing raw card data |
Retry and decline handling | Feeds dunning flows; recovers failed payments |
Multi-currency support | Required for international billing without separate gateways |
Webhook reliability | Billing system needs real-time payment status updates |
Reconciliation reporting | Matches gateway transactions to billing records |
3D Secure support | Fraud prevention on card-present and high-risk transactions |
Frequently Asked Questions
What is a payment gateway?
A payment gateway is the service that transmits payment details from a merchant to the acquiring bank and card networks, returning an authorisation decision. It is the connection between a checkout and the payment system.
What is the difference between a gateway and a processor?
The gateway transmits and secures the transaction data. The processor handles the actual movement of funds through the networks and settles to the merchant. Many vendors provide both, which is why the terms are used interchangeably.
How does a gateway relate to a billing engine?
The billing engine decides how much to charge and when. The gateway executes the charge. Keeping them separate lets a company change processor without rebuilding pricing, which is the main argument for not coupling them.
Why do companies use multiple gateways?
Redundancy against outages, better authorisation rates in specific markets, lower fees for particular payment methods, and local acquiring where it is required. The cost is reconciliation complexity across providers.
How do gateway fees affect billing?
Fees vary by method, currency, region and card type, so the cost of collecting a given invoice is not uniform. For low-value or high-volume billing, fee structure can materially change which payment methods are worth offering.
What should you look for in a gateway?
Coverage of the payment methods your customers actually use, local acquiring in your main markets, authorisation rates, support for the mandate types recurring billing needs, and clear handling of 3D Secure and strong customer authentication.
Related
Recurring payments. The charges a gateway executes repeatedly.
Billing engine. What decides the amount the gateway collects.
Dunning. Handling the declines a gateway returns.
Multi-currency billing. Collecting across currencies and markets.
Embedded finance. Payments embedded inside a software product.
Ready for billing v2?
Solvimon is monetization infrastructure for companies that have outgrown billing v1. One system, entire lifecycle, built by the team that did this at Adyen.
