Payment gateway

What is a payment gateway?

A payment gateway is the technology layer that captures a customer's card details at checkout and encrypts them before passing them along for approval. It sits behind the payment form, invisible to the buyer, and hands the actual approval decision off to a payment processor and the card issuer.

How a payment gateway works

A useful mental model is a sealed envelope passed hand to hand through a chain of trusted parties, none of whom can read what is inside except the one party authorized to open it.

1. The customer enters their card details on a checkout page.
2. The gateway encrypts those details immediately, so they never travel across the internet in plain, readable form.
3. The encrypted data is sent to a payment processor.
4. The processor routes the request through the relevant card network to the customer's bank, known as the issuer.
5. The issuer checks the account, decides whether to approve or decline the transaction, and sends that decision back through the same chain.
6. The gateway relays the result to the checkout, which shows a confirmation screen or a decline message.

All of this typically takes a few seconds, even though several separate systems hand the request off to each other. The gateway captures and transmits the payment data; it does not decide whether the transaction is approved. That decision belongs to the issuing bank.

Most gateways also split the transaction into two moments rather than one:

• Authorization happens at checkout, when the issuer confirms the funds are available and places a hold on them.
• Capture is the separate step where the seller actually claims those funds, which can happen immediately or, for businesses that ship physical goods, once an order is confirmed and ready to fulfill.

A customer sees this as a single "payment successful" moment, but behind the gateway it is often two distinct events hours or days apart. A seller shipping a made-to-order product might authorize the payment the moment the order comes in but only capture the funds once the item is packed and ready to ship, reducing the chance of collecting money for an order that ultimately cannot be fulfilled.

Payment gateway vs payment processor

The two terms get used interchangeably in everyday conversation, but they do different jobs in the transaction chain.

	Payment gateway	Payment processor
What it does	Captures and encrypts payment details at checkout	Moves the transaction request through the card network for approval
What it touches	Payment data	The actual movement of money between banks
Who the customer interacts with	The checkout page, invisibly, since the gateway sits behind the payment form	Nobody directly; it works behind the scenes with the issuer and the acquiring bank

Many providers, including Stripe, bundle both functions together as a single product, which is a large part of why the two terms blur together in everyday use. A gateway without a processor behind it cannot move money anywhere; a processor without a gateway has no secure way to capture the card details in the first place.

The distinction is most useful when reading a provider's documentation or pricing page. A company advertising itself purely as a "gateway" may be describing only the data-capture layer, with a separate processor or acquiring bank relationship required to actually move money. A company describing itself as handling both has already combined the two layers into one product a business can adopt without assembling the pieces itself.

Examples of payment gateways

Stripe, PayPal, and Adyen are all commonly used payment gateways, named here factually and not as a ranking or an endorsement of one over another. Each handles the same core job, securely capturing and transmitting payment data, but they differ in:

• The payment methods they support
• The countries and currencies they cover
• How tightly they bundle the gateway function with processing, fraud screening, or reporting

A business choosing between providers is usually really choosing between these differences in coverage and bundling, not between fundamentally different definitions of what a gateway does.

Older payment infrastructure sometimes separated the gateway from the processor into two distinct products a business had to connect together itself, each with its own contract and fees. That separation is largely disappearing: most modern providers bundle both functions into a single integration, no separate gateway account to open, no separate contract to negotiate, and no risk of the two pieces falling out of sync.

A useful way to tell the two eras apart: legacy setups often describe a "gateway" and a "merchant account" as separate things a business signs up for one after the other, sometimes with different companies. A bundled, modern setup describes onboarding as a single step, one account, one dashboard, one integration.

Payment gateway fees

Gateway costs are usually not billed as a separate line item. When a provider bundles the gateway and processing functions together, as most do today, the cost of capturing and securing payment data is folded into the processing pricing rather than charged on its own.

A business comparing providers is generally comparing one combined rate, not a gateway fee stacked on top of a separate processing fee. Exact rates vary by provider, payment method, and transaction volume, so a fee calculator gives a more accurate, current picture than any figure quoted in a general definition like this one.

Where the gateway fits in a checkout

On a hosted or embedded checkout, the gateway layer is almost always invisible to the buyer. The customer sees a payment form, enters their card, and gets a confirmation; the encryption, routing, and authorization steps all happen behind that form with no visible indication a gateway was involved.

This is also largely invisible to the seller running the checkout. A no-code checkout builder handles the gateway integration as part of the platform itself, so a seller spends their time configuring products, pricing, and branding rather than wiring up gateway APIs, managing encryption keys, or maintaining PCI compliance on their own servers.

On Checkout Page specifically, that gateway layer runs on Stripe Connect, so payments settle directly into the seller's own Stripe account rather than through a merchant of record standing in as the legal seller. A seller building a checkout for a subscription box, an online course, or a set of event tickets adds products, sets prices, and chooses payment methods; nothing in that workflow requires understanding encryption standards or card network routing.