What Is a Payment Gateway and How Does It Work?

Every online sale passes through a payment gateway, yet many merchants only learn what theirs does when something breaks. A basic understanding helps you read your own decline reports, compare providers fairly and decide how much control you want over checkout.

Payment gateway definition

A payment gateway is a secure software service that connects your checkout to the payment networks. It collects card, wallet or bank details from the customer, protects them in transit, forwards an authorization request and relays the answer back to your store. Without it, your website would have no safe way to ask a bank whether a payment is allowed.

Gateways also do more than relay messages. Modern gateways tokenize stored card data, run fraud checks, trigger 3D Secure authentication when needed, and increasingly route each transaction to the acquirer most likely to approve it. You can see how this fits together in our overview of the Everpay payment gateway.

How a payment gateway works, step by step

1. Customer submits payment details. They enter a card number, tap a wallet or choose a local payment method on your checkout page.
2. The gateway encrypts the data. Sensitive details are encrypted and usually replaced with a token, so your systems never need to store the raw card number.
3. Risk checks run. The gateway can score the transaction for fraud, check address and security code, and decide whether to ask for 3D Secure authentication.
4. The request goes to the acquirer. The gateway sends an authorization request to the processor or acquiring bank, which passes it through the card network to the customer's issuing bank.
5. The issuer decides. The issuing bank checks funds, applies its own fraud rules and returns an approval or a decline code.
6. The result returns to your store. The gateway delivers the outcome to checkout, and you show a confirmation or ask the customer to try again.

All of that typically completes in a few seconds. Funds do not move at this stage. Approval places a hold, and money is captured, cleared and settled afterwards. We cover those later stages in how merchant payment processing works.

Gateway, processor and merchant account: what is the difference?

These terms are often used interchangeably, but each plays a distinct role.

Some providers bundle all three; others let you bring your own merchant account. Our guide to payment gateway vs. merchant account explains how to decide.

Types of payment gateway integration

Hosted checkout

The customer enters payment details on a page hosted by the gateway. This is the fastest way to launch and keeps most of the card data handling off your servers, which can simplify PCI DSS compliance.

Embedded or API-based checkout

Payment fields are built into your own pages using the gateway's components or API. You control the look and flow, with more engineering work. It suits products where checkout is a core part of the experience.

Payment links and invoices

You generate a link and send it by email, chat or text. It is useful for services, phone orders and merchants with no storefront. Everpay supports hosted checkout and payment links alongside its API, so you can start simple and add control later.

What a good gateway includes

• Tokenization and encryption so raw card data stays out of your environment. See our security overview.
• Multiple payment methods including cards, wallets, bank payments and local methods. Browse supported payment methods.
• Fraud screening and 3D Secure to reduce chargebacks without blocking good customers. See fraud prevention.
• Multi-acquirer routing and cascading retries so a decline at one acquirer can be retried at another where appropriate.
• Reporting and reconciliation that shows approvals, declines and fees by method, country and acquirer.
• Webhooks and developer tooling that keep your order system in sync with payment status.

What a payment gateway costs

Gateway pricing varies. Common structures include a per-transaction fee, a percentage of volume, a monthly platform fee, or a blended rate that bundles the gateway with processing. Extra costs can appear for international cards, currency conversion, refunds, chargebacks and payouts. Compare the effective rate on your own order values, not the headline number. Current plans are on our pricing page.

Why payments fail at the gateway

Not every decline is the customer's fault. Common causes include mistyped details, issuer fraud rules, failed authentication, a processor outage, or a mismatch between the card and the acquirer. A gateway with routing and retry logic can recover some of these. For a deeper look, read how to improve payment approval rates.

How to choose a gateway

Start with the markets and payment methods your customers use, then check fraud tooling, routing flexibility, integrations and total cost. Our ecommerce gateway selection guide walks through the evaluation criteria in detail. If you want to see how a gateway fits your stack, request a demo.