Why Gateway Selection Is a Business Decision, Not a Technical One

Most store owners treat WooCommerce payment gateway criteria as a checkbox exercise: pick Stripe, enter the API keys, move on. That works fine until transaction volume grows, a chargeback dispute surfaces, or a customer in Germany hits an unsupported payment method and abandons at checkout. The gateway choice has compounding consequences — fees accumulate over thousands of orders, and a poor checkout experience quietly erodes conversion rates month after month.

This guide breaks down every meaningful criterion you should evaluate before committing to a gateway — and explains why the criteria vary depending on your store’s geography, product type, and transaction volume.

The Eight Criteria That Actually Matter

1. Transaction Fees and Fee Structure

The headline rate — typically around 2.9% + $0.30 for US cards — is only one part of the real cost. You also need to account for:

• Monthly platform fees: Authorize.net charges around $25/month in addition to per-transaction fees. At low volume, this makes it more expensive than Stripe even if the per-transaction rate is similar.
• Cross-border surcharges: Stripe adds 1.5% for international cards, which matters immediately for stores selling across borders.
• Currency conversion fees: Some gateways convert at unfavorable rates and pocket the spread.
• Chargeback fees: These typically run $15–$25 per dispute, win or lose, and they add up fast in sectors with higher dispute rates.

A useful exercise: project your expected monthly order volume and average order value, then calculate total gateway cost for each option you’re considering. A gateway that looks 0.3% cheaper may cost more in monthly fees at lower volumes — and vice versa at scale.

2. Geographic and Currency Coverage

A gateway that works perfectly in the US may create real friction for a store selling into Europe or Southeast Asia. Before selecting, answer three questions:

1. Which countries are your top three markets by revenue?
2. What local payment methods do customers in those markets expect?
3. Does the gateway support payouts in your local currency without forced conversion?

Mollie, for example, supports iDEAL (dominant in the Netherlands), Bancontact (Belgium), and SOFORT — none of which are available through WooPayments or Square. If you’re building a store for a European client, that gap matters. Payment gateways are not geographically neutral products.

3. Digital Wallet and Alternative Payment Method Support

Apple Pay and Google Pay are not standalone plugins — they ride on top of a gateway that supports the Payment Request API. In WooCommerce, that means your gateway must explicitly enable them. Stripe, WooPayments, and Braintree all support wallet payments natively. PayPal supports its own wallet but has limited Apple Pay integration depending on region.

Why this matters from a conversion standpoint: digital wallets reduce checkout friction significantly on mobile, where many stores now see 60–70% of traffic. A checkout that requires manual card entry where competitors offer one-tap Apple Pay will lose those customers quietly — it rarely shows up as an obvious problem, but it shows up in the data.

4. Subscription and Recurring Payment Support

Not all gateways tokenize cards in a way that WooCommerce Subscriptions can use for future charges. If your store sells subscription products, memberships, or installment payment plans, you need a gateway that supports stored payment methods and off-session charging — meaning it can charge a customer’s card without them being present in the browser.

Stripe handles this well and is generally considered the standard for subscription-ready WooCommerce stores. PayPal’s reference transaction system works but requires a business account with specific settings enabled. Square’s recurring support is limited in WooCommerce context. Always test this specific flow in a staging environment before going live.

5. Fraud Detection and Chargeback Handling

Built-in fraud tooling is often underweighted in gateway comparisons. Look specifically for:

• Address Verification Service (AVS): Checks that the billing address matches card issuer records.
• CVV verification: Basic but necessary.
• 3D Secure / Stripe Radar / equivalent: Rule-based risk scoring that flags suspicious orders before processing.
• Chargeback dispute tooling: Does the gateway’s dashboard make it straightforward to submit evidence? Some gateways provide almost no tooling for this.

Stripe Radar is the benchmark here — it uses machine learning trained on Stripe’s global transaction network. For stores with significant ticket sizes or high-risk product categories, this criterion alone can justify the gateway choice.

6. PCI Compliance Responsibility

Every gateway that touches cardholder data is subject to PCI DSS requirements. The key question is how much of that compliance burden falls on you versus the gateway provider.

Hosted / redirect gateways (PayPal Standard, some Authorize.net configurations) take card data entirely off your server. PCI scope is minimal — essentially a self-assessment questionnaire SAQ-A.

Direct / on-site gateways that process card data through your server dramatically expand your PCI scope. This isn’t necessarily a dealbreaker, but it adds compliance overhead and increases the cost of a security incident.

For most WooCommerce stores, choosing a gateway that uses JavaScript-based tokenization (Stripe Elements, WooPayments, Braintree.js) hits the middle ground: the card field is hosted by the gateway but appears embedded in your checkout page, keeping PCI scope low while maintaining a seamless UX.

7. Developer Ecosystem and WooCommerce Integration Quality

From a technical implementation standpoint, not all WooCommerce payment plugins are equal. Criteria worth evaluating:

