What Is a Pay Gateway? A Beginner’s Guide to Payment Gateways

A pay gateway is software that connects a customer’s checkout with the companies responsible for authorizing and processing a payment. The standard industry term is payment gateway; “pay gateway” is usually shorthand or a search misspelling for the same thing.

When a customer enters payment details or selects a wallet, the gateway securely sends the transaction request to the relevant payment provider. It then returns a result—such as approved, declined, or pending—to the website or app.

A gateway is therefore the communication layer at checkout. It does not necessarily issue cards, approve transactions, or move settlement funds itself.

Last reviewed: July 29, 2026. ## What does a payment gateway do?

A payment gateway helps a merchant accept electronic payments without connecting directly to every bank, card network, wallet, or provider.

Its usual responsibilities include:

• Connecting checkout to a payment form
• Transmitting a payment or authorization request
• Returning the provider’s transaction status
• Linking the result to an order or invoice
• Supporting operations such as capture, refunds, reconciliation, or webhooks when available

The exact boundary varies. The PCI Security Standards Council glossary notes that terms such as payment gateway, payment processor, and payment service provider are sometimes used interchangeably. Some companies provide only gateway technology, while others bundle gateway, processing, acquiring, fraud tools, and settlement services.

The simplest definition is:

A payment gateway carries payment information and status messages between checkout and the organizations that process and authorize the transaction.

How does a pay gateway work?

A typical online card payment passes through several organizations in a few seconds. Authorization happens first; settlement of the funds usually happens later.

1. The customer starts checkout

The customer confirms an order and selects an available method. Payment details may be entered on the merchant’s page, inside an embedded form, or on a hosted provider page.

A hosted page can reduce how much sensitive payment information touches the merchant’s own systems, but it does not automatically remove every security or compliance responsibility.

2. The gateway creates and transmits the request

The gateway packages the required transaction information, which can include the amount, currency, order reference, payment credentials, and authentication data.

The request is then transmitted to a processor, acquirer, or payment service provider.

3. The request reaches the card issuer

For a card transaction, the processor and card network route the authorization request to the bank that issued the customer’s card.

The issuer approves or declines the request based on factors such as account status, available funds or credit, authentication, and risk controls.

Visa Acceptance describes the gateway as the component that transmits payment information from the merchant to the appropriate parties, while the acquirer and issuer perform different financial roles in the process (Visa Acceptance Support Center).

4. The gateway returns the status

The response returns through the payment chain. The gateway translates it into a status the merchant can use:

• Authorized
• Declined
• Pending
• Authentication required
• Failed because of a technical error

The merchant can then show an appropriate message to the customer and update the order.

5. Capture and settlement follow

An authorization confirms that the transaction may proceed, but it is not always the same as receiving the money.

The merchant or provider may capture the transaction immediately or later. The financial institutions then complete clearing and settlement under their own schedules and rules.

The Reserve Bank of Australia’s explanation of a typical card transaction distinguishes the issuer from the merchant’s acquirer and notes that the acquirer provides funds to the merchant (Reserve Bank of Australia).

Payment gateway vs processor, acquirer, and merchant account

These terms describe connected but distinct roles. Because providers often bundle them, a merchant may interact with one company even though several functions are being performed behind the scenes.

• Payment gateway: Sends transaction information between checkout and the payment infrastructure. It normally relays an authorization decision and does not settle funds by itself.
• Payment processor: Routes authorization, capture, refund, and settlement messages. It relays the issuer’s decision and helps process settlement.
• Acquirer: Provides card-acceptance services to the merchant, participates in routing, and typically pays transaction proceeds to the merchant.
• Issuer: Provides the customer’s card or account, makes the card-authorization decision, and sends funds through the payment system.
• Merchant account: The account or arrangement used to receive card-payment proceeds. It does not approve payments.
• Crypto payment gateway: Creates or tracks crypto payment instructions and network confirmation. It may facilitate or track transfers to a configured wallet, but it does not use a card issuer’s approval model.

These are typical definitions, not universal product boundaries. Confirm which organization owns processing, fund movement, refunds, disputes, compliance checks, and support.

A practical card-payment example

Imagine an online shop selling a pair of shoes for $80.

• The customer clicks Pay and chooses a card.
• The gateway sends the $80 authorization request to the shop’s payment provider.
• The processor and card network route it to the customer’s issuer.
• The issuer approves or declines the request.
• The gateway returns that result to the shop.
• If approved, the shop confirms the order.
• Capture and settlement take place under the provider’s and acquirer’s rules.

The gateway carried the messages, but the issuer decided whether to approve the purchase.

A gateway also cannot guarantee that every payment will succeed. An issuer or provider may decline a transaction, request additional authentication, restrict a method, or return a temporary error.

How do digital wallets work with a gateway?

A digital wallet can provide a credential or token instead of requiring typed card details. The gateway and processor still send the transaction through the appropriate payment flow.

EMVCo explains that EMV Payment Tokenisation replaces the primary account number with a constrained alternative value called a payment token. That token may be limited to a particular merchant, device, or payment scenario (EMVCo).

Tokenization can reduce the usefulness of exposed information, but it is not a complete security solution. Each participant remains responsible for its systems.

What is a crypto payment gateway?

A crypto payment gateway helps a merchant present and track blockchain-based payment instructions. Instead of sending a card authorization to an issuer, the flow may involve:

• Selecting a supported asset and network
• Calculating the required crypto amount
• Providing a payment address and QR code
• Watching the relevant blockchain for the transaction
• Waiting for the required confirmation state
• Updating the merchant’s order
• Forwarding or settling supported funds according to the merchant’s configuration

