What Is a Payment Gateway?

A payment gateway is the software layer that securely captures payment credentials at checkout, encrypts them, transmits them to the acquiring bank or processor for authorization, and returns the approve or decline decision back to the merchant. It is the bridge between a customer's card or wallet and the card networks (Visa, Mastercard, Amex), issuing banks, and alternative rails like UPI, iDEAL, or Pix.

A payment gateway is not the same as a processor or an acquirer. The gateway transmits and tokenizes the data; the processor executes the transaction with card networks; the acquirer is the merchant's bank that ultimately receives the funds. Many modern providers (Stripe, Adyen, Checkout.com, Worldpay) bundle all three functions, which is why the terminology blurs in practice.

How a Payment Gateway Works: The Five-Step Flow

Every card transaction follows roughly the same path, end to end in 2 to 4 seconds:

Steps 1 through 4 are synchronous and visible to the customer. Step 5 happens in the background and is what you reconcile against. The gateway's job is to make steps 1, 2, and 4 invisible and step 3 reliable.

Payment Gateway vs. Payment Service Provider vs. Payment Orchestrator

The three terms are not interchangeable, and the distinction matters when you choose what to integrate.

A payment gateway moves data. A PSP gives you a merchant account plus the gateway. A payment orchestrator sits above multiple gateways and PSPs, gives you one API, and decides which provider handles each transaction.

For a single-market business processing under ten million dollars annually, a single PSP is usually enough. For global operators, marketplaces, and any business processing across regions, orchestration is the only architecture that scales without a dedicated payments team.

Types of Payment Gateways

Gateways differ in where the sensitive data is collected and how much PCI scope falls on the merchant.

Hosted (redirect) gateways route the customer to the provider's own checkout page. PayPal Checkout and Klarna Hosted are common examples. Easiest to integrate (one redirect URL), lowest PCI burden (SAQ A), but the merchant gives up branding control and adds a redirect that costs 3 to 7 percentage points in conversion on mobile.

Self-hosted (direct post) gateways keep the customer on the merchant's site. The merchant collects card data and posts it to the gateway. Full branding control but PCI scope expands significantly (SAQ D for card-present input).

API-based gateways with hosted fields are the modern default. The merchant builds the checkout UI, but card fields are rendered as iframes from the gateway (Stripe Elements, Adyen Components, Braintree Hosted Fields). The customer never leaves the site, the merchant never touches raw card data, and PCI scope stays at SAQ A. This is the architecture used by 80%+ of high-conversion checkouts in 2025.

Local bank integration gateways plug into regional rails: iDEAL in the Netherlands, Bancontact in Belgium, UPI in India, Pix in Brazil. Coverage is narrow but costs are typically 30 to 70% lower than card rails.

The decision tree is simple. If you do not want to touch PCI compliance, use API-based with hosted fields. If you sell internationally, layer in local bank integrations through an orchestrator. If you have an internal compliance team, self-hosted only makes sense for very specific server-to-server flows.

The Hidden Cost of Payment Gateway Integration

Public pricing pages show transaction fees. They do not show the engineering bill.

Direct integration with a single API-based gateway typically takes 2 to 8 weeks of developer effort, depending on the integration method (ScienceSoft, 2025). That covers card payments only. Each additional gateway or alternative payment method adds 3 to 6 weeks of build, test, and certification, according to industry benchmarks. A merchant who wants to support cards in the US, iDEAL in the Netherlands, Pix in Brazil, and UPI in India through direct integrations is looking at roughly 4 to 9 months of focused engineering before a single line of new product code ships.

Then there is the ongoing cost. Each gateway requires monitoring, certification renewals (PCI DSS 4.0.1 since March 2025), schedule scheme updates, and reconciliation against settlement reports that arrive in different formats from each provider. The operational tax compounds with every connector you add.

Why Enterprises End Up With Multiple Gateways Anyway

Despite the cost, most merchants above mid-market scale end up running 3 to 8 gateways simultaneously. The reasons are concrete:

