Worldpay Payment Gateway for WooCommerce: Setup Guide

If you already have a Worldpay merchant account, or your bank has offered you one with good rates, connecting it to WooCommerce is a reasonable choice. The official Worldpay plugin (updated April 2026) handles cards, hosted and embedded checkout, subscriptions and refunds. What trips people up is that there are several Worldpay products with similar names, the old WooCommerce.com extension is discontinued, and the setup involves credentials from a dashboard most store owners have never opened.

This guide covers which plugin to use, what it costs, how to configure it step by step, and when we would tell a client to pick Stripe or WooPayments instead.

Which Worldpay product you actually have

Worldpay has been through several acquisitions and rebrands (Vantiv, FIS, and since 2024 a majority stake held by GTCR), and the developer products reflect that history. Before you install anything, work out which of these you have:

Product	Who has it	Integration route
Worldpay eCommerce (formerly Access Worldpay)	New UK and EU merchants signed up since roughly 2022; US merchants on the new platform	The official Worldpay WooCommerce plugin, API username and password from the Dashboard Portal
Worldpay Business Gateway / Worldpay Online (legacy)	Small UK merchants on older contracts, identified by an Installation ID	Legacy hosted payment page. The old Chrome Orange extension that supported this was removed from WooCommerce.com
Worldpay Corporate Gateway (WPG)	Enterprise contracts	Enterprise plugins and direct API integration; usually involves a developer
Worldpay from FIS (US, formerly Vantiv)	US merchants through banks and ISOs	Often routed through third-party gateway plugins or Authorize.net-style emulation; check with your account manager

Log in to your Worldpay dashboard. If you see a Dashboard Portal with API credentials and an “Entity” reference starting with PO, you are on Worldpay eCommerce and the official plugin is the right path. If you only have an Installation ID and a Remote Administration password, you are on the legacy platform, and the honest advice is to ask Worldpay to migrate you before you build a new checkout around it.

The official Worldpay WooCommerce plugin

Worldpay maintains its own WooCommerce plugin and documents it at docs.worldpay.com. It is free; you pay Worldpay’s transaction fees, nothing to the plugin.

Requirements as of the April 2026 release:

• WooCommerce 8.4 or later (the docs list it as tested up to 8.5.1, but it runs on current releases; test on staging)
• WordPress 6.4.2 or later
• PHP 7.4 or later (use 8.2 or 8.3, for security as much as speed)
• An active Worldpay eCommerce account with Dashboard Portal access
• WooCommerce Subscriptions if you want recurring billing

One requirement catches people out: Worldpay states the plugin is designed to be the only active payment or checkout-related plugin on the store. In practice we have run it alongside PayPal Standard without trouble, but if you use a checkout field editor, a one-page checkout plugin or a second card gateway, expect to do some testing, and do not expect Worldpay support to help with conflicts.

What it supports

• Card payments (Visa, Mastercard, Amex, Maestro where enabled on your account) with 3D Secure 2, which is mandatory for UK and EU cards under PSD2
• Hosted checkout (customer is redirected to a Worldpay page) or embedded checkout via a Checkout ID, which keeps the form on your site while Worldpay’s iframe handles the card data
• Tokenised cards for returning customers and subscription renewals
• Refunds from the WooCommerce order screen
• Recurring payments with WooCommerce Subscriptions, including trials and sign-up fees
• Apple Pay and Google Pay, where enabled on your Worldpay account and configured in the dashboard

Because card entry happens in Worldpay’s hosted page or iframe, your PCI DSS obligation stays at the SAQ A level, the lightest self-assessment. That is the same position you would be in with Stripe Checkout or PayPal.

Fees: what Worldpay charges

Worldpay does not publish one price list; it quotes per merchant. For UK small businesses in 2026, the published starting rates are around 1.3 percent plus 20p per online transaction for turnover under £75,000 a year, dropping to rates from 0.75 percent for larger merchants who negotiate. Expect a monthly gateway fee and possibly a minimum monthly service charge in the contract. Contracts often run 18 months, so read the exit terms.

Compare that with Stripe and WooPayments in the UK at 1.5 percent plus 20p for UK cards with no monthly fee and no contract, and 2.5 percent plus 20p for EU cards. At low volume Stripe is simpler and probably cheaper once you add Worldpay’s monthly fees. At higher volume (roughly £10,000 a month and up), a negotiated Worldpay rate can beat it, and if you also take in-person payments through Worldpay terminals, having one acquirer and one settlement report has real operational value.

Our rule of thumb: if you do not already have a Worldpay contract, do not go and get one only for WooCommerce. If you do have one, the plugin lets you use it without paying a second processor.

Step-by-step setup

Allow an hour, plus however long Worldpay takes to issue credentials. Do the test (“Try”) environment first, then switch to live.

