Woocommerce Redsys Gateway featured image

WooCommerce Redsys Gateway v31.0.5 - WordPress Plugin

Developer: WooCategory: WordPress PluginsTrusted with 321 downloadsLite2 favoritesLatest v31.0.5Updated 2w ago

Allow customers to check out and pay via RedSys (the Servired / Sermepa successor) on your WooCommerce store.

Related items

Related Woocommerce Plugins

Woocommerce Subscriptions icon

Woocommerce Subscriptions

by Prospress Inc

WooCommerce Subscriptions Plugin allows you to introduce a variety of subscripti...

Woocommerce Smart Coupons icon

Woocommerce Smart Coupons

by StoreApps

Enhance your coupon options – create gift certificates, store credit, coupons ba...

Woocommerce Table Rate Shipping icon

Woocommerce Table Rate Shipping

by WooCommerce

Advanced, flexible shipping. Define multiple shipping rates based on location, p...

Redsys payment gateway for WooCommerce. Thanks to this extension, you will get Redsys, Iupay, refund, tokenization ( Pay with 1 Click), Sequential invoice numbers, CSV Exporter. Compatible with PHP 5.6.x, 7.0.x, 7.1.x and 7.2.x

Redsys the is the most used gateway in Spain (98%).

This extensión add the ability to use Redsys Gateway and Iupay Gateway. Iupay Gateway is the new Redsys Gateway similar to Paypal. Use a second terminal number is allowed by this extension. It is WPML compatible.

Too the extension add sequential invoice number to every paid order. This is essential in Spain. The spanish law is very strict with this. If you don’t have sequential invoice numbers, you can have a very big problem.

A CSV exported is included, so you can export all orders to a CSV file and import it to an Excel. You can use this file for sent the orders, or use for accounting.

Recent releases

Release history