• Authorization rate uplift. Merchants using two or more gateways see 12 to 15 percentage-point increases in successful authorizations during peak sales versus single-gateway peers, based on industry benchmarks for multi-acquirer setups. On a USD 100M GMV business, that is USD 12 to 15 million in recovered revenue.
• Fee arbitrage. Routing every transaction to the lowest-fee or highest-success gateway can cut blended processing fees by up to 8%. For Adyen's intelligent routing pilot with eBay, Microsoft, and 24 Hour Fitness, the result was 26% cost savings on US debit (Adyen, 2024).
• Outage insurance. A single gateway outage during Black Friday can wipe out millions in sales. Diversification eliminates the single point of failure.
• Local rails. No single gateway covers UPI, Pix, iDEAL, MobilePay, GrabPay, and Konbini equally well. Cross-border merchants must combine providers to capture local payment methods, which now drive 66% of global e-commerce value, up from 34% a decade earlier (Worldpay Global Payments Report, 2024).
• Regulatory and risk segmentation. High-risk verticals (gaming, supplements, adult) need fallback acquirers because primary gateways can suspend the merchant with little notice.

The question for any growing merchant is not whether to use multiple gateways. It is whether to integrate them yourself or push that complexity to an orchestrator.

How to Choose a Payment Gateway: A Decision Framework

Use this scorecard before signing a contract. Each row should be evaluated on the gateway's actual capabilities, not its sales deck.

A common mistake is over-weighting fees and under-weighting authorization rate. A 0.2% fee saving on a gateway with 2% lower auth rate is a net 1.8% revenue loss.

How Juspay Hyperswitch Solves the Multi-Gateway Problem

Juspay Hyperswitch is an open-source payment orchestrator that sits above payment gateways and provides one unified API for the merchant. It supports 300+ processors and payment methods through a single integration, replacing the per-gateway engineering lift with a configuration change in a dashboard.

One API, Many Connectors

The architecture is built around three components: connectors, a routing engine, and a unified API. Each connector implements a standard interface defining authentication, base URL, currency unit handling, and the supported flows (authorize, capture, refund, dispute). For developers, this means the integration code your team writes against Juspay Hyperswitch is identical whether the underlying processor is Stripe, Adyen, Worldpay, Checkout.com, or any of the 300+ supported. Adding a new processor is a configuration change in the Hyperswitch Control Center, not a sprint.

Smart Routing

Smart Retries Recover 20 to 30% of Failed Payments

When a transaction fails, Juspay Hyperswitch's cascading retry engine reattempts the payment on a different acquirer based on the decline reason, card BIN, and historical performance for that card type. Industry benchmarks show that intelligent retry logic on the right second acquirer recovers 20 to 30% of initially declined transactions, with Stripe's published Smart Retries data showing roughly USD 9 in recovered revenue for every USD 1 spent (Stripe, 2024). Configuration is granular: max retries per day, max retries over 30 days, and per-card-network policies for Visa, Mastercard, Amex, and Discover are all tunable in the dashboard.

Frequently Asked Questions

What is the difference between a payment gateway and a payment processor? A payment gateway captures and securely transmits payment data from the customer to the processor. A payment processor executes the actual transaction with the card networks and the issuing bank. Most modern providers bundle both functions, but architecturally they are separate concerns.

How long does it take to integrate a payment gateway? Direct API integration with a single modern gateway takes 2 to 8 weeks. Each additional gateway adds 3 to 6 weeks. A multi-gateway orchestration platform like Juspay Hyperswitch reduces total time to roughly 4 to 6 weeks for two connectors, with subsequent connectors added in hours via configuration.

Why use multiple payment gateways? Multiple gateways increase authorization rates by 12 to 15 percentage points during peak loads, cut blended processing fees by up to 8% through smart routing, eliminate single-point-of-failure outage risk, and unlock local payment methods (UPI, Pix, iDEAL, etc.) that no single gateway covers globally.

The Bottom Line

A payment gateway is the smallest atom of payment infrastructure. The strategic question for 2026 is not which single gateway to pick, but how to access many gateways without paying the integration tax for each one. The math is unforgiving. Direct multi-gateway integration costs 4 to 9 months of engineering and continues to compound operationally. Smart routing and retries across multiple gateways recover 10 to 30% of revenue that single-gateway merchants leave on the table.

Juspay Hyperswitch resolves this by exposing a single API, a single Control Center, and a single PCI scope while connecting to 300+ processors and payment methods underneath. The integration time falls from quarters to weeks, and the orchestration becomes a configuration concern rather than a code concern.

Get started at app.hyperswitch.io or read the API reference. For self-hosting, the GitHub repository is Apache 2.0 licensed.