A payment gateway is the technical layer that captures a player's payment details at checkout, encrypts them, and passes the transaction request from the operator's website or app to the payment service provider or acquiring bank for authorisation, then relays the approve-or-decline response back in real time.
Definition
A payment gateway is the technical layer that captures a player's payment details at checkout, encrypts them, and passes the transaction request from the operator's website or app to the payment service provider or acquiring bank for authorisation, then relays the approve-or-decline response back in real time. It is the piece of infrastructure a player directly interacts with (the card form, the e-wallet redirect), distinct from the PSP or acquirer that actually processes and settles the funds behind it.
A gateway typically supports multiple payment methods and PSPs behind a single integration, handles PCI-DSS-compliant tokenisation so raw card data does not sit on the operator's own servers, and often includes basic fraud screening (3-D Secure, velocity checks) before the transaction is even passed onward.
In context
For affiliates writing about operator payment infrastructure, and for B2B content aimed at operators choosing a stack, the gateway-versus-PSP-versus-acquirer distinction is one of the most commonly confused parts of the payments chain, and getting it right adds real clarity: the gateway is the pipe and the checkout experience, the PSP aggregates multiple payment methods and often multiple acquirers behind one contract, and the acquirer/acquiring bank is the entity with the direct relationship to the card scheme that actually moves the money.
Content comparing gateway providers for an iGaming audience should focus on genuinely differentiating factors: the range of local payment methods and currencies supported (critical for multi-market operators), checkout conversion rate (a poorly designed gateway checkout is a real source of lost deposits), latency and uptime, and whether the gateway is itself licensed to touch funds or purely a routing layer sitting in front of a licensed PSP. It should not present gateway choice as interchangeable with PSP or licensing choice — they solve different problems.
A practical angle for affiliate content is that operators frequently run several gateways in parallel (a cascading or waterfall setup) so a declined transaction on one route is automatically retried on another, which materially improves deposit success rates — a detail worth explaining when comparing payment stacks.
Worked example
An operator's payments review compares three gateway providers on local-method coverage (12, 18 and 27 methods respectively across its target markets), checkout conversion (78%, 82%, 85%), and cascading support, concluding the third is worth its higher fee for markets where deposit failure is the biggest churn driver.
Related terms
Frequently asked questions
Browse more iGaming terms in our glossary.
← Back to glossary