Payment Gateway
A payment gateway is the software layer that captures payment details at checkout or at the point of sale and passes them to a processor or acquirer for authorization. It is a connection between the merchant and the card system, and it moves data rather than money.
Also called: gateway
A payment gateway sits where the customer is. It renders or hosts the checkout, collects the card details, encrypts them and sends an authorization request onward to a payment processor or directly to an acquirer. When the answer comes back it tells the merchant’s system whether the sale can proceed. It also does the work that keeps raw card data out of the merchant’s own systems — hosted fields, redirects and tokenization, which swaps the card number for a token the merchant can store and reuse.
Most gateways add more than that: routing and retry logic across several acquirers, stored-credential handling for subscriptions, and reporting that lines authorizations up against settlements. Some vendors sell gateway, processing and acquiring together on one contract, which is why the terms blur commercially even though the functions stay separate.
The money never stops at the gateway. Settlement funds move from the issuer through the scheme to the acquirer, and from the acquirer to the merchant’s bank account. A gateway outage stops new transactions being taken; it does not put already authorized funds at risk.
In practice
A gateway is a connection, not a holder of funds — no settlement money passes through it, so its failure is an availability problem rather than a money-at-risk problem. Where a provider calls itself a gateway but also receives customer funds, it is doing a second thing as well, and that part needs its own licensing analysis.
Example
A retailer’s checkout posts card details to its gateway. The gateway tokenizes the card, sends the authorization to the processor, and returns an approval in under a second. Two days later the acquirer credits the retailer’s bank account. The gateway saw every one of those transactions and never held a cent of the money.
Commonly confused with
| Term | How it differs |
|---|---|
| Payment Processor | A processor executes the authorization, clearing and settlement steps; a gateway is the connection that hands the transaction to it. |
| Payment Service Provider | PSP is a commercial label for a bundle of services sold to a merchant; the gateway is one function inside that bundle. |
See also
- Payment ProcessorA payment processor carries out the technical steps of a transaction — authorization, capture, clearing and settlement instructions — for a merchant, an acquirer or an issuer. It generally handles the transaction rather than taking ownership of the money.
- AcquirerAn acquirer is the institution that contracts with a merchant to accept card payments, submits those transactions into the card schemes, settles the merchant’s proceeds, and carries the acquiring-side financial exposure — including the cost of chargebacks the merchant cannot fund itself.
- Payment Service ProviderA payment service provider, or PSP, is a firm that moves payments for merchants or consumers. In UK and EU payment services law it is also a defined umbrella term covering several kinds of regulated provider, and Canada defines it separately again under the Retail Payment Activities Act.
- TokenizationTokenization means representing an asset, or a claim on one, as a transferable token recorded on a ledger. The token is a record of entitlement; whether legal ownership of the underlying asset moves with it depends on the contract and the governing law, not on the ledger.