What is a payment gateway? How it works, types, and cost considerations

What is a payment gateway

A payment gateway is the technology that securely connects your checkout to the payment-processing infrastructure. It handles the exchange of payment information needed to authorize a transaction and return its status to your business.

A payment gateway:

• Captures payment details entered at checkout.
• Secures the information through encryption and other security controls.
• Transmits the transaction data for authorization.
• Returns the approval or decline status to your checkout system.

The purpose of a payment gateway is to provide a secure connection between your checkout experience and the payment-processing infrastructure. It can encrypt payment information, facilitate transaction authorization, return approval or decline responses, and support secure payment data and transaction reporting.

What does a payment gateway do

A reliable payment gateway keeps revenue flowing, enables multiple payment methods, and gives you insight into customer behavior. Startups like SaaS platforms, marketplaces, and fintech apps rely on gateways to scale without growing operational complexity.

For example, when a customer purchases a USD $100 subscription from a SaaS company, the payment gateway securely captures the customer's payment details and sends the transaction through the payment-processing infrastructure for authorization. If the payment is approved, the gateway returns the payment status to the SaaS platform so it can confirm the subscription and proceed with fulfillment.

Example of a payment gateway

Stripe: A strong option for online-first businesses, particularly SaaS and e-commerce companies that need flexible payment integrations and support for multiple payment methods.

PayPal: A familiar payment option for businesses that want to offer customers a widely recognized digital checkout alongside other payment methods.

Square: Suited to businesses that sell both online and in person, with payments and point-of-sale capabilities brought into the same ecosystem.

Adyen: Better suited to businesses operating across markets that need global and local payment methods and a more comprehensive payments setup.

Understanding how payment gateways work

Each transaction is a chain of actions that determines whether money lands safely in your account. Understanding how payment gateways work helps you spot inefficiencies, reduce failed payments, and build a smoother experience for your customers.

This is how a typical online transaction moves through your system:

• Securing the payment: The gateway immediately protects sensitive details, keeping your customers’ data safe and reducing the risk of fraud. It securely captures and encrypts the payment information before sending the transaction for payment processing.
• Checking with the bank: As part of the payment gateway process, the system communicates with the customer’s bank through the payment processor and relevant payment network to verify the funds and confirm the transaction is valid.
• Confirming the order: You can fulfill the purchase with confidence once approved, ensuring your product or service reaches the customer without hiccups. The authorization response is sent back through the payment infrastructure to the gateway, which communicates the payment status to your checkout system.
• Receiving the funds: The approved payments are collected and deposited into your account, completing the cycle and letting you focus on growth instead of chasing transactions. After authorization, the payment gateway transaction moves through clearing and settlement, with the acquiring bank receiving the funds on the merchant’s behalf before they are made available to your business according to the provider’s settlement schedule.

Payment gateway transaction flow: Customer → Payment gateway → Payment processor → Payment network → Issuing bank → Authorization response → Clearing and settlement → Acquiring bank → Merchant

Important note: Optimized routing, real-time insights, and strong fraud protection don’t just secure money; they also enhance customer trust, reduce failed payments, and create a smoother path to scaling your business globally.

The role of a payment gateway in the payment ecosystem

A payment gateway is one part of a larger payment system that works behind the scenes every time a transaction happens. When a customer enters their details, several moving pieces kick into action, as you might know, like verifying the payment, routing it through the right networks, checking for fraud, and eventually settling the funds into your account. The gateway is simply one layer in that chain.

Understanding how these pieces connect matters for founders. It helps you see where fees are added, why some transactions fail, and what actually affects approval rates and cash flow as you scale.

Key components in a payment ecosystem:

Payment gateway vs payment processor

At this point, payment gateway and payment processor are often mentioned in the same breath, and many providers bundle both services into one platform. But they perform different roles in the payment flow.

When an online transaction happens, 2 distinct things must occur: the payment details must be securely transmitted for approval, and the funds must be moved between banks. These responsibilities sit with different parts of the payment infrastructure.

