Why Most Gateway Comparisons Miss the Point

Search for WooCommerce payment gateway criteria and you will find dozens of posts ranking gateways by transaction fees or listing which ones support PayPal. That is useful up to a point — but it skips the harder questions that determine whether a gateway will actually work for your specific store, at your volume, with your product type, in your target markets.

The criteria that matter most depend entirely on context: a subscription box company has fundamentally different requirements than a B2B wholesale store or a digital downloads shop. This guide breaks down the real evaluation framework — the one that holds up once your store is live and processing real orders.

Start With Business Model Fit, Not Fee Tables

The first filter should not be «which gateway is cheapest» but «which gateways can actually support how this store operates.» Three business model dimensions drive this:

Transaction Type: One-Time vs. Recurring

If you sell subscriptions, recurring billing capability is non-negotiable. Not every gateway that claims subscription support handles it the same way. Some require tokenization — storing a card token server-side so future charges can be processed without the customer re-entering details. Others rely on the gateway’s own recurring billing engine, which may conflict with how WooCommerce Subscriptions or Sumo Subscriptions manages billing cycles.

Before committing to any gateway for a subscription store, verify that it supports payment tokenization natively and that the WooCommerce Subscriptions documentation lists it as a compatible gateway with automatic renewal support. Partial support exists for many gateways — they process the first payment but fall back to manual renewal for subsequent charges. That is a conversion and retention disaster.

Average Order Value and Chargeback Risk

High-ticket or high-risk product categories (electronics, supplements, digital goods) attract higher chargeback rates. Some gateways — Stripe in particular — have strict policies around chargeback thresholds and can hold or terminate accounts with limited notice. If your store operates in a sensitive category, you need to evaluate whether a gateway explicitly supports your vertical or has industry-specific terms that protect you during disputes.

B2B vs. B2C Checkout Flows

B2B stores often need invoice-based payment, net terms, or purchase order workflows. Standard consumer gateways are not designed for this. If your store serves wholesale buyers, evaluate gateways that integrate with B2B invoicing or support delayed capture — where authorization happens at order time but the charge is captured later when the invoice is approved.

Technical Integration Criteria That Agencies Overlook

Beyond business model fit, there are technical criteria that directly affect build complexity, maintenance burden, and long-term reliability. These are the ones that matter when you are responsible for the store’s architecture rather than just picking a plugin.

Redirect vs. Embedded vs. On-Site Processing

Payment gateways fall into three integration patterns, and each has real tradeoffs:

• Redirect gateways send the customer off-site to complete payment (classic PayPal). Simple to implement, lower PCI scope, but you lose control of the checkout experience and conversion often drops.
• Embedded/hosted fields (Stripe Elements, Braintree Drop-in UI) render the payment form inline using iframes. The card data never touches your server, PCI scope stays limited, and the UX stays on-site. This is the dominant pattern for high-conversion stores.
• On-site direct processing routes card data through your server before passing it to the gateway. Maximum UX control, but full PCI DSS compliance is required — including quarterly scans and annual audits. Most stores should avoid this unless there is a specific technical reason.

The integration pattern affects not just UX but your PCI DSS compliance scope significantly. Embedded hosted fields keep you at SAQ-A level — the lightest compliance requirement. On-site processing can push you to SAQ-D, which requires considerably more infrastructure and documentation.

WooCommerce Plugin Quality and Maintenance

Every gateway needs a WooCommerce plugin to connect. The quality of that plugin matters more than most store owners realize. Evaluate:

• Active installs and update frequency: A plugin with 100,000+ active installs and updates every few weeks is less likely to break on a WooCommerce major version upgrade than one with 2,000 installs and no update in 14 months.
• Who maintains it: First-party plugins (maintained by the gateway company itself, like Stripe’s official plugin) are more reliable than community forks or third-party bridges.
• Hook coverage: Does the plugin use WooCommerce’s payment gateway API properly? Poorly built plugins bypass standard hooks and break with theme customizations or checkout plugins.

Webhook Reliability and Order Status Accuracy

A gateway that processes payments correctly but sends unreliable webhooks creates operational chaos. If the payment confirmation webhook fails or arrives with a delay, orders stay in «pending» status, fulfillment is blocked, and customer support costs spike. When evaluating gateways, look for documentation on their webhook retry logic — how many times they retry on failure, and over what time window. Stripe’s webhook system retries up to 72 hours with exponential backoff. Not all gateways are this robust.

Geographic and Currency Criteria

This is where many gateway evaluations are too optimistic. A gateway may list 50 supported countries but have meaningful restrictions that only appear in the fine print.

Merchant Country vs. Customer Country

There is a difference between where the gateway lets you register as a merchant and where your customers can be located. Some gateways require the merchant account to be based in specific countries. Others have no merchant location restrictions but limit which currencies can be settled. Know both dimensions before committing.

Local Payment Methods

Card payments are not universal. In Germany, SEPA direct debit and Sofort dominate. In the Netherlands, iDEAL accounts for the majority of online transactions. In Brazil, Boleto and Pix are critical. If you are building for or targeting a specific market, verify that the gateway supports the local payment methods buyers actually use — not just Visa and Mastercard. A store targeting German buyers that only accepts cards will leave significant revenue on the table.

Multi-Currency Settlement

Accepting payments in multiple currencies is different from settling in multiple currencies. Some gateways convert everything to a single settlement currency, which means you absorb the conversion risk. If your cost base is in Euros but you sell in USD and GBP, the settlement currency arrangement can directly affect margin. Multi-currency settlement (receiving GBP directly into a GBP account) requires specific gateway and banking setup — not all gateways support it.