1. Get your credentials. In the Worldpay Dashboard Portal, go to Developer or API settings and create an API username and password for the Try environment. Note your Entity reference (it begins with PO). If you want embedded checkout, create a Checkout ID as well.
2. Install the plugin. Download the latest release from the link in Worldpay’s documentation. In WordPress go to Plugins → Add New → Upload Plugin, choose the zip, click Install Now, then Activate.
3. Enable the gateway. Go to WooCommerce → Settings → Payments. Find Worldpay in the list, toggle it on, and click Manage (or Finish set up).
4. Enter Try credentials. Tick Enable Worldpay, paste the Try API username and password, the Entity reference, and the Try Checkout ID if you are using embedded checkout. Leave “Enable live mode” unchecked. Turn Debug on for now. Save.
5. Set the checkout title and description. Customers see these on the payment step. “Credit or debit card” works better than “Worldpay”, which most shoppers have never heard of.
6. Run test orders. Worldpay’s docs list test card numbers for successful payments, declines and 3DS challenges. Place at least one of each. Check that the order status moves to Processing (or Completed for virtual products) and that the transaction ID appears in the order notes.
7. Test a refund. Open a test order, click Refund, enter an amount, and choose “Refund via Worldpay”. Confirm it shows in the Worldpay dashboard.
8. Test a subscription if you sell one. Create a subscription product with a short renewal period, buy it with a test card, then trigger a renewal from WooCommerce → Subscriptions → the subscription → Actions → Process renewal. The renewal should charge the stored token without customer involvement.
9. Go live. Generate Live API credentials in the dashboard, paste them into the Live fields, tick “Enable live mode”, turn Debug off, and save. Place a small real order with your own card and refund it.

Keep the Debug log off in production. It writes request and response data to WooCommerce → Status → Logs, which is useful while testing and a liability afterwards.

Troubleshooting the common failures

“Payment method not available” at checkout

Usually a currency mismatch. Worldpay only offers the gateway for currencies enabled on your merchant account. Check WooCommerce → Settings → General → Currency against what your Worldpay account is set up for. Multi-currency plugins that switch the store currency on the fly will hit this constantly.

Orders stuck in Pending payment

The customer paid but WooCommerce never heard about it. With the hosted checkout, that means the return or webhook call from Worldpay did not reach your site. Common causes: a security plugin or Cloudflare rule blocking the callback, a caching layer serving a cached response to the callback URL, or the site being in maintenance mode. Exclude the WooCommerce API endpoints (/wc-api/ and /wp-json/wc/) from caching and firewall challenges.

3D Secure challenge never loads

Almost always a conflict with a checkout customiser or a theme that strips the iframe. Switch to a default theme on staging and deactivate checkout-related plugins to confirm. Also check that your site runs entirely over HTTPS with no mixed content.

Subscription renewals failing

The token was not stored at the original purchase, usually because the subscription extension was activated after the first orders came in. Ask the customer to update their payment method from My Account → Subscriptions, which creates a fresh token.

Alternatives worth considering

Be honest with yourself about why you want Worldpay. The alternatives for a WooCommerce store in 2026:

• WooPayments: built by Automattic on Stripe, free plugin, no monthly fee, the only gateway that works with every WooCommerce feature on day one (block checkout, in-dashboard disputes, Apple Pay and Google Pay without extra setup). The default for new stores.
• Stripe: same underlying processor with a more flexible dashboard and better developer tooling. Choose it over WooPayments if you also sell outside WooCommerce.
• PayPal Payments: higher fees, but some customer segments convert much better with a PayPal button. Most stores run it alongside a card gateway rather than instead of one.
• Adyen or Checkout.com: enterprise acquirers with interchange-plus pricing, worth it above a few hundred thousand a year in card volume.

Worldpay wins when you already have a contract with good rates, you need UK acquiring with settlement into a UK bank account from a bank-aligned provider, or you want one provider for terminals and online. It loses on developer experience, documentation and the speed of getting support.

Selling services rather than products

A lot of the stores we see connecting Worldpay are not selling physical goods at all. Agencies, consultants and freelancers use WooCommerce as a billing front end. The gateway choice matters less there than the order flow: you need a way to collect requirements, track delivery, and close the job. Our Woo Sell Services plugin adds that layer on top of whatever gateway you run, so a Worldpay-processed order becomes a service ticket with conversation, files and a completion step. It is gateway-agnostic, so it works with the Worldpay plugin above as it does with Stripe.

If you are building something more involved, such as a marketplace with vendor payouts, Worldpay is not the right fit; it has no split-payment product comparable to Stripe Connect. Talk to us about WooCommerce development before committing to an acquirer in that case.

Frequently asked questions

Is there still a Worldpay extension on WooCommerce.com?

No. The Chrome Orange “Worldpay Gateway for WooCommerce” extension is listed as no longer available, and its documentation is frozen. Existing users can keep running it, but it targets the legacy hosted payment page and will not get block checkout or HPOS updates. Move to the official plugin.

Does the official plugin work with the WooCommerce block checkout?

Check the changelog of the release you download. Support for the block-based checkout has been added in recent versions, but if your store uses the classic [woocommerce_checkout] shortcode you avoid the question entirely. Test on staging before switching checkout types.

Do I need an SSL certificate?

Yes. Even though card data is entered on Worldpay’s page or iframe, the whole checkout must be served over HTTPS for 3D Secure and browser payment buttons to work, and every host provides free certificates now.

Can US stores use this plugin?

If your account is on the Worldpay eCommerce platform, yes. Many US merchants are on the older Worldpay from FIS (Vantiv) platform, which this plugin does not support. Confirm with your account manager which platform you are on before you install anything.

Where to start

Log in to your Worldpay dashboard and confirm you are on Worldpay eCommerce. Generate Try credentials, install the official plugin on a staging copy of your store, and run the nine steps above. If you get through a test order, a refund and a 3DS challenge without surprises, go live. If you do not have a Worldpay account yet, install WooPayments instead and revisit this when your volume justifies a negotiated acquiring contract.