The payment gateway is responsible for:

• Capturing payment information at checkout
• Encrypting and securing sensitive data
• Sending the transaction for authorization
• Returning an approval or decline response

In simple terms: It handles the secure communication layer between your checkout and the payment-processing infrastructure.

The payment processor is responsible for:

• Communicating with card networks and issuing banks
• Requesting authorization of funds
• Coordinating the settlement into your merchant account
• Ensuring the funds are transferred correctly

Basically, it manages the movement of money once the request is approved.

How payment gateways and processors work together: When a customer submits a payment, the gateway securely captures and transmits the transaction details to the payment processor. The processor then communicates with the relevant payment networks and issuing bank to request authorization. The authorization response travels back through the processor to the gateway, which communicates the payment status to the merchant's checkout system. If approved, the transaction proceeds through clearing and settlement.

For founders: Understanding the difference helps you interpret fees, approval rates, and settlement timelines more clearly as you grow. Knowing who does what gives you better visibility into how revenue actually flows through your business.

Merchant accounts explained

Once a transaction is approved, the money doesn’t instantly appear in your business bank account. There’s a middle layer most founders don’t think about until settlement timelines start affecting cash flow, and that’s the merchant account.

A merchant account is a specialized account that temporarily holds funds from approved card transactions before they’re transferred to your primary business bank account. It exists because card payments don’t settle instantly. Banks need time to verify, batch, and transfer funds securely. The merchant account is where that transition happens.

When a customer pays you:

• The gateway secures the data
• The processor coordinates authorization
• The merchant account receives the funds after the transaction is captured and settled.
• Then, the settlement moves the money into your business account

Founders care because it influences:

• Settlement speed (How quickly funds reach you)
• Cash flow predictability
• Rolling reserves or payout holds imposed by the acquirer, processor, or PSP
• Chargeback management

If you’ve ever wondered why funds are delayed, partially held, or settled in batches, the merchant account is usually where those mechanics sit.

Types of payment gateways

Not all payment gateways work the same way, and the difference is not just technical architecture. It affects customer experience, compliance responsibility, and how much control you retain over checkout. The main types of payment gateways can be classified by how the payment experience is hosted and integrated into a business's website or application. For this classification, most founders will encounter 3 primary models.

1. Hosted payment gateways

Your customer is redirected to a third-party payment page to complete the transaction with a hosted gateway. You have likely seen this before. You click 'Checkout' on a website, and suddenly you are on a different branded page to enter card details.

This model can reduce the amount of payment security work your business manages directly because the provider handles the payment page and payment processing. However, outsourcing payment processing does not remove all of your PCI DSS responsibilities.

For early-stage founders, there are trade-offs:

• You give up some control over the checkout experience
• Customization is limited
• The redirect can slightly impact conversion if not implemented smoothly

Why to choose it: Hosted gateways are ideal when speed of setup and reduced operational responsibility matter more than deep customization.

2. Self-Hosted or on-site gateways

Customers enter their payment details directly on your website with this model. The data is then securely transmitted to the gateway for processing.

Unlike a hosted gateway, the payment experience remains on your website rather than redirecting the customer to a third-party payment page. From the customer’s perspective, everything happens within your branded environment. This gives you:

• Greater control over user experience
• Better alignment with your product design
• More flexibility in optimizing checkout flows

Who can choose it: This model can suit businesses that want greater control over their checkout experience and have the technical resources to manage the added implementation and security responsibilities.

3. API or fully integrated gateways

This is the most customizable approach. The gateway integrates directly into your application through APIs, allowing you to design a fully embedded payment experience. This approach is often used for embedded payments, where the payment experience is built directly into a website or application rather than sending customers to a separate payment page. You see this model frequently in SaaS platforms, marketplaces, and fintech products where payments are part of the product itself.

The advantages include:

• Deep customization
• Advanced routing and logic
• Better support for subscriptions, multi-party payments, or international expansion

