A WooCommerce payment gateways comparison comes down to five variables: transaction fees, supported countries, digital wallet coverage, setup complexity, and PCI compliance scope. Stripe charges 2.9% plus $0.30 on domestic United States cards, PayPal Checkout charges 3.49% plus $0.49, Square charges 2.9% plus $0.30 through its ecommerce API, and Authorize.Net adds a $25 monthly gateway fee on top of 2.9% plus $0.30. Those headline rates hide the differences that actually decide your margin. The sections below break down each variable with current 2026 pricing, then cover the operational factors that determine whether your chosen gateway actually completes orders reliably.
What Is a WooCommerce Payment Gateway?
Quick Answer:
A WooCommerce payment gateway is a service that authorizes card and wallet payments between your store, the customer’s issuing bank, and your merchant account. WooCommerce ships with offline methods only, so every store needs at least one third-party gateway to accept cards. The integration method you pick changes your compliance obligations significantly.
A WooCommerce payment gateway handles four discrete jobs during a single checkout: it encrypts the payment credential, requests authorization from the issuing bank, returns an approve or decline response, and later settles funds into your account. WooCommerce core includes direct bank transfer, check payments, and cash on delivery. None of those process cards.
Gateways integrate with WooCommerce in three ways, and the difference matters more than most comparison guides admit.
| Integration Type | How It Works | PCI Scope | Checkout Experience |
| Redirect / hosted page | Customer leaves your site to pay on the provider’s page | Smallest scope, typically SAQ A | Off-site, breaks visual continuity |
| Embedded iframe or hosted fields | Payment fields render from the provider inside your checkout | Small scope, SAQ A with conditions | On-site, provider controls the field |
| Direct API / self-hosted | Card data posts through your own server | Largest scope, SAQ A-EP or SAQ D | Fully custom, highest engineering cost |
Most stores should use hosted fields. The customer stays on your checkout page, but the card number never touches your server. That combination keeps conversion high and audit scope low.
Gateway choice also affects site architecture. Each gateway loads its own JavaScript, opens its own outbound connections, and writes its own order metadata. On managed WooCommerce hosting tuned for transactional traffic, that overhead is absorbed by dedicated PHP workers and object caching. On generic shared plans, it surfaces as slow checkouts and timed-out authorizations.
This is where the hosting layer stops being background infrastructure and starts being part of your payment stack. Prestige Technologies builds WooCommerce environments around the specific demands of gateway traffic: uncached checkout routes, reserved PHP worker capacity, Redis object caching for session and cart lookups, and outbound connection handling tuned for authorization round trips. Prestige Technologies also validates the integration type you have selected against your compliance target before launch, so a store aiming for the simplest PCI questionnaire does not accidentally deploy a direct API integration that expands its audit scope.
WooCommerce Payment Gateways Comparison: Fees at a Glance
A WooCommerce payment gateways comparison of fees shows four providers clustering near 2.9% plus a fixed fee for domestic cards, with the real separation appearing in fixed fees, monthly costs, and cross-border surcharges. The table below reflects published United States rates as of August 2026.
| Gateway | Domestic Online Rate | Monthly Fee | International Card Surcharge | Currency Conversion | Dispute Fee |
| Stripe | 2.9% + $0.30 | $0 | +1.5% | +1% | $15 |
| PayPal (Checkout) | 3.49% + $0.49 | $0 | +1.5% | ~3% to 4% spread | Varies by product |
| PayPal (standard card) | 2.99% + $0.49 | $0 | +1.5% | ~3% to 4% spread | Varies by product |
| Square (ecommerce API) | 2.9% + $0.30 | $0 on Free plan | Not broadly supported | Limited | $0 |
| Square (payment links) | 3.3% + $0.30 | $0 on Free plan | Not broadly supported | Limited | $0 |
| Authorize.Net | 2.9% + $0.30 | $25 | Varies by merchant account | Varies by merchant account | $25 |
| WooPayments | 2.9% + $0.30 | $0 | +1% | +1% | $15 |
Stripe’s surcharges stack, so an international card that also needs currency conversion runs 2.9% plus 1.5% plus 1% for a total of 5.4% plus $0.30. A $100 domestic sale costs $3.20 in Stripe fees. The same sale from a European card settled into USD costs $5.70.
PayPal’s structure is more fragmented than its headline suggests. PayPal Checkout’s rate is 3.49% plus $0.49, and if the same buyer checks out as a guest with a plain card, the standard card rate of 2.99% plus $0.49 applies instead. That $0.49 fixed fee is 63% higher than Stripe’s $0.30, and on small baskets the fixed fee dominates the effective rate.
Square changed its published online pricing in 2026, which most comparison articles have not caught. Square online payments now cost 3.3% plus $0.30 on the Free plan or 2.9% plus $0.30 on Plus and Premium plans, and manually keyed transactions are 3.5% plus $0.15 across all plans. The WooCommerce integration uses the ecommerce API rate of 2.9% plus $0.30, while payment links cost 3.3% plus $0.30.
How Fixed Fees Distort Small-Basket Stores
Fixed fees distort effective rates on low average order values far more than percentage differences do. A store selling $12 items pays a materially different effective rate than a store selling $200 items, even on identical published pricing.
| Order Value | Stripe (2.9% + $0.30) | PayPal Checkout (3.49% + $0.49) | Difference |
| $10 | 5.90% | 8.39% | 2.49 points |
| $25 | 4.10% | 5.45% | 1.35 points |
| $50 | 3.50% | 4.47% | 0.97 points |
| $150 | 3.10% | 3.82% | 0.72 points |
| $500 | 2.96% | 3.59% | 0.63 points |
If your average order value sits below $30, the fixed fee is the single most important number in your WooCommerce payment gateways comparison. If it sits above $200, the percentage dominates and negotiated volume rates matter more.
Modeling a blended rate against your actual order distribution is part of the onboarding review Prestige Technologies runs for new WooCommerce clients. Rather than defaulting every store to the same provider, the Prestige Technologies team looks at average order value, international card share, refund frequency, and subscription mix, then configures the gateway combination that produces the lowest effective cost for that specific store. Merchants routinely discover their published rate and their real rate differ by 40 basis points or more once cross-border volume is counted.
Which Gateways Support Apple Pay and Google Pay
Apple Pay and Google Pay are not standalone gateways. Both are wallet layers that require an underlying processor, so wallet availability is a function of which gateway you install.
- Stripe: Apple Pay, Google Pay, and Link, all included at the standard card rate.
- WooPayments: Apple Pay and Google Pay, included at the standard card rate.
- Square: Apple Pay and Google Pay through the WooCommerce integration.
- PayPal: PayPal wallet, Venmo, and Pay Later in the United States. Apple Pay and Google Pay require the Advanced Checkout product.
- Authorize.Net: Limited wallet support, generally requiring additional configuration.
Wallet support is not a nice-to-have. Baymard research found that 10% of shoppers abandon because there are not enough payment options, and the Visa Acceptance and MRC 2025 report found 73% of merchants now accept digital wallets. Apple Pay also requires domain verification, which means uploading a verification file to a specific path on your server. Stores on restrictive hosting frequently cannot complete this step without support intervention.
Which Payment Gateway Is Best for WooCommerce?
Quick Answer:
No single gateway is best for every WooCommerce store. Stripe suits stores needing global reach and developer flexibility, PayPal captures buyers who prefer that wallet, Square fits retailers with physical locations, and Authorize.Net serves established merchants with existing merchant accounts. The right answer depends on your average order value, geography, and subscription model.
The question of which payment gateway is best for WooCommerce appears in the People Also Ask block more than any other query for this topic, and the honest answer is that it depends on four store-specific variables. The gateway profiles below map each provider to the conditions where it genuinely wins.
Stripe: Best for Global Reach and Developer Flexibility
Stripe is the strongest default choice for WooCommerce stores that sell internationally or plan to add custom payment logic. Stripe supports 195 countries, 135 or more currencies, and 100 or more payment methods through a single integration.
Strengths:
- Widest country and currency coverage of the four gateways compared here.
- Native support for Apple Pay, Google Pay, Klarna, Afterpay, and Link at standard rates.
- Deepest plugin ecosystem, meaning most WooCommerce extensions support Stripe first.
- Sandbox and test mode that mirror production behavior closely.
Trade-offs:
- Additional fees can push effective rates above 6% once international cards, currency conversion, and add-on products like Billing at 0.7% stack together.
- New accounts that scale quickly can hit reserves or holds.
- Rates vary widely by country, at 2.9% plus $0.30 in the United States, 1.5% plus £0.20 in the United Kingdom, and 1.75% plus A$0.30 in Australia.
Stripe vs PayPal for WooCommerce: Which Should You Run?
Stripe versus PayPal for WooCommerce is not usually an either-or decision, because most established stores run both. Stripe handles card processing at a lower effective rate, while PayPal captures buyers who will not enter card details on an unfamiliar site.
| Factor | Stripe | PayPal |
| Domestic rate | 2.9% + $0.30 | 3.49% + $0.49 (Checkout) |
| Effective rate on $40 order | 3.65% | 4.72% |
| Buyer trust with unknown brands | Moderate | High |
| On-site checkout | Yes, hosted fields | Partial, some flows redirect |
| Subscription handling | Native with WooCommerce Subscriptions | Supported, more constraints on plan changes |
| Account hold risk | Present | Present, more frequently reported |
Run Stripe as the primary card processor and PayPal as the secondary wallet. The incremental cost of PayPal’s higher rate applies only to the orders it captures, and those orders would frequently not convert on cards alone.
Square: Best for Stores With Physical Locations
Square is the strongest option for WooCommerce stores that also sell in person, because inventory, customer records, and reporting sync across both channels on one account. The Square integration syncs catalog, inventory, orders, and customer data automatically between WooCommerce and Square.
The trade-off is geographic. Square operates in a limited set of markets including the United States, United Kingdom, Canada, Australia, Japan, France, Ireland, and Spain. Stores selling outside those markets should not use Square as a primary gateway. Subscription support is also weaker than Stripe or WooPayments.
Authorize.Net: Best for Established Merchants With Existing Accounts
Authorize.Net is best suited to established United States businesses that already hold a merchant account and need granular fraud rules. Authorize.Net’s all-in-one plan charges $25 monthly plus 2.9% plus $0.30 per transaction, and its gateway-only plan also costs $25 monthly plus $0.10 per transaction with a daily batch fee, requiring a separate merchant account. Authorize.Net also charges a non-refundable $25 fee for every chargeback.
The $25 monthly fee makes Authorize.Net uneconomical below roughly $8,000 in monthly volume, where the fixed cost exceeds the savings from any negotiated rate. Above that threshold, the configurable Advanced Fraud Detection Suite filters justify the cost for merchants with elevated chargeback exposure.
WooPayments: Best for Fastest Setup
WooPayments is the fastest gateway to configure because it requires no separate merchant signup and no API keys. It runs on Stripe infrastructure and mirrors Stripe’s base rates at 2.9% plus $0.30 for domestic United States cards. WooPayments now supports roughly 38 or more countries, including major European Union markets such as France, Germany, and Italy.
The constraint is flexibility. Stores that later need custom Stripe logic, Radar rule tuning, or Connect-style payouts typically migrate to standalone Stripe, and that migration means re-tokenizing saved cards.
Whichever gateway you select, the configuration work sits at the server level as much as the plugin level. Prestige Technologies handles gateway installation, API credential management, webhook verification, and sandbox testing during onboarding, so stores go live with payments already validated rather than debugging declines after launch.
Does WooCommerce Have Its Own Payment Gateway?
Quick Answer:
Yes. WooCommerce offers WooPayments, its native gateway built on Stripe infrastructure and managed entirely from the WordPress dashboard. WooCommerce core also ships with offline methods including direct bank transfer, check payments, and cash on delivery, but none of those process card payments. Understanding the distinction changes which setup path you should take.
WooCommerce’s own gateway is WooPayments. It handles payouts, refunds, and disputes inside WooCommerce rather than in a separate provider dashboard. Because it sits on Stripe rails, its processing behavior and fee structure closely track Stripe’s.
The offline methods bundled with WooCommerce core serve different purposes:
- Direct bank transfer (BACS): Customer transfers funds manually. Order stays on hold until you confirm receipt. Common for B2B and wholesale.
- Check payments: Customer mails a check. Requires manual order status changes.
- Cash on delivery: Payment collected at handover. Common for local delivery and regional markets.
None of these authorize cards, and all three require manual reconciliation. Treat them as supplements to a real gateway, not replacements.
Stores that genuinely need offline methods, such as wholesale operations invoicing on net terms, usually run them alongside a card gateway with role-based visibility rules. Prestige Technologies configures that split during WooCommerce onboarding so retail customers see card and wallet options while approved trade accounts see bank transfer and purchase order methods, without exposing offline payment routes to the general public. The full catalog of supported providers is published in the WooCommerce payment gateway extension directory.
How Do WooCommerce Payment Gateway Fees Actually Work?
Quick Answer:
WooCommerce payment gateway fees combine a percentage of the transaction with a fixed per-transaction charge, then add surcharges for international cards, currency conversion, disputes, and optional services. WooCommerce itself takes zero commission. The published headline rate typically accounts for only part of what a store actually pays each month.
WooCommerce charges no transaction fee and takes no revenue share. Every fee you see originates from the gateway. Your total processing cost is built from six layers.
- Base percentage. Applied to the full transaction amount including tax and shipping.
- Fixed per-transaction fee. Flat regardless of order size, which is why low average order values carry high effective rates.
- Cross-border surcharge. Triggered by the card’s issuing country, not the customer’s shipping address.
- Currency conversion margin. Applied when the charge currency differs from your settlement currency.
- Dispute and chargeback fees. Often non-refundable even when you win the dispute.
- Optional product fees. Subscription billing, tax calculation, and fraud tooling are billed separately.
The Cross-Border Fee Most Stores Miss
Cross-border surcharges apply based on where the card was issued, which catches stores that believe they only sell domestically. A United States store shipping only within the United States still pays the international surcharge when a visiting customer pays with a foreign-issued card.
Stripe’s international card surcharge of 1.5% applies whenever a customer’s card is issued in a different country from your Stripe account, even if both parties use USD. Currency conversion is separate. Stripe adds 1% when the payment currency does not match your settlement currency, which can trigger even on a domestic card if you charge in a different currency.
For stores with meaningful international traffic, model your blended rate rather than the domestic rate. A store with 25% international card volume on Stripe pays an effective blended rate near 3.3%, not 2.9%.
Subscription and Recurring Billing Costs
Subscription stores carry costs that single-purchase stores never encounter. Using Stripe Billing for subscriptions adds a flat 0.7% on top of the base rate. Failed recurring charges also create silent revenue loss when dunning is not configured, since a card that expires simply stops paying.
If subscriptions represent a material share of revenue, evaluate gateways on renewal success rate rather than headline processing cost. Card account updater services, automatic retries, and dunning schedules recover more revenue than a 0.2% rate difference.
Recurring billing also raises the stakes on server reliability, because a failed renewal is not retried by the customer the way an abandoned checkout might be. Prestige Technologies provisions subscription-heavy WooCommerce stores with scheduled task handling that runs on real system cron rather than WordPress pseudo-cron, which is a common and largely invisible cause of renewals that never fire on low-traffic stores.
PCI Compliance Considerations for WooCommerce Stores
PCI compliance considerations for WooCommerce stores changed materially on March 31, 2025, when PCI DSS version 4.0.1 requirements became mandatory and the Self-Assessment Questionnaire A eligibility criteria were rewritten. Most WooCommerce comparison articles still describe the pre-2025 rules.
The PCI Security Standards Council removed Requirements 6.4.3 and 11.6.1 for payment page security and Requirement 12.3.1 from SAQ A, and added an eligibility criterion requiring merchants to confirm their site is not susceptible to attacks from scripts that could affect their ecommerce systems. Removing the requirements did not remove the obligation, and a merchant who cannot make that confirmation is not eligible for SAQ A at all and must validate against SAQ A-EP, which carries a far larger requirement set.
What This Means for Your Gateway Choice
Your gateway integration type determines which questionnaire applies to your store.
| Scenario | Likely SAQ | Practical Obligation |
| Full redirect to provider’s hosted page | SAQ A | Confirm site is not susceptible to script attacks |
| Provider-hosted iframe or fields, correctly implemented | SAQ A | Confirm implementation matches vendor instructions exactly |
| Custom checkout that influences payment transmission | SAQ A-EP | Full script inventory, integrity checks, weekly monitoring |
| Card data touching your server | SAQ D | Full PCI DSS requirement set |
Requirement 6.4.3 demands an authorized inventory of every script on your payment page plus a business justification and integrity check for each one, while Requirement 11.6.1 demands weekly monitoring of HTTP headers and script changes with an alert path when something is modified without approval.
The practical trap for WooCommerce stores is script sprawl. Analytics tags, heatmap tools, chat widgets, and retargeting pixels loading on the checkout page all count. A store running eleven third-party scripts on checkout cannot casually assert that its site is not susceptible to script-based attacks.
FAQ 1588, published by the PCI Security Standards Council on February 28, 2025, clarifies how merchants can meet the new SAQ A eligibility criterion. Full details are published in the PCI Security Standards Council announcement and the accompanying SAQ A eligibility FAQ.
Server-Side Controls That Support SAQ A Eligibility
Several of the controls that support the eligibility confirmation live at the hosting layer rather than in a plugin:
- A web application firewall that blocks script injection attempts before they reach WordPress.
- File integrity monitoring that alerts on unauthorized changes to theme and plugin files.
- Content Security Policy headers restricting which origins may execute scripts on checkout.
- Malware scanning tuned for WordPress-specific injection patterns.
- Access controls limiting who can modify checkout templates.
Prestige Technologies provisions WAF rules, file integrity monitoring, and header configuration as part of standard WooCommerce hosting setup. That reduces the number of controls a merchant has to build independently in order to make the SAQ A confirmation defensibly.
Prestige Technologies also documents the checkout script inventory during onboarding, recording every third-party tag loading on the payment page along with its business justification. That document is the artifact most merchants lack when an acquirer asks how they satisfied the eligibility criterion. Because Prestige Technologies manages both the hosting layer and the WooCommerce configuration, script changes introduced by a new plugin or marketing tag are caught at the server level rather than surfacing during an annual assessment.
How to Set Up a Payment Gateway in WooCommerce
Setting up a payment gateway in WooCommerce requires installing the gateway extension, connecting your merchant account, configuring checkout display, verifying webhooks, and completing sandbox transactions before enabling live mode. The full process takes 30 to 90 minutes depending on the gateway.
- Confirm SSL is active across the entire site. Every page must serve over HTTPS, not just checkout. Mixed content warnings block wallet buttons from rendering.
- Create the merchant account first. Sign up with the provider and complete identity and bank verification before touching WordPress. Underwriting can take 24 to 72 hours for some providers.
- Install the official gateway extension. Use the provider’s official WooCommerce extension rather than a third-party alternative. Official extensions receive security patches faster and match the provider’s current API version.
- Connect the account or paste API credentials. Stripe, WooPayments, and PayPal use guided OAuth-style connection flows. Authorize.Net requires copying an API Login ID and Transaction Key from the merchant dashboard.
- Configure the customer-facing settings. Set the method title shown at checkout, the description text, the payment capture behavior (authorize only versus authorize and capture), and the order in which methods display.
- Register and verify the webhook endpoint. The gateway posts asynchronous events such as successful charges and refunds to a WooCommerce endpoint. If the endpoint is blocked, cached, or rate limited, orders remain stuck on pending payment even though funds were captured.
- Complete Apple Pay domain verification if applicable. Upload the provider’s verification file to the required path and confirm the provider can retrieve it.
- Run sandbox transactions covering four scenarios. Test a successful charge, a declined card, a partial refund, and a full refund. Confirm each produces the correct WooCommerce order status and triggers the correct email.
- Switch to live mode and place one real low-value order. Confirm the funds appear in the provider dashboard, the order status updates automatically, and the receipt email sends.
- Document your script inventory for checkout. Record every third-party script loading on the checkout page with a business justification, which supports your PCI validation position.
Step 6 causes more production incidents than any other. Webhook delivery depends on server configuration, and aggressive page caching or overly restrictive firewall rules silently drop the callbacks that mark orders as paid.
Every step in this sequence is included in Prestige Technologies onboarding. The Prestige Technologies team installs the gateway extension, manages API credentials, registers and confirms the webhook endpoint against live provider logs, completes wallet domain verification, and runs the full sandbox matrix covering successful charges, declines, partial refunds, and full refunds. Stores launch with a verified payment path rather than discovering a dropped webhook after the first real customer order fails to confirm.
How Does Hosting Affect Payment Gateway Reliability?
Quick Answer:
Hosting affects payment gateway reliability through webhook delivery, PHP execution timeouts, outbound connection handling, and checkout concurrency. Gateway authorizations frequently fail for server reasons rather than gateway reasons. Stores that switch gateways to fix intermittent payment failures often find the problem persists because the underlying cause was infrastructure.
Payment gateways are network-dependent processes running inside a PHP request. Four server-level factors determine whether that process completes.
Webhooks, Timeouts, and Stuck Orders
Webhook delivery failures are the most common cause of WooCommerce orders stuck in pending payment status. The gateway captures the funds, posts a confirmation event to your store, and if that request is dropped, WooCommerce never updates the order.
Common server-side causes:
- Aggressive full-page caching serving a cached response to the webhook endpoint instead of executing PHP.
- Firewall rules blocking the provider’s IP ranges as unrecognized traffic.
- PHP max_execution_time set too low, killing the request mid-processing.
- Rate limiting rejecting bursts of webhook events during a traffic spike.
PHP Workers and Checkout Concurrency
Checkout requests cannot be cached, because each one is unique to a session. Every concurrent checkout consumes a PHP worker for the full duration of the gateway round trip, which typically runs 800 milliseconds to 3 seconds.
A store with 4 PHP workers can process roughly 4 simultaneous checkouts. During a flash sale or email send, the fifth shopper queues. If the queue exceeds the timeout, the request fails after the card was already authorized, producing the worst possible outcome: a charged customer with no order.
This is a capacity planning problem, not a gateway problem. Hosting plans sized for transactional workloads allocate enough workers to absorb concurrent checkout load, and pair them with object caching so cart and session lookups do not consume worker time on repeated database queries.
Outbound Connection Handling
Every gateway authorization requires an outbound HTTPS request from your server to the provider. Shared environments that throttle outbound connections, enforce short DNS cache times, or route through congested network paths add latency to every single transaction.
On a store processing 500 orders daily, an extra 400 milliseconds per authorization is not a rounding error. It is a measurable increase in timeout-related declines.
Prestige Technologies runs WooCommerce workloads on NVMe storage with tuned PHP-FPM pools and Redis object caching, which keeps authorization round trips inside the window gateways expect. Cart, checkout, and account routes are excluded from full-page caching by default, and webhook endpoints are whitelisted at the firewall so provider callbacks are never mistaken for anomalous traffic. Worker allocation is sized against expected concurrent checkout load rather than average traffic, which matters most during the promotional spikes when payment failures are most expensive. When a store outgrows its allocation, Prestige Technologies scales worker capacity without requiring a platform migration or a gateway change.
Common WooCommerce Payment Gateway Problems
Common WooCommerce payment gateway problems cluster into five categories: stuck pending orders, checkout errors after plugin updates, unexpected declines on legitimate cards, missing wallet buttons, and duplicate charges. Each has a diagnostic path that starts with logs rather than settings.
Why Are My WooCommerce Orders Stuck on Pending Payment?
Orders stuck on pending payment almost always indicate a webhook that never arrived or never executed. Check the provider dashboard first. If the charge succeeded there but the WooCommerce order still reads pending, the payment worked and the callback failed.
Diagnostic sequence:
- Confirm the charge status in the provider dashboard.
- Check the provider’s webhook delivery log for failed attempts and HTTP response codes.
- Verify the webhook URL is excluded from page caching.
- Confirm the firewall is not blocking the provider’s published IP ranges.
- Review WooCommerce logs under WooCommerce, then Status, then Logs.
Why Do Wallet Buttons Disappear?
Apple Pay and Google Pay buttons fail to render for three reasons: incomplete domain verification, mixed content on the checkout page, or a JavaScript error thrown by an unrelated plugin before the wallet script initializes. Browser console errors identify which one applies within seconds.
Why Did Checkout Break After an Update?
Gateway extensions track provider API versions, and provider APIs deprecate on a schedule. An extension that has not been updated in eight months may be calling a deprecated endpoint. Conversely, updating a gateway extension without testing can break a customized checkout template.
Both failure modes are preventable with a staging environment. Test every gateway extension update against real checkout flows before deploying to production. Stores on managed WordPress hosting with one-click staging can validate a gateway update in minutes instead of discovering the breakage through customer complaints.
Order confirmation emails are a related failure point. Gateways trigger WooCommerce emails, and if those emails land in spam or fail SPF and DKIM checks, customers assume the order did not process and contact support or file a dispute. Authenticated professional business email on your own domain measurably improves transactional deliverability.
How Do You Choose a Payment Gateway for Your Store?
Quick Answer:
Choosing a WooCommerce payment gateway means matching four store variables to provider capabilities: average order value against fixed fees, customer geography against country support, business model against subscription handling, and technical capacity against setup complexity. Ranking these in order of impact for your specific store produces a clear answer faster than feature comparison.
Work through the four variables in sequence. Each one eliminates options.
- Average order value. Below $30, prioritize the lowest fixed fee. Above $200, prioritize percentage rate and negotiated volume pricing.
- Customer geography. Confirm the gateway supports every country where you expect card issuance, not just where you ship.
- Business model. Subscriptions, pre-orders, and deposits require gateways with strong recurring billing and card updater support.
- Technical capacity. If nobody on your team can debug an API integration, weight setup simplicity heavily.
Technical capacity is the variable most stores can outsource rather than optimize around. Prestige Technologies pairs WooCommerce hosting with hands-on development support, which means setup complexity stops being a selection criterion. Merchants can choose the gateway with the best economics for their order profile instead of the one that happens to be easiest to install, and Prestige Technologies handles the credential management, webhook configuration, and testing that would otherwise push a store toward a simpler but more expensive provider.
WooCommerce Payment Gateways Comparison by Store Type
A WooCommerce payment gateways comparison by store type produces clearer recommendations than a general ranking, because the same gateway can be the best and worst choice depending on context.
| Store Type | Primary Gateway | Secondary | Rationale |
| New store, domestic only | WooPayments | PayPal | Fastest setup, no separate merchant account |
| Growing store, international | Stripe | PayPal | Widest country and currency coverage |
| Low AOV, high volume | Stripe | None | Lowest fixed fee compounds across order count |
| Subscription or membership | Stripe | None | Strongest recurring billing and card updater |
| Retail with physical location | Square | Stripe | Unified inventory and customer records |
| Established high volume US | Authorize.Net | Stripe | Fraud rule granularity, existing merchant account |
| B2B or wholesale | Authorize.Net | Bank transfer | eCheck support and invoice-style terms |
Should You Run More Than One Gateway?
Running two gateways is the standard configuration for stores past roughly $20,000 in monthly revenue. The second gateway serves two functions: it captures buyers who prefer a specific payment method, and it provides failover if the primary provider has an outage or freezes the account.
The cost of a second gateway is not the fee difference. It is reconciliation complexity, since refunds, disputes, and payouts now arrive through two systems. Keep the count at two unless a specific market requires a local method. Worldpay reported that global ecommerce spend surpassed $6.8 trillion in 2024, with smartphones accounting for 57% of that spend, and regional wallet preferences vary enough that international stores sometimes need a third local option.
Every additional gateway also adds scripts to your checkout page, which enlarges your PCI script inventory and your page weight. Three gateways is usually where the operational cost begins to exceed the conversion benefit. Regional payment preference data is published in Worldpay’s regional payment method distribution, and current Stripe rates are maintained on the official Stripe pricing page.
Checkout conversion research supports offering more than one method. Baymard Institute has tracked the global average cart abandonment rate for 14 years and it currently sits at 70.19%, with payment friction a recurring contributor. The full methodology is published in Baymard’s checkout usability research.
Conclusion
A useful WooCommerce payment gateways comparison ends with a decision, not a feature list. Stripe wins on international reach and low fixed fees. PayPal wins on buyer trust and belongs alongside a card processor rather than replacing one. Square wins when a physical location shares inventory with the store. Authorize.Net wins above roughly $8,000 monthly volume where fraud rule granularity justifies the $25 monthly fee. WooPayments wins on setup speed for domestic stores that want one dashboard.
The variable most stores underweight is infrastructure. Gateways fail for server reasons far more often than for gateway reasons, and no amount of provider switching fixes a dropped webhook or an exhausted PHP worker pool.
Prestige Technologies configures your preferred payment gateways during onboarding, including extension installation, API credential setup, webhook verification, wallet domain validation, and full sandbox testing across success, decline, and refund paths. Your store goes live with payments already proven rather than debugging authorization failures against real customers. Explore WooCommerce hosting with payment gateway setup included, or browse more WooCommerce performance and security guides to plan your build.
Frequently Asked Questions
Q: Which payment gateway is best for WooCommerce?
No single gateway is best for every store. Stripe suits international stores and low average order values because of its lower fixed fee. PayPal suits stores needing buyer trust from an established wallet. Square suits merchants with physical locations. The best choice depends on your average order value, customer geography, and whether you sell subscriptions.
Q: Does WooCommerce have its own payment gateway?
Yes. WooPayments is the native gateway, built on Stripe infrastructure and managed entirely inside the WordPress dashboard. It handles payouts, refunds, and disputes without a separate provider login. WooCommerce core also includes direct bank transfer, check payments, and cash on delivery, but those offline methods cannot process card payments and require manual reconciliation.
Q: Can I use Stripe as a payment gateway for WooCommerce?
Yes. Stripe integrates with WooCommerce through an official extension that supports cards, Apple Pay, Google Pay, Link, and buy now pay later methods. Setup requires creating a Stripe account, connecting it to WooCommerce, and registering a webhook endpoint. Stripe also powers the native WooCommerce gateway, so both options run on the same underlying infrastructure.
Q: Is WooCommerce a monthly fee?
No. WooCommerce core is free and charges no transaction fee or revenue share. Costs come from hosting, premium extensions, themes, and payment processing fees charged by your gateway. A production store typically spends on hosting monthly plus roughly 2.9% plus a fixed fee per transaction, depending on which payment provider you select.
Q: Is Stripe or PayPal cheaper for a WooCommerce store?
Stripe is cheaper for most card transactions. Stripe charges 2.9% plus $0.30 domestically in the United States, while PayPal Checkout charges 3.49% plus $0.49. On a $50 order that is $1.75 versus $2.24. The gap widens on smaller orders because PayPal’s fixed fee is 63 percent higher than Stripe’s.
Q: Can I use multiple payment gateways in WooCommerce at the same time?
Yes. WooCommerce displays every enabled gateway at checkout and remembers which one each customer selects. Running two gateways is standard practice above roughly $20,000 monthly revenue, providing both customer choice and failover if one provider has an outage. The trade-off is reconciliation complexity, since payouts and disputes arrive through separate systems.
Q: How many payment gateways should a WooCommerce store offer?
Two gateways suits most stores: one card processor and one wallet. A third is justified only when a specific market requires a local payment method. Each additional gateway adds scripts to your checkout page, increasing page weight and enlarging your compliance script inventory. Beyond three, operational overhead usually exceeds the incremental conversion benefit.
Q: What is the difference between a payment gateway and a payment processor?
A payment gateway captures and transmits payment credentials securely from checkout to the processing network. A payment processor moves funds between the issuing bank and the acquiring bank. Many modern providers perform both functions, which is why the terms are used interchangeably. Traditional gateways require a separate merchant account from an acquiring bank.
Q: Do I need PCI compliance if I use Stripe or PayPal on WooCommerce?
Yes. Using a third-party provider reduces your compliance scope but does not eliminate it. Since March 31, 2025, merchants validating with the simplest questionnaire must confirm their site is not susceptible to script-based attacks. Stores unable to make that confirmation must validate against a substantially larger requirement set instead.
Q: Why do my WooCommerce orders get stuck on pending payment?
Stuck pending orders almost always mean a webhook never arrived or never executed. The gateway captured the funds but the confirmation callback failed to update WooCommerce. Common causes include page caching serving the webhook endpoint, firewall rules blocking provider IP ranges, low PHP execution timeouts, and rate limiting during traffic spikes.
Q: Which WooCommerce payment gateways support Apple Pay and Google Pay?
Stripe, WooPayments, and Square all support Apple Pay and Google Pay at standard card rates through their official WooCommerce extensions. PayPal requires its Advanced Checkout product for those wallets. Apple Pay additionally requires domain verification, which means uploading a verification file to a specific server path that your host must permit.
Q: What does Authorize.Net cost for a WooCommerce store?
Authorize.Net charges a $25 monthly gateway fee plus 2.9% plus $0.30 per transaction on its all-in-one plan. A gateway-only plan also costs $25 monthly plus a per-transaction charge and a daily batch fee, but requires a separate merchant account. Chargebacks carry a non-refundable $25 fee, higher than most competing providers charge.
Q: Which WooCommerce payment gateway is best for subscriptions?
Stripe generally handles WooCommerce subscriptions best, with native recurring billing, automatic card updater services, and configurable retry logic for failed renewals. Evaluate subscription gateways on renewal success rate rather than headline processing rate, since recovered failed payments typically outweigh small differences in per-transaction cost across a subscriber base.
Q: Do WooCommerce payment gateways work in every country?
No. Coverage varies significantly. Stripe supports 195 countries and 135 or more currencies. The native WooCommerce gateway supports roughly 38 or more countries. Square operates in a limited set including the United States, United Kingdom, Canada, Australia, Japan, France, Ireland, and Spain. Always confirm coverage for card issuance countries, not just shipping destinations.
Q: How much do WooCommerce payment gateways charge for international cards?
Most providers add a cross-border surcharge of roughly 1 to 1.5 percent when the card is issued outside your account country. Currency conversion is charged separately, typically around 1 percent for card processors and a wider spread for wallet providers. Surcharges stack, so an international card requiring conversion can exceed 5 percent total.
Q: Can I switch WooCommerce payment gateways without losing subscription customers?
Switching gateways breaks existing subscription tokens because saved card credentials are stored by the provider, not by WooCommerce. Some providers support tokenized card migration on request, which preserves active subscriptions. Without migration, subscribers must re-enter payment details. Plan any gateway change with a migration request and a customer communication sequence.
Q: Does adding more payment gateways slow down WooCommerce checkout?
Yes. Each gateway loads its own JavaScript, stylesheets, and outbound connections on the checkout page. Three or more gateways measurably increase page weight and time to interactive. Checkout pages also cannot be cached, so every concurrent session consumes a PHP worker for the full gateway round trip, making server capacity a limiting factor.
Q: What is the cheapest way to accept payments on WooCommerce?
Bank transfer costs nothing in processing fees but requires manual reconciliation and delays fulfillment. Among card processors, the cheapest option depends on order size. Below $30 average order value, the lowest fixed fee wins. Above $200, the lowest percentage wins. Bank debit methods where available typically cost under 1 percent.
Q: Which is the fastest payment gateway for WooCommerce checkout?
Speed depends more on server configuration than on provider choice, since all major gateways complete authorization within roughly one to three seconds. Digital wallets are fastest from the shopper’s perspective because they eliminate manual card entry. Server factors including PHP worker availability, outbound connection latency, and object caching affect perceived speed most.
Q: What are the best online payment gateways for small businesses?
Small businesses generally benefit most from providers with no monthly fee and simple onboarding. Options charging only per-transaction fees avoid fixed costs during low-volume months. Prioritize gateways offering digital wallets at standard rates, transparent published pricing, and guided setup that does not require developer involvement to configure correctly.