Payment Gateway for WooCommerce: How to Choose and Integrate the Right Provider

A payment gateway for WooCommerce is the plugin or API integration that connects your store checkout to the acquirer: without it every order stalls in pending-payment status. WooCommerce powers about 20% of e-commerce sites worldwide according to W3Techs, so the provider choice affects margins, conversion and EU compliance. This guide covers integration types, real fees and the setup process.

Payment Gateway for WooCommerce: Costs & EU Guide 2026

What a payment gateway does inside the WooCommerce checkout

The payment gateway decides which methods appear at checkout, transmits customer data securely to the acquirer and confirms or rejects the order. Technically a WooCommerce gateway is a PHP class extending WC_Payment_Gateway: the registered plugin hooks into the checkout page, submits the payment request and receives the outcome through redirect or webhook.

A typical EU store flow works like this: the customer picks a card or a local method, the plugin calls the gateway, the gateway runs the 3D Secure 2 challenge required by PSD2, the issuer approves the debit and the webhook flips the order from pending to processing. If the webhook is missed (the customer closes the browser before the redirect completes) the order stays suspended, which is why the integration must treat webhooks as the authoritative confirmation rather than the redirect alone.

Scale matters for the decision: per W3Techs WooCommerce is the most widely used e-commerce software on the web, and it remains the default choice for European merchants who want full control of their catalogue without platform subscription fees. Thousands of EU small and medium businesses run on it, so a two-point difference in processing fees compounds into a material annual saving.

Official plugin, marketplace extension or REST API: choosing the integration

WooCommerce payment integrations come in three shapes, with different consequences for development effort, PCI scope and checkout experience.

Marketplace plugin: the fast route. Install the provider extension from Plugins, paste the API keys in the settings and the methods appear at checkout. If the gateway ships an official extension listed on WooCommerce.com, compatibility with platform updates is generally better maintained. Quality still varies by provider.

Hosted checkout (redirect): the gateway hosts a payment page that the WooCommerce checkout redirects to. Practical benefits: minimal PCI scope (your server never touches card data, so the merchant qualifies for SAQ A) and setup in days. Trade-offs: some customers abandon when they leave your domain, and testing changes on the payment page is less straightforward.

Native REST API integration: to control every checkout detail (fields, retries, card tokenisation for recurring orders) you build a module that calls the gateway REST API directly. Companies running subscriptions or marketplace-style flows usually go this way. It requires a WooCommerce developer rather than a payments specialist: the delicate parts are webhook handling and order state transitions.

If you have no in-house developer, use the official plugin when one exists, otherwise a hosted checkout, and reserve REST API work for when the sales flow demands it.

For the step-by-step configuration see the full ecommerce payment integration guide.

WooCommerce payment fees: flat percentage or IC++

Fees are where providers really differ, and two pricing models coexist in Europe.

Flat percentage (blended): one rate covering interchange, scheme fees and the provider margin. On European cards Stripe charges 1.5% + €0.25 for EEA cards (Stripe pricing pages, 2026); PayPal starts at 2.9% plus a fixed fee for EU merchants (PayPal Business rate card). On a €60 average order, a 2.9% rate costs almost €0.90.

IC++ (interchange plus plus): every component is visible on the statement. Interchange is the issuing-bank fee, capped in the EEA by Regulation (EU) 2015/751 at 0.2% for debit cards and 0.3% for credit cards. Scheme fees and the provider markup sit on top. On real European volume, where debit cards dominate, the all-in cost often lands below 1%.

RoxPay applies €0.15 + 0.35% to 0.85% (IC++), so the visible fee is only the transparent markup over regulated costs.

Worked example for a €10,000 monthly card volume: a blended 2.4% rate costs about €240, while an IC++ model with 0.3% average interchange, 0.1% scheme fees and 0.5% markup stays under €100. That gap is worth thousands of euros a year at modest volumes. EU companies comparing providers should ask for the full fee schedule, not the headline rate.

PSD2, 3D Secure 2 and PCI DSS: what EU rules require

A European WooCommerce gateway has to satisfy three regulatory obligations.

Strong Customer Authentication (PSD2): Directive (EU) 2015/2366 mandates two-factor authentication on online payments since 14 September 2019. For a WooCommerce store this means the gateway must support 3D Secure 2 with risk-based authentication. A provider still relying on 3DS1, or disabling 3DS, exposes the merchant to rejected authorisations and chargeback liability.