View all 14 versions
v31.0.5Latest
Jul 2, 20267.8 MB
Fixed
  • Subscription renewals could still get stuck in an endless SIS0051 ("número de
Other
  • pedido repetido") loop after 31.0.4: Redsys reports a duplicate order number as a
  • plain errorCode (not as a signed decline), so the stored number was never released
  • and every retry resent the same DS_MERCHANT_ORDER. Renewal charges now ALWAYS
  • generate a brand-new order number at the start of every attempt and never read a
  • previously stored one. The attempt's iniciaPeticion/trataPeticion pair shares the
  • fresh number, duplicate concurrent workers are stopped by the renewal lock, and the
  • last number sent is still persisted so refunds and the IPN resolve the right order.
  • Stores stuck in the loop self-heal on the next scheduled retry after updating.
v31.0.3
Jun 27, 20266.9 MB
View changelog
Fixed
  • InSite card payments on the block-based (Blocks) checkout were rejected by Redsys
  • InSite card payments on the block-based (Blocks) checkout were rejected with
  • InSite card payments on the block-based (Blocks) checkout failed with a
Other
  • with SIS0574 ("browserUserAgent not indicated"): the 3DS browser fingerprint never
  • reached the order because the hook that copies it (woocommerce_checkout_create_order)
  • does not run on the Store API checkout. The InSite Blocks form now collects the
  • fingerprint and sends it with the token, and it is written onto the real order before
  • process_payment runs.
  • an "error code without token" after a few attempts (shown as "check that the
  • checkout/card fields are filled in"). Because the order does not exist yet on the
  • Blocks checkout (order id 0), the prepared Redsys order number was almost constant
  • (~999 possible values, all ending in zeros) and Redsys rejects a reused order number.
  • The InSite Blocks form now uses a unique incremental sequence as a surrogate id.
  • misleading "check that the checkout/card fields are filled in" error and the order
  • was never paid (the browser console showed a 404 on save_order_data). Current
  • WooCommerce no longer creates the order until "Place order" is pressed, so during
  • card entry the Blocks checkout returns order id 0 and the InSite token (idOper) and
  • prepared order number could not be saved to order meta. They are now stashed in the
  • WooCommerce session via admin-ajax when the card is tokenised and moved onto the real
  • order while it is created (woocommerce_store_api_checkout_update_order_from_request),
  • before process_payment runs, and the order-number transient is re-mapped to the real
  • order id so the notification (IPN) resolves the order. The classic/shortcode checkout
  • is unaffected.
  • Security Fix: Added Inespay notification signature (signatureDataReturn / HMAC-SHA256)
  • and amount verification in the Inespay callback to prevent unauthenticated payment
  • forgery. The signature gate covers both the single-payin and the periodic-mandate
  • notifications. Thanks to Shivamani Vastrala for the responsible disclosure.
v31.0.2
Jun 16, 20266.9 MB
View changelog
Improved
  • La sección "Comportamientos hacia la APP" (conexión con la app
  • El filtro redsys_modify_data_to_send ahora recibe
  • Actualizadas todas las traducciones.
Other
  • Redsys Manager) se oculta de los ajustes de Redsys Avanzado mientras la
  • app sigue en desarrollo. La API REST y sus gestores se mantienen; solo se
  • elimina el enlace del menú de ajustes.
  • 'context' => 'add_payment_method' y 'user_id' en el flujo de "Añadir
  • método de pago", para poder enrutar la tokenización al terminal correcto.
  • rechazado por Redsys con error de divisa. Ahora se envía la divisa base
  • de la tienda, que coincide con el terminal por defecto.
  • se creaba como 'C' (one-click) en Redsys. Ahora se envía correctamente
  • DS_MERCHANT_COF_TYPE 'R'.
  • suscripción no respetaban la preautorización. Ahora se envía una
  • preautorización real de tipo 1 que puede confirmarse después.
  • SECURITY: La clave secreta SHA-256 ya no se escribe en texto plano en los
  • logs de depuración; se enmascara mostrando solo los 4 últimos caracteres.
  • SECURITY: Las firmas de las notificaciones (IPN) de Redsys se verifican
  • con hash_equals() (comparación en tiempo constante) en todos los
  • gestores de notificación.
  • SECURITY: El gestor AJAX de borrado de un token ahora exige la capacidad
  • manage_woocommerce además del nonce.
Fixed
  • Añadir una tarjeta desde Mi Cuenta en tiendas multidivisa podía ser
  • Al añadir una tarjeta con la opción de suscripciones, el acuerdo COF
  • Los pagos con tarjeta guardada (token R) y las renovaciones de

Frequently asked questions

Is Woocommerce Redsys Gateway GPL licensed?
Yes, Woocommerce Redsys Gateway is distributed under the GNU General Public License (GPL). You can legally use, modify, and redistribute it on unlimited websites.
Can I use Woocommerce Redsys Gateway on multiple websites?
Yes. Under the GPL license, there are no domain or site restrictions. You can install Woocommerce Redsys Gateway on as many websites as you need.
How much does Woocommerce Redsys Gateway cost on GPLCoffee?
Woocommerce Redsys Gateway is available for $2.99 for a 1-year license or $7.99 for a lifetime license. Membership plans also include credit-based access so you can download Woocommerce Redsys Gateway along with thousands of other plugins for a single subscription.
Are updates included with Woocommerce Redsys Gateway?
Yes. Every new release of Woocommerce Redsys Gateway is synced to GPLCoffee automatically. You can download the latest version any time, and subscribers can use the one-click connector plugin to update directly from their WordPress dashboard.
Is Woocommerce Redsys Gateway safe to download?
Every Woocommerce Redsys Gateway release is scanned with VirusTotal before publication. Scan results (including the specific threat report URL when available) are visible on each version page, and releases flagged as malicious are blocked from the catalog.

Auto-updates included

Install it once, update automatically.

The GPLC Connector installs this plugin from your wp-admin and rolls out new versions to your connected sites - up to 25. Included with 12-month and Geek Lifetime plans (plus legacy 6-month).