The trade-off is increased implementation effort and more reliance on your internal technical capabilities.

The benefits of using a payment gateway

As your company grows, payments start affecting more than just checkout. Processing fees compound with volume, global expansion becomes complex, and rigid systems limit product flexibility. Choosing the right payment gateway can help you manage these challenges while supporting a more reliable and scalable payment experience.

It’s about gaining control over margins, scalability, data, and the overall payment experience that supports long-term growth.

Here are some of the key benefits of using a payment gateway:

• Better control over payment costs and margins: A suitable gateway lets you compare transaction pricing, payment methods, settlement terms, and other costs so you can choose an option that fits your business economics. Every transaction becomes an opportunity to optimize revenue instead of losing money to hidden fees.
• Custom experiences for your customers: You can tailor payment flows to match your product, brand, and customer behavior. For example, subscription-based models or multi-currency checkouts can be supported when the gateway offers the appropriate payment methods and integration capabilities.
• Data ownership and insights: Payment gateways can provide transaction data and reporting that help you monitor payment performance, identify failed transactions, and understand payment patterns. The amount of data and level of access depend on the provider and integration.
• Scalability: As your platform grows, a gateway with appropriate infrastructure and capacity can help you handle increasing transaction volumes without having to build payment infrastructure from scratch. Whether it’s flash sales, peak holiday traffic, or global expansion, the right payment setup can support your growth.
• Enhanced security and compliance: Established payment providers can offer security features and compliance support such as PCI DSS-related controls, tokenization, fraud monitoring, and 3D Secure, depending on the provider and payment setup. These capabilities can reduce the operational burden of managing payment security.
• Broader payment capabilities: A payment gateway can give your business access to multiple payment methods, currencies, recurring payments, and other capabilities without requiring you to develop each payment function internally.

The benefits come with trade-offs. Payment gateways can introduce transaction and processing fees, integration effort, provider dependency, and restrictions around settlement or payout timing. Depending on the provider and business risk profile, accounts may also be subject to reserves, payment holds, or additional verification. Businesses should therefore compare the total cost, capabilities, security controls, integration requirements, and settlement terms rather than choosing a gateway based only on its headline transaction fee.

Fees and costs of the payment gateway

Payment gateway fees vary by provider, payment method, transaction type, and business volume. For example, Stripe's Payments rates vary depending on the payment method and transaction type, while other payment providers have their own pricing structures. Once you start processing serious volume, even a 0.5% difference can materially impact your margins.

Beyond the headline rate, here’s what founders should actually pay attention to:

• Effective rate vs advertised rate: Blended pricing, card type differences, and volume tiers can quietly increase your real cost per transaction. The advertised payment gateway fee may therefore differ from the effective rate you actually pay after all applicable charges.
• Cross-border and FX markups: Currency conversion spreads and cross-border fees can add additional costs on top of base pricing. That directly affects global profitability. For example, Stripe's standard card pricing lists an additional 1.5% for international cards and 1% when currency conversion is required. Applicable rates can vary depending on the Stripe product and payment setup.
• Chargeback and dispute fees: Every dispute carries a fixed penalty fee. At scale, high chargeback ratios can also trigger higher processing rates. Stripe, for example, currently lists a USD $15 dispute fee on its standard pricing, although dispute pricing varies by provider and pricing plan.
• Settlement timelines: Settlement timing varies by provider, payment method, account history, and business setup. Slower settlement impacts cash flow, which can be more expensive than the fee itself.
• Hidden operational costs: Integrations, reporting limitations, reconciliation effort, and fraud tooling sometimes require add-ons or third-party tools. Those 'extras' compound over time. When comparing payment gateway costs, consider these operational expenses alongside transaction and processing fees rather than looking only at the advertised rate.

In practice, your total payment-processing cost can include the payment gateway fee, payment processing charges, cross-border or currency-conversion fees, chargeback costs, and additional software or operational expenses.

