The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →A payment gateway is the technology that securely collects payment details at checkout, protects and routes the transaction request, and returns an approval, decline, or pending result to a website, app, or point-of-sale system. It is the online equivalent of the communications role played by a card terminal in a shop.
A gateway usually does not act alone or necessarily hold the merchant’s money. The provider may also bundle processing, acquiring, fraud screening, merchant-account services, reporting, and payouts, which is why products such as Stripe, PayPal, Square, and Adyen can appear to perform the entire payment operation.
Payment gateway definition
At checkout, the gateway connects the customer and merchant to the payment infrastructure behind a transaction. It can collect card, wallet, bank-account, or other payment details; encrypt or tokenize sensitive data; send an authorization request to a processor or acquirer; support authentication and fraud checks; and return the result to the merchant.
The gateway is best understood as a secure communications and transaction-orchestration layer. It routes information and instructions. Authorization, capture, settlement, and payout are separate stages, although one modern payment provider may manage several of them.
Recommended Free Tools
#1 Best Overall
- With Square Terminal, you can ring up sales, accept payments, and print receipts, all with one device. Use it at the counter or ring up customers anywhere in your store.
- Accept all major credit and debit cards and pay one low rate with no hidden fees and no long-term contracts.
- Process chip cards in just two seconds.
- Get your money as soon as the next business day.
- Use it cordlessly with the built-in battery, designed to last all day.
The parties commonly involved are:
- Customer: chooses a payment method and submits payment details.
- Merchant: sells the goods or services and fulfills the order.
- Payment gateway: presents or supports checkout, protects data, routes requests, and reports status.
- Processor: handles transaction processing and communication between the merchant, acquirer, issuer, and payment networks.
- Acquirer or acquiring bank: represents the merchant in the card system and facilitates receipt of card-payment proceeds.
- Card network or payment network: routes transactions and operates network rules, such as Visa or Mastercard.
- Issuing bank: provides the customer’s card or account and decides whether to authorize the transaction.
A physical terminal performs a comparable communication job for an in-person card payment. A gateway performs it mainly for websites, apps, payment links, and other remote transactions.
How a payment gateway works
A typical online card payment follows this sequence. Other payment methods use different rails and timing, but the same broad ideas—secure data collection, authorization, status reporting, and later settlement—still apply.
- Checkout begins. The customer selects products or services and chooses a card, wallet, bank method, or another supported option.
- Payment details are collected. A hosted checkout page, embedded provider component, iframe, mobile SDK, or API-based flow receives the information.
- Data is protected. The gateway or payment component encrypts data in transit and may replace card credentials with a token. A token can be used for later charges without exposing the original card number to the merchant’s systems.
- The request is routed. The gateway sends the transaction to a processor or acquirer. For a card, the request may travel through a card network to the issuing bank.
- Risk and authentication checks run. Fraud systems can evaluate device information, velocity, address and CVV results, transaction history, and other signals. The customer may be asked for 3-D Secure or another step-up authentication.
- The issuer decides. The issuing bank checks account status, card validity, available funds or credit, fraud indicators, and its authorization rules, then approves or declines.
- The result returns. The gateway reports success, failure, pending, or authentication-required status to the merchant. A reliable integration should also confirm the state server-side or through signed provider webhooks rather than trusting only a browser redirect.
- Capture and settlement follow. Authorization approves or reserves the amount. Capture instructs the system to finalize it. Settlement moves funds through the payment system, and payout is when the provider sends funds to the merchant’s bank account. Some providers capture automatically; others allow delayed or separate capture.
- Later events are managed. The same platform may support cancellations, refunds, recurring charges, disputes, chargebacks, reporting, and reconciliation.
What does a payment gateway do?
Collect payment data
It provides or supports fields and interfaces for cards, digital wallets, bank accounts, and alternative payment methods. Hosted forms keep the sensitive entry experience on the provider’s page; embedded fields let the merchant present a more integrated design while the provider’s component handles the data.
Encrypt and tokenize credentials
Encryption protects information as it travels. Tokenization substitutes a non-sensitive reference for a card number, which can reduce the amount of raw card data in the merchant’s environment. Tokenization does not automatically remove every PCI DSS obligation.
Free tools Windows power users keep installed
One-click scans. No signup required.
Route and authorize transactions
The gateway sends a request to the appropriate processor, acquirer, or payment-method provider and returns the issuer’s decision. It may also select among available routes in a more advanced payment-orchestration setup.
Support authentication and fraud controls
Depending on the product, controls include 3-D Secure, address verification, CVV checks, velocity limits, rules, machine-learning risk scores, device signals, and dispute-management tools. These controls reduce risk but cannot guarantee that a transaction is genuine or that a chargeback will be won.
Rank #2
- A complete countertop point of sale — Combine dual responsive touchscreens, built-in POS software, and durable hardware for a fast, reliable checkout experience.
- Serve customers faster — Run smoothly through busy shifts, complex menus, and big orders with high-speed processing, memory, and responsive touchscreen displays.
- Accept every way they pay — Take all major cards at one simple rate, with no hidden fees or long-term contracts. Receive funds as soon as the next business day.
- Handle real-world demands — Resist everyday spills, dust, and wear with a durable, IP54-rated design.
- Stay reliable through every rush — Maintain strong connectivity and consistent performance through your busiest hours.
Manage the payment lifecycle
Full-stack platforms may expose APIs and dashboards for authorization, capture, cancellation, refunds, partial refunds, recurring billing, disputes, webhooks, and reconciliation. A basic gateway may provide only the transmission and status layer, so capabilities must be checked provider by provider.
Payment gateway versus payment processor
| Component | Main role |
|---|---|
| Payment gateway | Collects, protects, transmits, and reports payment information, especially at checkout. |
| Payment processor | Processes the transaction and communicates among the merchant, acquirer, issuer, and payment networks. |
| Acquirer or acquiring bank | Represents the merchant in the card system and facilitates settlement of proceeds. |
| Issuing bank | Provides the customer’s card or account and decides whether to authorize. |
| Card network | Routes card transactions and sets network rules, such as Visa or Mastercard. |
| Merchant account | An account or arrangement used to receive card-payment proceeds; a payment service provider may supply it indirectly. |
| Payment service provider | A broader service that can bundle gateway, processing, acquiring, merchant-account, fraud, billing, and payout functions. |
The distinction is useful for understanding the system, but it is often invisible commercially. Stripe, PayPal, Adyen, and similar providers combine several layers, so a merchant may sign one contract rather than separate gateway, processor, and acquiring agreements.
Payment gateway versus payment terminal
A gateway is primarily software for remote payments. A terminal is physical equipment that reads a chip, magnetic stripe, or contactless device for an in-person transaction. An omnichannel provider can connect both: the same business might use a gateway for its online store and terminals in a shop, with shared reporting or customer records.
Types of payment gateways
Hosted or redirected checkout
The customer is sent to a payment page controlled by the provider. This is usually the fastest route to launch and can reduce the amount of payment-data infrastructure the merchant maintains. The trade-offs are less control over design, possible redirect friction, and provider branding or flow constraints.
Embedded checkout
The form appears within the merchant’s site or app through hosted fields, iframes, SDKs, or provider components. It can produce a smoother branded experience, but it requires more integration, testing, script security, and potentially more complex PCI DSS assessment.
Direct API integration
The merchant’s backend communicates directly with the provider’s APIs. This suits subscriptions, marketplaces, SaaS platforms, and unusual payment flows, but demands experienced engineering, idempotency, webhook handling, monitoring, reconciliation, and security controls.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #3
- Windows 11 PROFESSIONAL POS TERMINAL - Equipped with Intel Core i5 High-Performance CPU, 4 GB Memory, and 128 GB Hard Disk. It also offers versatile connectivity options, including two serial ports, four USB ports, an HDMI output, an audio input, a DC 12V power input, and an Ethernet port.
- SLEEK & COMPACT DESIGN - Volcora POS Terminal is designed to take up as little space as possible so you can focus on better utilization of the counter space. Our sleek yet heavy-duty metal base ensures the terminal is well-stabled while taking orders with style. Suitable for any business such as retail stores, quick service restaurants, dine-in restaurants, cafes, bars, and more.
- DUAL WIDE TOUCHSCREEN - Terminal comes with one 15.6" capacitive LCD touchscreen and one 11.6” capacitive LCD touchscreen for customer display, combined with 1366x768 high-resolution, makes it easy to read and touch with minimal effort. Our POS Terminals can also withstand over 15000 hours of screen time with little to no quality sacrifice.
- IN THE BOX - Volcora 15.6" & 11.6” Dual-TouchScreen Windows 11 Professional POS Terminal, Power Adapter, Registration Card, and User Manual.
- LIFETIME WARRANTY & SUPPORT - Simply unbox, and set up your POS terminal like a Windows tablet with ease. We do understand that additional support might be needed for non-tech-savvy users and our US Based Customer Service team is committed to help. Plus, all Volcora products come with a limited lifetime warranty so you can purchase with peace of mind.
Payment links and no-code pages
Providers can create a hosted page or link for invoices, donations, freelancers, social selling, and businesses validating demand without building a complete storefront.
Omnichannel gateways
These support online, in-app, recurring, and in-person payments under one platform. They are useful for retailers, restaurants, and subscription businesses with several sales channels.
Benefits of a payment gateway
- Reduced direct exposure to card data: Encryption, tokenization, hosted fields, and authentication tools can reduce what the merchant’s systems handle.
- Faster implementation: Hosted pages, plugins, SDKs, and prebuilt integrations avoid direct connections to every bank and network.
- More payment choices: One integration may support cards, wallets, bank transfers, buy-now-pay-later products, local methods, and recurring billing.
- Less checkout friction: Wallet buttons, mobile-optimized forms, saved payment methods, and local currencies can make payment easier.
- Risk and dispute tools: Rules, screening, authentication, and evidence workflows help manage fraud and chargebacks.
- Recurring billing: Tokenized credentials can support subscriptions, subject to consent, provider rules, network requirements, and account-updater availability.
- Reporting: Transaction, payout, refund, dispute, and reconciliation records help finance and operations teams.
- International reach: Some providers offer multiple currencies, local methods, and local acquiring, although availability varies by merchant country, customer country, business type, and method.
Payment gateway fees and total cost
Typical costs can include:
- Percentage and fixed per-transaction fees.
- International-card and currency-conversion charges.
- Payment-method-specific fees.
- Chargeback or dispute fees.
- Instant-payout, recurring-billing, software, or invoicing fees.
- Engineering, maintenance, failed-payment, and reconciliation costs.
- Reserves or delayed payouts for higher-risk businesses.
Compare the complete cost against your transaction size and mix. A high fixed fee is especially significant on small orders; a flat rate may be expensive at high volume; interchange-plus pricing can be more transparent but usually requires more payments expertise.
Public US pricing signals (reviewed August 18, 2026)
These are displayed examples, not universal quotes. Country, payment method, card type, volume, risk, contract, and account configuration can change the result.
| Provider | Displayed US pricing signal | Official details |
|---|---|---|
| Stripe | 2.9% + $0.30 per successful domestic-card transaction on standard online pricing; additional charges can apply to manually entered cards, international cards, and currency conversion. No setup or monthly fee was displayed for standard pricing. | Stripe pricing |
| PayPal | Displayed rates included 2.89% + $0.29 for certain expanded card checkout, 2.99% + $0.49 for PayPal Checkout card payments, and 3.49% + $0.49 for PayPal and Venmo payments. Exact rates depend on product and account. | PayPal pricing and detailed fee table |
| Square | 2.6% + $0.15 for certain online or invoice card payments; Square says fees vary by payment type, location, and plan. | Square fees |
| Adyen | $0.13 fixed processing fee plus a payment-method-specific fee, with no setup or monthly fee shown on the reviewed page; some card pricing uses interchange-plus structures. | Adyen pricing |
Are payment gateways secure?
Gateways can provide encryption, tokenization, authentication, fraud screening, access controls, and monitoring. Security still depends on the merchant’s website, scripts, credentials, servers, integrations, staff access, and operational practices.
PCI DSS applies to entities that store, process, or transmit cardholder data, including merchants and service providers. PCI DSS v4.0.1 is identified in Adyen’s compliance documentation as the current version. A hosted page or tokenized field may reduce exposure and compliance scope, but outsourcing payment handling does not automatically make the merchant PCI compliant. Merchants should use the correct Self-Assessment Questionnaire and address payment-page scripts, vulnerability scanning, and surrounding systems. See PCI Security Standards Council terminology and Adyen’s PCI DSS guidance.
Rank #4
Common failures and how to design for them
Declined payment
Insufficient funds, incorrect or expired details, issuer restrictions, fraud rules, cross-border limits, authentication failure, unsupported methods, and temporary outages can all cause a decline. Keep the cart intact, show a useful but non-revealing message, offer another method, avoid blind repeated retries, and inspect provider decline codes and logs.
Authorization succeeds but checkout reports failure
A network interruption can prevent the merchant from receiving the success response. Use idempotency keys, server-side status checks, provider transaction IDs, and webhooks before fulfilling or retrying an order.
Duplicate charges or orders
Repeated button clicks, browser retries, timeouts, merchant retries without idempotency, and incorrectly processed webhooks are common causes. Disable repeated submissions and make both payment creation and order fulfillment idempotent.
Authorization expires
Delayed fulfillment can outlast an authorization window. Capture rules and windows vary by provider, network, payment method, and industry, so a business may need to capture promptly or reauthorize.
Refund versus reversal
A cancellation or void can stop an uncaptured authorization. A refund normally applies after capture. Posting time is controlled partly by the issuer and banking system, so a customer may not see the result immediately.
Chargebacks and payout holds
A gateway can help gather evidence and manage a dispute but cannot guarantee the outcome. Providers may also delay payouts or request business information when volume, fraud signals, prohibited products, compliance checks, or chargeback risk change.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsBest Value
- With Square Handheld, you can accept payments, take tableside orders, or scan barcodes anywhere. With a slim design and comfortable grip, the POS is easy to carry in your palm or pocket. Square Handheld is designed to withstand water splashes and dust. Add an optional protective case for accidental drops. A long-lasting battery and offline payments let you keep selling.
- Slim, pocketable, and lightweight so you can accept payments wherever your customers are.
- Take tableside orders, bust lines, or use the built-in barcode scanner, all with one sleek device.
- A battery that can power through your shift and offline payments let you keep selling, even if your internet is down.
- Accept all major credit and debit cards and pay one simple rate with no hidden fees and no long-term contracts required.
Recurring billing failures
Subscriptions need handling for expired cards, updated credentials, insufficient funds, authentication requests, retry schedules, cancellations, pauses, duplicate invoices, failed webhooks, and regional payment rules.
Provider lock-in
Stored payment tokens, subscription objects, fraud rules, webhook formats, and payout reports may be proprietary. Before switching, check whether tokens can be migrated or whether customers must enter payment details again.
How to choose a payment gateway
- Match the business model. A simple store, subscription service, marketplace, nonprofit, high-risk business, and omnichannel retailer have different requirements. Marketplaces may need seller onboarding, split payments, and payouts.
- Confirm geography. Check merchant-country eligibility, customer countries, settlement currencies, local methods, local acquiring, cross-border fees, tax, and regulatory requirements.
- List the methods customers actually use. Compare cards, wallets, ACH or bank debit, buy-now-pay-later, local wallets, bank transfers, and card-present acceptance.
- Choose the integration level. Payment links and hosted checkout minimize development; embedded components balance control and effort; APIs provide flexibility at the highest engineering and operational cost.
- Model total cost. Include percentage, fixed, international, conversion, refund, dispute, payout, recurring, platform, engineering, and maintenance costs.
- Review security and compliance. Check PCI DSS service-provider status, tokenization, hosted fields, 3-D Secure, fraud tools, webhook signing, role-based access, audit logs, and retention controls.
- Test operations. Investigate uptime, status transparency, webhook reliability, payout timing, account-review procedures, reserve policies, support, exports, and dispute workflows.
- Assess portability and scale. Ask about token migration, data exports, negotiated pricing, local methods, and whether the provider can support future volume and channels.
Examples of payment gateway providers
| Provider | Often suited to | Important qualification |
|---|---|---|
| Stripe | Developers, startups, SaaS, subscriptions, marketplaces, APIs, Checkout, and Payment Links. Product information: Stripe payments and Stripe Checkout. | May be less suitable for a purely no-code business or a market where a required local method is unavailable. Public rates are not universal quotes. |
| PayPal | Businesses whose customers prefer PayPal or Venmo, invoicing, and familiar wallet checkout. Product information: PayPal Checkout. | Product-specific fees and less checkout control can matter for merchants optimizing customization or small-ticket economics. |
| Square | Small retailers, restaurants, service businesses, invoices, POS, and online-plus-in-person selling. Developer information: Square online payment APIs. | Rates vary by method, location, and plan; highly customized marketplaces and broad international coverage may require another architecture. |
| Adyen | International or larger businesses needing local methods, acquiring, recurring, risk management, and omnichannel payments. Product information: Adyen online payments. | Its more sophisticated model may be a poor fit for a very small merchant seeking the simplest flat-rate onboarding. |
Alternatives to a conventional gateway
- Standalone gateway plus merchant account: More control over pricing and infrastructure, but more contracts, integrations, reconciliation, and responsibility.
- Full-stack payment service provider: Faster deployment and one vendor, in exchange for possible lock-in and less transparent underlying pricing.
- Digital-wallet checkout: Familiar, low-entry payment for customers, but with account or device dependencies and potentially different fees.
- ACH or bank transfer: Useful for larger or recurring business payments, with different settlement timing and return risks from cards.
- Buy-now-pay-later: May improve affordability and conversion, but adds method fees, eligibility limits, refund complexity, and customer-credit considerations.
- Payment orchestration: Connects multiple processors or gateways for routing and resilience, but adds another architectural and vendor layer.
Frequently Asked Questions
Do I need a separate merchant account?
Not always. A traditional setup uses a separate merchant account, while an aggregated payment service provider may provide a bundled arrangement. Confirm the provider’s structure, payout terms, and underwriting requirements.
Is PayPal or Stripe a payment gateway?
Both offer gateway functionality, but each also bundles other services such as processing, payment methods, risk tools, billing, and payouts. Calling either only a gateway leaves out much of the product.
How long does settlement take?
There is no universal timeframe. Settlement and payout depend on provider schedules, country, payment method, risk review, account history, weekends, and reserves. Authorization alone does not mean funds are already in your bank account.
What happens after a payment is declined?
Keep the customer’s cart, provide a non-revealing explanation, offer another payment method, and avoid automatic repeated retries. Diagnose the provider’s decline code and confirm the final state server-side.
Can one gateway support online and in-person payments?
Some omnichannel providers support both gateways and physical terminals. Availability of shared reporting, tokens, methods, and countries varies by provider and product.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
