Woocommerce Redsys Gateway icon

Release v32.0.0

Woocommerce Redsys Gateway v32.0.0

What's new in v32.0.0

Woocommerce Redsys Gateway v32.0.0 was released on . Allow customers to check out and pay via RedSys (the Servired / Sermepa successor) on your WooCommerce store. See the full changelog below and compare with the complete version history.

Release details

Released
7.9 MB
File available

Changelog

Added
  • Manage your store from a native app. This release turns on the management app API that
  • A "Behaviors towards the APP" section in the Redsys advanced settings to enable or
  • A per-user "App profile" on the user edit screen, so each employee connecting from the
  • An "Apps and Plugins" section in the Redsys advanced settings: a read-only overview of
  • PackDesk is published on the Mac App Store, and the official "Download on the Mac App
Other
  • until now shipped hidden. Your store can be connected to PackDesk, the native macOS
  • management app, to work with orders, refunds, products and customers. The API (namespace
  • redsys-manager/v1) is strictly opt-in: OFF by default, it requires HTTPS and an active
  • license, and no app can reach the store until a merchant enables it. It offers an order
  • picking queue and order updates, product and customer routes, a "changes" delta feed for
  • efficient sync, safe write retries via Idempotency-Key, and a per-employee rate limit
  • (applied per user, never per IP).
  • disable the API, allow or restrict refunds for the Customer service profile, require a
  • minimum app version, and set the per-employee requests-per-minute limit (default 300).
  • app operates under a profile (for example Administrator or Customer service) that gates what
  • they can see and do, including whether they may issue refunds.
  • the native app and the rest of the plugins, websites and skills.
  • WooCommerce no longer warns that the gateway is untested on the version you run. The minimum
  • supported WooCommerce is unchanged (7.4).
  • Store" button now appears at the top of "Behaviors towards the APP" and in the featured-app
  • area of "Apps and Plugins", so the app can be installed straight from the store settings. It
  • uses Apple's own artwork in the administrator's language (English, Spanish, Catalan, French
  • or Portuguese; English for Basque and Galician, which Apple does not publish) and opens each
  • visitor's own country store. The app entry now shows the published version and states that
  • it requires macOS 26 Tahoe or later.
  • external service such as Cloudflare Images. The plugin saved and showed a URL it had built by
  • hand from the local uploads folder instead of the media library's real attachment URL, so on
  • an offloaded store that address pointed at a file no longer served locally and the image was
  • broken. The QR URL is now resolved through wp_get_attachment_url, the attachment id is stored,
  • and the address is resolved every time the QR is shown, so it follows the file wherever it is
  • served - including offloading enabled after the QR was created. Existing QR codes are healed
  • automatically the first time their product is opened; otherwise the "Regenerate QR Code" link
  • rebuilds them correctly.
  • showing "Signature verification failed in successful_request". The order-completion step in one
  • of the two Bizum gateways verified the bank notification with the gateway's plain configured
  • signature key, while the operation had been signed with the per-order key actually used for it -
  • as happens on stores with a per-user or dual/test terminal, or the bizum_modify_data_to_send
  • filter. The notification passed the first validation and was then rejected by this second check,
  • so the money was taken but the order stayed pending. The completion step now resolves the signing
  • key exactly like the notification validation - and like the other Bizum gateway already did -
  • from the order meta, then the request transient, then the settings key for the order's customer,
  • so both agree.
Improved
  • Compatibility declared with WooCommerce 11 ("WC tested up to" is now 11.0), so
Fixed
  • The product QR code did not appear on stores whose media library is offloaded to an
  • A Bizum payment could be charged at the bank yet leave the order pending, with the log

Compatibility

Requires WordPress
5.4
Tested up to
7.0
Requires PHP
7.4

Verified safe

Woocommerce Redsys Gateway v32.0.0 scanned clean with no security threats detected.

View full scan report