Payments
Payment Gateway
Definition
A payment gateway is the technology that captures a customer's payment details at checkout, protects them with encryption and tokenisation, and passes the transaction on to the processor, card scheme and issuing bank for authorisation, then returns the approve or decline decision to the merchant. It is the messenger in a card payment rather than the party that moves the money: the issuer debits the cardholder and the acquiring bank settles funds to the merchant.
In iGaming the gateway sits behind the operator's cashier. It handles authentication requests such as 3-D Secure, routes deposits to the right acquirer or alternative payment method, and returns the response codes that decide whether a deposit goes through. Many providers bundle gateway, processing and acquiring into one contract, which is why the terms are often used loosely, but they are distinct functions with different responsibilities.
Key takeaways
- A payment gateway captures payment details, secures them and routes the transaction for authorisation; it does not itself hold or settle the funds.
- It is distinct from the processor and the acquiring bank, although many providers sell all three together.
- In iGaming the gateway sits behind the cashier and affects deposit approval rates, authentication and routing.
- Using a gateway's hosted fields or tokenisation can keep raw card data off the operator's own systems, which narrows PCI DSS scope.
Why it matters
Every failed deposit is a lost session and often a lost customer, so the gateway behind the cashier has a direct effect on revenue. Gateways differ in which acquirers and local methods they connect to, how they handle 3-D Secure challenges, how quickly they return decisions and how clearly they report decline reasons. Payments teams use that data to retry soft declines, route transactions to the acquirer most likely to approve them and spot problems with a particular issuer or market.
The gateway is also a security boundary. If card numbers are captured in the gateway's hosted fields and replaced with tokens, the operator's own servers never see the full card number, which reduces the part of its estate that falls under PCI DSS. The flip side is dependency: tokens issued by one gateway are not always portable, so switching provider can mean asking players to re-enter card details.
That lock-in is one reason larger operators put an orchestration layer above several gateways and PSPs, keeping control of routing and failover. The Payment Operations course explains how the pieces fit together.
Payment Gateway vs Payment service provider (PSP) vs Payment orchestration
| Payment Gateway | Payment service provider (PSP) |
|---|---|
| The technical layer that captures, secures and routes a payment for authorisation and returns the result. | A commercial provider that bundles a gateway with processing, acquiring relationships, alternative methods, risk tools and reporting under one contract. |
Most operators buy a gateway as part of a PSP package. Knowing which function sits where matters when something fails, because a gateway outage, a processor problem and an acquirer decline each need a different fix.
| Payment Gateway | Payment orchestration |
|---|---|
| One connection from the merchant to a processing network, usually tied to one provider's acquirers and methods. | A layer above several gateways and PSPs that decides where each transaction goes, with rules for routing, retries and failover. |
A single gateway is simpler to run; orchestration adds resilience and bargaining power, at the cost of another integration and vendor to manage.
The bottom line
A payment gateway is the secure messenger between a checkout and the card networks. For gambling operators its quality shows up in approval rates, authentication friction and PCI scope, which is why gateway choice and routing are treated as revenue decisions.
Sources
- What is a payment gateway and how does it work? - Adyen
- Payment gateways 101 - Stripe
- PCI Data Security Standard (PCI DSS) - PCI Security Standards Council
Frequently asked questions
What is a payment gateway?
A payment gateway is the service that takes payment details from a website, app or terminal, encrypts or tokenises them, and sends the transaction to the processor and card network so the cardholder's bank can approve or decline it. The gateway then passes the decision back to the merchant. It is the communication layer of a payment, not the bank that holds or settles the money.
Payment gateway vs payment processor: what is the difference?
The gateway captures and secures payment data and routes it; the processor carries the transaction through the card network between the merchant's acquirer and the cardholder's issuer and handles authorisation messaging and settlement files. In practice many providers offer both, which blurs the line, but the gateway faces the merchant and the processor faces the networks.
Is a payment gateway the same as a merchant account?
No. A merchant account is the relationship with an acquiring bank that allows a business to accept card payments and receive the funds. The gateway is the technology that connects the business's checkout to that acquirer and the card networks. A gambling operator needs both, and the merchant account is usually the harder of the two to obtain.
Do gambling operators need their own payment gateway?
Rarely. Most operators use gateways supplied by PSPs or platform providers, often several at once through an orchestration layer. Building a proprietary gateway is mostly limited to very large groups that want full control of routing, data and costs, and even then they connect to third-party acquirers and local payment schemes.