RedSys Gateway | Pasarela Redsys for WooCommerce

Current release v32.2.1 Updated 🧪 Virus-Scanned (0/70 Clean)
RedSys Gateway | Pasarela Redsys for WooCommerce
Live Demo
⚡ Instant Direct Download 🌐 Unlimited Domains 🛡️ Original GPL File
$5.00 one-time
Lifetime Updates
⚡ Unlock all 7 categories + this asset
🛡️ 1-Click cancel anytime in dashboard
Add to Cart
Actively maintained repository updates
VirusTotal verified (0/70 detected)
Licensed under GPL
Secure 256-bit encrypted checkout
Instant download link via email & dashboard

RedSys Gateway for WooCommerce Overview & Spanish Acquiring Architecture

RedSys Gateway for WooCommerce is a WordPress payment gateway plugin, engineered for developers and agencies building Spanish-market storefronts to connect checkout flows directly to the Redsys acquiring network. The module consolidates Spain’s dominant payment rails — Redsys serves roughly 98% of Spanish merchants — behind one integration, removing the need to wire Bizum, card capture, wallets, and transfers through separate code paths. Within a production build, it operates as the transactional layer: it processes card authorizations, exposes preauthorization confirmation at the order level, stores payment tokens for one-click charges, and dispatches recurring billing events to compatible subscription engines.

Technical Specifications & Deployment Matrix

Engineering Metric Deployment Specification
Base Technology / Framework WordPress plugin extending the WooCommerce payment gateway abstraction
Runtime / Language Requirements PHP 7.0, 7.1, 7.2, 7.3, 7.4, 8.0, 8.2 and 8.3
Communication Protocols Redsys PSD2-compliant authorization flow, InSite embedded card field, Bizum, Bizum InSite, GPay, Apple Pay, MasterPass
Commerce Dependencies WooCommerce core; optional compatibility with WooCommerce Subscriptions, Yith WooCommerce Subscriptions Premium, All Products for WooCommerce Subscriptions, SUMO Subscriptions
Persistence Footprint WooCommerce order metadata, stored payment tokens for one-click charging, preauthorization state held on the order record

Payment Orchestration Pipeline & Execution Flow

Each payment method registers as an independent WooCommerce gateway instance at boot. When a customer reaches the checkout, the plugin attaches every enabled rail — Redsys cards, Bizum, GPay, Apple Pay, MasterPass — as a selectable gateway option. InSite mode injects the card form directly into the checkout page, so card data is captured inside a hosted field without a full-page redirect; standard mode dispatches the customer to the Redsys authorization page and returns them after the bank responds. On return, the module validates the signed notification payload before any order status transition occurs. Preauthorized transactions remain in a held state until an administrator confirms or cancels the capture from the order screen, writing the settlement decision back into the order record.

Recurring revenue runs on token-based charging. The engine is documented as compatible with WooCommerce Subscriptions across all of its options, in addition to Yith WooCommerce Subscriptions Premium, All Products for WooCommerce Subscriptions, and SUMO Subscriptions, so scheduled renewals execute against stored tokens instead of re-prompting the customer for card data. For storefronts selling software products on the same order pipeline, Kestrel API Manager for WooCommerce handles activation-key delivery and managed product access at the order level, keeping fulfillment and billing coupled through WooCommerce’s native data stores.

Architectural & Functional Highlights

  • InSite card capture: the credit card form renders inside the WooCommerce checkout page, shortening the payment path and keeping the customer on-domain during data entry.
  • Bizum and Bizum InSite: Spain’s dominant mobile payment method is available in both redirect and embedded checkout modes, selectable per merchant configuration.
  • Wallet rails: GPay, Apple Pay, and MasterPass register as distinct gateway options, each with its own settings screen and credentials.
  • Preauthorization lifecycle: funds can be held at authorization time, then confirmed or cancelled directly from the WooCommerce order administration screen without merchant-panel access.
  • Transfer rails: bank transfers processed through Redsys are supported, alongside Inespay instant transfers with renewal-payment support and the PayGold method for direct charge requests.

Production Implementation & Operational Resilience

Deployment requires a WooCommerce storefront running PHP 7.0 through 8.3 and an active Redsys merchant account issued by the client’s bank. Each method ships with an isolated settings screen — Redsys and preauthorization parameters, Bizum, MasterPass, InSite, PayGold, and bank transfer each occupy separate panels — so a staging environment can enable individual rails without disturbing others. This isolation matters during agency handover: a client can activate Bizum InSite while leaving wallet rails dormant until bank-side credentials are provisioned, reducing the risk of half-configured gateways reaching production.

State integrity follows the gateway response cycle. Because signed return notifications are validated before order status changes, spoofed callbacks cannot flip an order to a paid state, and failed authorizations leave the order pending for customer retry. PSD2 strong customer authentication is enforced bank-side within the authorization flow, keeping SCA complexity out of the store’s own codebase. Since promotional logic executes upstream of payment capture, Free Gifts for WooCommerce can mutate cart composition — adding conditional gifts based on cart contents — before the gateway receives the final amount, so gift and discount operations stay decoupled from the authorization layer. Customization boundaries are defined by the settings screens themselves: method enablement, credentials, and per-rail behavior are configuration-driven rather than code-driven, which constrains modifications to what each panel exposes unless the gateway classes are extended in a child deployment.

Frequently Asked Questions

Can a preauthorization be confirmed without logging into the Redsys merchant panel?

Yes, confirmation is exposed at the order level. The plugin places preauthorization capture and cancellation actions directly inside the WooCommerce order screen, letting staff settle or release held funds as an order operation without switching to an external interface.

Does Bizum require a full-page redirect away from the checkout?

No, not necessarily. Bizum InSite keeps the confirmation flow embedded within the WooCommerce checkout page, while the standard Bizum configuration operates as a redirect-based method, with the mode determined by merchant and bank-side configuration.

Are scheduled renewal charges supported when running SUMO Subscriptions instead of WooCommerce Subscriptions?

Yes. Compatibility is documented across WooCommerce Subscriptions in all its options, Yith WooCommerce Subscriptions Premium, All Products for WooCommerce Subscriptions, and SUMO Subscriptions, so token-based renewals work across those scheduling engines.

Can bank transfers be settled through the gateway instead of manual statement reconciliation?

Yes. Bank transfer processing through Redsys is built in, and Inespay adds instant bank transfers with support for recurring payments, replacing manual matching with gateway-confirmed order status transitions.

🏷️ Topic Tags:
#GPL Licensed #Premium Plugin #WooCommerce Addon
On this page
    Update history Current release
    1. v32.2.1 Latest
    2. v32.2.0