Fee Structure: The Honest Breakdown

Transaction fees are obvious. The less obvious costs are what create budget surprises later.

The Fee Components Most Comparisons Skip

• International card surcharges: Most gateways add 1-2% on top of their base rate when the card is issued outside your settlement country. If a significant portion of your traffic is international, this changes the effective rate substantially.
• Currency conversion fees: When a customer pays in a currency that requires conversion, gateways typically add 1-2% on top of the interbank rate.
• Dispute and chargeback fees: Stripe charges $15 per dispute. Some gateways charge more. If your product category has even moderate chargeback exposure, this compounds quickly.
• Payout fees and timelines: When does money actually reach your bank account? Standard Stripe payouts take 2-7 days in most countries. Some gateways hold funds for 7-14 days for new accounts. Cash flow impact matters for stores with high fulfillment costs.

Security Criteria Beyond PCI Compliance

PCI compliance is a baseline, not a differentiator. The security criteria that actually separate gateways in practice are:

3D Secure 2 Support

3D Secure 2 (3DS2) is required for European transactions under PSD2 Strong Customer Authentication rules. But beyond compliance, 3DS2 shifts liability for fraudulent transactions from the merchant to the card issuer when the authentication challenge is completed. For stores with meaningful EU traffic, a gateway with full 3DS2 support — including the friction-less flow that passes authentication without a popup when risk is low — is a meaningful fraud protection upgrade.

Fraud Detection Tools

Some gateways include built-in fraud scoring (Stripe Radar, Braintree’s fraud tools). Others require you to integrate a third-party service like Signifyd or Kount separately. Evaluate what comes in the box and whether the fraud tools are configurable enough for your product category’s risk profile.

Operational and Support Criteria

The final category is the one most often ignored during evaluation and most frequently regretted after go-live.

Account Stability

Stripe is excellent technology, but their support model for account holds and terminations is notoriously opaque for smaller merchants. PayPal has a long history of fund holds during high-volume periods. If your store’s cash flow is sensitive to payment delays, evaluate gateways that offer dedicated account managers or documented escalation paths — not just email support with 48-hour response windows.

Sandbox Environment Quality

Before a gateway goes live on a production store, it should be thoroughly tested in a sandbox. Not all sandbox environments accurately replicate production behavior. Specifically, test: declined card scenarios, 3DS authentication flows, webhook delivery, refund processing, and subscription renewal behavior. A sandbox that only tests happy-path successful payments is not adequate for production confidence.

Developer Documentation and API Maturity

If there is any customization needed — custom payment flows, split payments, marketplace payouts — evaluate the quality and completeness of the gateway’s API documentation. Stripe sets the industry standard here. Less mature gateways often have incomplete documentation, deprecated endpoints, and slow API versioning that creates technical debt over time.

A Practical Evaluation Framework

Rather than starting with a feature checklist, work through these questions in order:

1. What is the primary transaction type? One-time, subscription, or mixed? This filters immediately.
2. Where are merchants and customers located? This determines geographic and local payment method requirements.
3. What is the product category? High-risk categories need explicit gateway support.
4. What is the integration pattern? Redirect, embedded, or on-site — and what does that mean for PCI scope?
5. Who maintains the WooCommerce plugin? First-party vs. third-party, and what is the update cadence?
6. What is the real effective rate? Base rate plus international surcharges plus currency conversion plus dispute fees at estimated chargeback rates.
7. What does the support model look like? Especially for account holds or disputes.

If you are building WooCommerce stores for clients and need reliable technical execution on payment integrations — including custom flows, subscription setups, and multi-gateway configurations — the BMD Creatives team works as a technical partner for agencies that need senior-level WooCommerce development without the overhead of an in-house hire.

Frequently Asked Questions

Can I use multiple payment gateways on the same WooCommerce store?

Yes, and for many stores it makes sense. A typical setup might use Stripe as the primary gateway for card payments and add a local gateway (like iDEAL for Netherlands or BACS for UK bank transfers) as a secondary option. WooCommerce supports multiple active gateways simultaneously, and you can configure their display order at checkout. The complexity comes in reconciliation — you will have transactions spread across multiple dashboards and payout timelines to manage.

Does gateway choice affect checkout conversion rate?

Significantly. Research consistently shows that redirect gateways convert lower than embedded payment forms because the off-site transition increases cart abandonment. The payment methods available also matter — offering only cards in a market where local payment methods are dominant (like iDEAL in the Netherlands) directly reduces conversion. Gateway performance (speed of the payment form loading and processing response) also has a measurable impact on mobile conversion.

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

A payment gateway is the technology that transmits payment data between your store and the financial network. A payment processor handles the actual movement of funds between banks. In many modern gateways (Stripe, Square, Braintree), both functions are bundled into a single product. In older models, they were separate services — a gateway like Authorize.Net paired with a separate merchant account processor. Understanding which model you are working with affects how fees are structured and who to contact for different types of issues.

How do I test a payment gateway before going live?

Every major gateway provides a sandbox or test mode. Enable test mode in the WooCommerce gateway settings, then use the gateway’s provided test card numbers to simulate successful payments, declined cards, 3DS authentication challenges, and refunds. For subscription stores, test at least two billing cycles to confirm automatic renewal behavior. Always disable test mode before launching — live mode and test mode use separate API keys and orders processed in test mode are not real transactions.