PCI DSS: running a WooCommerce store does not exempt you from PCI, but the workload depends on the integration. With a hosted page or drop-in iframe the merchant completes the simplified SAQ A self-assessment; capturing card data on your own server moves you to SAQ D with quarterly ASV scans. Always check that the provider holds a current PCI DSS Level 1 certificate.

GDPR and payment data: the gateway acts as a data controller for transaction data, so review its privacy terms, log retention and data portability options for EU customers. A provider with EU servers also simplifies cross-border sales within the Union.

Practical test before signing: request the current PCI certificate and confirm the plugin documentation explicitly states 3DS2 support. These two checks prevent payment outages when supervisory deadlines hit.

EU local payment methods and settlement: what to verify

A WooCommerce checkout that only lists Visa and Mastercard loses orders in markets where local rails dominate.

SEPA rails: for recurring charges and B2B orders SEPA Direct Debit costs far less than cards; under Regulation (EU) 2024/889 banks in the Union must accept instant credit transfers within 10 seconds (reception obligation active since January 2025, sending from October 2025). Gateways offering payment initiation on SEPA Instant shorten cash collection considerably.

Local methods per market: iDEAL carries the largest share of Dutch online payments, Bancontact dominates in Belgium, Bizum in Spain, BLIK and Przelewy24 in Poland, Multibanco and MB Way in Portugal, MyBank in Italy. If you sell across the EU, the gateway should cover these native schemes from the start: bolting on a second provider later doubles fixed costs.

Settlement: ask for funding times per corridor (cards, SEPA, wallets). A gateway paying out to any SEPA bank within 48 hours materially reduces working capital needs compared with T+5 schedules typical of some traditional acquirers.

Disputes: the merchant panel should handle chargebacks and information requests with visible deadlines. Stores running WooCommerce Subscriptions should also verify recurring mandate management and pre-renewal notifications.

In short: transparent pricing with full cost visibility, coverage of your target markets' methods, native 3DS2, minimal PCI scope and predictable settlement.


Frequently Asked Questions

How much does a payment gateway for WooCommerce cost?

Flat-rate gateways charge between 1.5% and 3.4% plus a fixed fee: Stripe bills 1.5% + €0.25 on EEA cards (Stripe pricing 2026) and PayPal starts at 2.9% + fixed for EU merchants. With RoxPay IC++ pricing the merchant pays €0.15 + 0.35% to 0.85% (IC++) plus interchange and scheme fees, capped in the EEA by Regulation (EU) 2015/751 at 0.2% debit and 0.3% credit.

How do I install a payment gateway in WooCommerce?

From the WordPress panel: Plugins, Add New, search for the provider plugin, Install and Activate. Then in WooCommerce, Settings, Payments enable the method, paste the publishable and secret API keys and choose the methods displayed at checkout. Complete a test order with sandbox credentials before going live, and verify that the plugin receives webhooks, which are the authoritative payment confirmation.

WooPayments or a third-party gateway for an EU store?

WooPayments is Automattic's native solution: activation takes minutes, but it is not available in every EU country and uses a flat percentage. A third-party gateway with IC++ pricing shows every cost component on the statement and lets one plugin accept local EU methods (iDEAL, Bancontact, BLIK, MyBank), which is more efficient for merchants selling in multiple Union markets.

What level of PCI compliance does a WooCommerce store need?

It depends on the integration method. If payment happens on a gateway-hosted page or inside a drop-in iframe, the WooCommerce server receives no card data and the merchant files the simplified SAQ A questionnaire. Direct card data ingestion on your own server triggers SAQ D with quarterly scans. Always verify the provider's current PCI DSS Level 1 certificate.

Can a WooCommerce store accept SEPA Direct Debit and instant transfers?

Yes, provided the gateway supports them. SEPA Direct Debit suits subscriptions and recurring supplies (single mandate, revocable up to 8 weeks after the debit). Instant SEPA credits arrive within 10 seconds under Regulation (EU) 2024/889, which required EU banks to accept them from January 2025. In Italy MyBank is the reference circuit for bank-authorised checkout payments.

Get started today

Optimize your payments today

Integrate the RoxPay gateway into your e-commerce store. Complete API documentation and dedicated technical support. Get started at /en/contact.

✓ No monthly fixed costs · ✓ Activation in 24 hours · ✓ Dedicated technical support