For businesses using Aspire's payment integrations, the applicable payment fees depend on the connected provider. Aspire1 currently lists Stripe, PayPal, Square, and Adyen among its payment gateway integrations.

Note: Pricing may bundle gateway services with payment processing and other payment infrastructure, so a published transaction rate should not automatically be treated as a standalone gateway fee.

Factors for selecting a payment gateway

Choose a payment gateway that fits your current stage, protects your margins at scale, and won’t block your future expansion.

For example, a SaaS startup doing USD $20K/month doesn’t need the same setup as a marketplace processing USD $5M across multiple countries. The 'best' gateway isn’t the most popular one; it’s the one that aligns with your volume, geography, risk profile, and product model.

You can evaluate it on the basis of a few important factors. When comparing payment gateway features and requirements, look beyond the basic ability to accept payments and assess payment methods, security, integrations, reporting, recurring payments, international capabilities, and scalability.

1. Start with your business model and not the pricing page

Are you:

• Subscription-based?
• Marketplace or multi-vendor?
• Cross-border from day one?
• High-ticket B2B?

Your revenue mechanics matter just as much as your size. Subscriptions need smart retry logic. Marketplaces need split settlements. D2C brands care deeply about checkout speed. Recurring payment support, failed-payment retries, and split-payment capabilities can therefore be important payment gateway features depending on your business model.

2. Look at the effective cost, not just the headline rate

That 2.9% might look standard. But you can look into:

• FX markups
• Cross-border surcharges
• Chargeback penalties
• Payout fees

At USD $1M in monthly volume, even a 0.4% difference can equal thousands in margin impact. Don’t optimize for the lowest rate. Optimize for predictable economics.

3. Understand settlement timelines

Cash flow matters more than most founders expect. Some providers settle in 1–2 days. Others may:

• Delay first payouts
• Hold rolling reserves
• Freeze funds during disputes

If you’re inventory-heavy or ad-spend dependent, payout speed can affect growth velocity more than pricing. Settlement timing and payout flexibility should therefore be treated as payment gateway requirements when evaluating providers.

4. Evaluate international readiness early

Even if you’re domestic today, check:

• Multi-currency support
• Local payment methods
• FX transparency
• Local acquiring partnerships

Switching gateways later during global expansion is painful. Choose something that grows with you. Multi-currency support and local payment methods are particularly important payment gateway features for businesses planning to expand internationally.

5. Assess fraud tools and compliance depth

You don’t need to become a compliance expert, but you should confirm a few things, including PCI DSS compliance, tokenization (https://aspireapp.com/us/blog/payment-tokenization)support, built-in fraud monitoring, and 3D Secure capabilities.

PCI DSS helps establish security requirements for handling payment card data, while tokenization replaces sensitive payment data with tokens. Fraud monitoring can identify suspicious transaction patterns, and 3D Secure adds an additional layer of customer authentication.

These security features help protect payment information, authenticate transactions, and identify potentially fraudulent activity. Fraud isn’t just revenue loss; it can increase your processing rates or even get your account flagged.

6. Check integrations and reporting

Make sure your gateway integrates cleanly with:

• Your accounting system
• Billing tools
• CRM
• ERP (if relevant)

Clear reporting saves hours every month and reduces finance team friction. API and integration capabilities, reporting, and reconciliation tools are also important payment gateway features, particularly as transaction volume and operational complexity increase.

Conclusion

The right payment gateway is the one that securely supports the payment methods, integrations, transaction economics, and operating model your business actually needs.

For most early-stage businesses, bundled payment service providers (PSPs) can simplify setup by combining payment processing, gateway capabilities, risk tools, and reporting. More complex businesses may require deeper integrations and greater control over payment flows as their payment requirements grow.

For most founders, flexibility matters more than ownership. Platforms like Aspire¹ let you streamline payments, treasury³ visibility, and expense management without rebuilding financial infrastructure from scratch. Instead of managing rails, you can focus on growth and keep your financial stack scalable as you expand.