Crypto payments use a different confirmation model from cards. Network compatibility, rates, quote expiry, wallet accuracy, fees, and confirmation timing can affect the result.

Merchants evaluating this model can read more about a crypto payment gateway. Paymegate supports eligible card and crypto methods through independent providers, and supported crypto payouts use wallets configured by the merchant. Method availability and provider checks may apply.

Are payment gateways secure?

A gateway can support a safer payment architecture, but the word “gateway” is not itself a security certification.

For card payments, PCI DSS provides baseline technical and operational requirements for protecting payment account data. Its scope includes entities that store, process, or transmit cardholder data, as well as systems that can affect the cardholder-data environment (PCI Security Standards Council).

Useful controls or capabilities to investigate include:

• Hosted or provider-controlled payment fields
• Encryption and tokenization
• Merchant-account access controls
• Protected API credentials
• Signed webhook verification
• Transaction monitoring and audit records

Some card flows also use EMV 3-D Secure. EMVCo describes EMV 3DS as a protocol that exchanges transaction, payment-method, and device information between the merchant and issuer to authenticate a customer during a card-not-present purchase (EMVCo).

No single control eliminates fraud, disputes, or operational risk. Merchants should assess how the entire payment flow is designed and which party owns each security responsibility.

Does outsourcing checkout remove PCI DSS responsibilities?

Not necessarily.

PCI SSC states that outsourcing all payment processing can mean many PCI DSS requirements do not apply directly to the merchant’s environment. However, the merchant still remains responsible for confirming that the provider protects account data and for understanding the shared responsibilities (PCI SSC outsourcing guidance).

Merchants should confirm their exact validation obligations with the acquirer, payment brand, or organization managing their compliance program.

How can a business integrate a pay gateway?

Three common approaches are available.

Hosted checkout

The customer is redirected to a provider-controlled payment page. This is often the fastest option for a small business because the provider supplies most of the checkout interface.

E-commerce plugin

A plugin connects the gateway to a supported store or content-management platform. The merchant still needs to configure credentials, payment methods, order states, and notifications correctly.

Payment API

An API gives developers more control over orders, checkout, and reconciliation. It also requires careful server-side handling of credentials and webhooks.

Developers considering Paymegate can review the merchant API documentation. API keys should remain on the server, and a merchant should verify a payment event before fulfilling an order.

How much does a payment gateway cost?

There is no universal fee structure. A merchant may encounter:

• A platform or gateway fee
• Provider or processor charges
• Card or payment-network costs
• Currency-conversion charges
• Blockchain-network fees for crypto transactions
• Refund or dispute-related fees
• Monthly, setup, or minimum-usage charges

Ask what pricing includes and whether rates vary by method, country, currency, transaction size, or business category.

For Paymegate’s current platform pricing and its distinction between platform and independent-provider fees, see the pricing page.

How should you choose a payment gateway?

Start with the payment experience your customers need, then evaluate the full operational setup.

Check:

• Payment-method fit: Does it support the cards, wallets, bank methods, or crypto assets relevant to your customers?
• Geographic availability: Are those methods available to your business and buyers?
• Provider requirements: Can providers apply identity, business, eligibility, geographic, sanctions, fraud, or transaction checks?
• Integration options: Is hosted checkout, a plugin, or an API available?
• Security responsibilities: Which systems handle sensitive data, and what must your business validate?
• Settlement: Where do funds go, in what form, and on what schedule?
• Reconciliation: Can you match provider events to orders and invoices?
• Refund and dispute handling: Which organization manages each process?
• Pricing: Which charges are fixed, variable, or controlled by third parties?
• Support: Who helps when a transaction is pending or fails?

You can explore Paymegate’s payment gateway overview for its supported card-and-crypto order flow. Availability varies, independent-provider checks may apply, and crypto payout destinations are configured by the merchant.

Common questions about pay gateways

Is “pay gateway” the same as “payment gateway”?

Usually, yes. “Pay gateway” is a common shorthand or misspelling. “Payment gateway” is the clearer term to use in business and technical documentation.

If you intended a specific product or similarly named brand, see the separate guide explaining what PayGate is.

Is a payment gateway a bank?

Not necessarily. A gateway is usually a technology or service layer. Banks, issuers, acquirers, processors, and regulated payment providers may perform other parts of the transaction.

Can a payment gateway approve a card?

The gateway normally transmits the request and returns the response. The customer’s card issuer makes the authorization decision, although processors and providers may also apply their own eligibility, risk, or technical controls.

Does an approved payment mean the merchant has the money?

Not always. Approval usually refers to authorization. Capture, clearing, settlement, blockchain confirmation, or payout may still need to occur.

Can customers pay without creating an account?

That depends on the gateway and the selected provider. Some hosted checkouts allow guest payment, while others require authentication or verification. For a customer-focused walkthrough, read how to pay with PayGate.

Which payment methods can a gateway support?

Depending on the service, a gateway may connect to cards, digital wallets, bank payments, local methods, or crypto assets. Support does not mean that every method is available for every merchant, buyer, currency, country, or transaction.

The separate PayGate payment methods guide explains how to check method availability before starting payment.

The key point

A pay gateway is the software bridge between checkout and the organizations that process a payment. It sends transaction information, receives a status, and helps the merchant connect that result to an order.

It should not be confused with the issuer that approves a card, the acquirer that serves the merchant, or the settlement process that moves funds. Understanding those boundaries makes it easier to compare providers, evaluate fees, assign security responsibilities, and design a reliable checkout.