• Plugin update frequency: A gateway plugin that hasn’t been updated in 12+ months is a liability. WooCommerce’s checkout blocks (introduced via the Cart and Checkout Blocks) require gateways to implement a separate compatibility layer — older plugins often don’t.
• Webhook reliability: Gateways communicate async events (payment confirmed, refund issued, dispute opened) via webhooks. Poor webhook delivery means order statuses fall out of sync.
• Logging and debugging: A gateway plugin that provides detailed logs makes troubleshooting payment failures far faster.
• Documentation quality: This matters more than it should. A gateway with thin documentation costs real hours when something breaks in production.

If you’re building WooCommerce stores for clients as an agency — or evaluating which gateways to support in your development stack — testing the plugin in a staging environment before recommending it to clients is time well spent.

8. Setup Complexity and Ongoing Maintenance Burden

Some gateways are genuinely plug-and-play. WooPayments connects in minutes through a guided onboarding flow inside WordPress. Stripe requires API key management but is straightforward. Authorize.net, by contrast, often requires merchant account setup through a separate acquiring bank, manual API credential configuration, and occasional certificate management.

For agencies managing multiple client stores, the maintenance overhead compounds. A gateway that requires manual intervention every time credentials rotate or a webhook endpoint changes is a real operational cost that rarely shows up in gateway comparison articles.

Comparison Table: Key WooCommerce Payment Gateway Criteria

The Criteria Shift Depending on Store Type

There is no universally correct gateway. The right WooCommerce payment gateway criteria depends heavily on store context. Here’s how priorities shift:

For High-Volume Stores

Fee optimization becomes the primary driver. A 0.1% difference in per-transaction rate is negligible at $5,000/month but meaningful at $500,000/month. At that scale, negotiated interchange-plus pricing (available through some gateway providers) can meaningfully reduce total cost. Fraud tooling also becomes more critical — higher volume attracts more fraud attempts, and manual review doesn’t scale.

For Subscription-First Stores

Recurring billing reliability and tokenization compatibility with WooCommerce Subscriptions are the dominant criteria. Everything else is secondary. A gateway that fails silently on renewal charges will cause involuntary churn that’s nearly impossible to recover.

For International or Multi-Currency Stores

Currency coverage, local payment method support, and cross-border fee transparency dominate. A European store using a US-centric gateway like Square will frustrate customers and leave local payment method revenue on the table.

For Agencies Managing Client Stores

Developer experience, plugin maintenance burden, and the ability to configure gateways consistently across multiple client environments matter most. Gateways with strong webhook tooling, clear logs, and reliable WooCommerce block compatibility reduce the total support overhead across a client portfolio. If you’re at the point where gateway decisions are becoming a recurring project bottleneck, it may be worth reviewing your overall development workflow — working with a technical partner like BMD Creatives can help standardize these decisions across client builds.

Frequently Asked Questions

Can I use multiple payment gateways in WooCommerce?

Yes. WooCommerce supports multiple active gateways simultaneously, and customers can choose between them at checkout. A common setup is Stripe as the primary gateway plus PayPal as an alternative for customers who prefer it. The order gateways appear in at checkout is configurable in WooCommerce settings.

Does the gateway affect checkout page speed?

It can. Gateways that load external JavaScript at checkout (which is most of them) add a dependency to the critical render path. Stripe Elements and WooPayments are generally well-optimized. Poorly maintained gateway plugins can load multiple scripts or block render. This is worth testing with a performance audit on the checkout page specifically.

What is the difference between a payment gateway and a payment processor?

A payment gateway is the interface that securely captures and transmits payment data. A payment processor is the service that actually moves funds between banks. Many modern providers (Stripe, PayPal, Square) bundle both functions, which is why the distinction is often blurred in WooCommerce discussions. Traditional setups separate them — Authorize.net is the gateway; you choose a separate processor (or bank) for settlement.

Is WooPayments the same as Stripe?

WooPayments is powered by Stripe’s infrastructure but is a distinct product. The key difference is the interface: WooPayments manages everything inside WordPress, while running Stripe directly means using both the WooCommerce plugin and the separate Stripe dashboard. Feature parity is close but not identical — some Stripe features (like certain Radar rules or advanced connect features) require using Stripe directly.

Do gateway fees apply to refunds?

This varies by gateway and has changed in recent years. Stripe no longer refunds the transaction fee when you issue a refund (as of 2022). PayPal’s policy depends on account type and region. This is a meaningful consideration for stores with higher return rates — always check the current refund fee policy directly with the gateway before finalizing your choice.

A Practical Evaluation Checklist

Before finalizing any gateway decision, run through these questions:

• What are my top three customer geographies, and does this gateway cover them with local payment methods?
• Does the gateway support Apple Pay and Google Pay natively in WooCommerce?
• If I sell subscriptions, has recurring billing been tested in a WooCommerce Subscriptions staging environment?
• What is the true total monthly cost at my expected transaction volume, including monthly fees and cross-border surcharges?
• Does the gateway plugin support WooCommerce’s Cart and Checkout Blocks?
• What fraud tooling is included, and is it sufficient for my product category?
• How does the gateway handle dispute evidence submission, and what does the chargeback fee structure look like?
• When did the WooCommerce plugin last receive an update, and how responsive is the support team?

This checklist won’t make the decision for you, but it will prevent the most common evaluation gaps that lead to gateway migrations 12 months after launch.