WooCommerce RedSys Payment Gateway 30.4.1

I’d reach for WooCommerce RedSys Payment Gateway on Spanish Woo stores that need more than bare card redirect: Bizum, tokenization, preauth, refunds, Apple/Google Pay, and fewer checkout dead-ends. It fits merchants who want Redsys to behave like a proper Woo gateway, not a bolt-on that dumps users off-site and hopes the callback lands.

What I like is the mechanics. Most control lives in WooCommerce → Settings → Payments → Redsys. Gateway options are stored in WordPress settings, while payment results and flags land in order meta / HPOS order data. The heavy lifting is plugin-side PHP plus checkout JS; this is not a theme-template product. You can tweak labels, logos, and payment flow from settings, but the real transaction logic is hardcoded in the plugin classes, not something a page builder will override cleanly.

Where it usually goes sideways: the bank says “paid”, Woo order stays Pending. Root cause is almost always the server callback getting mangled by cache, redirects, or a security layer. I fix that by checking DevTools → Network for the return flow and server logs for requests hitting /?wc-api=. If that endpoint returns 301/302/403, the order status update can fail. Fast workaround: exclude checkout, order-received, and the Redsys callback URL from cache/CDN rules; then whitelist it in Cloudflare, Wordfence, or the host WAF.

Second common mess: test/live credential mismatch or JS optimization breaking checkout. In practice, delayed or combined scripts can break payment UI the same way they break other Woo dynamic flows. In LiteSpeed Cache / WP Rocket / Autoptimize, exclude plugin assets loaded from the Redsys plugin folder and avoid delaying core Woo checkout scripts. If the console shows JS errors on checkout, fix those first; payment gateways are usually just the first thing to explode.

On GPL and activation: the plugin can run without connecting a key, but on the official WooCommerce.com build that mainly means no automatic updates and no vendor support. There’s no demo import story here. Manual updates are simple: download the new ZIP from your account, upload it in Plugins → Add New → Upload Plugin, or replace the plugin folder over FTP. If you edited plugin files directly, the update will wipe them. Keep custom logic in a small snippets plugin or mu-plugin instead.

I won’t fake a “personally activated and verified on your install” claim without direct backend access. What I can say from the code/docs trail: the product is mature, actively maintained, HPOS-aware, and built for real Redsys workflows rather than generic gateway fluff.

FAQs (the stuff people actually trip over)