WooCommerce Redsys Gateway Version 31.0.5 Changelog

Here’s what’s changed in WooCommerce Redsys Gateway Version 31.0.5

  
* FIX: Subscription renewals could still get stuck in an endless SIS0051 ("número de pedido repetido") loop after 31.0.4. The 31.0.4 fix released the stored order number only when the decline arrived as a signed Ds_Response without an authorisation code, but Redsys reports a duplicate order number as a plain errorCode (SIS0051) in the trataPeticion response, which the plugin handles through the request-error path — so the stored number was never released and every retry resent the exact same DS_MERCHANT_ORDER (already burned at Redsys by attempts made before updating), failing again with SIS0051 forever. Renewal charges now ALWAYS generate a brand-new order number at the start of every attempt and never read a previously stored one: the iniciaPeticion/trataPeticion pair of the attempt shares that freshly generated number (so they cannot mismatch, SIS0502), duplicate concurrent workers are stopped by the renewal lock before the number is generated, and the last number sent is still persisted to order meta so refunds and the payment notification (IPN) resolve the right order. Stores stuck in the SIS0051 loop self-heal on the next scheduled retry after updating, with no manual action needed. Applies to the Redirection and InSite gateways and every subscription plugin routing through them (Google Pay / Apple Pay delegate to Redirection).
  

View the full WooCommerce Redsys Gateway Changelog

(No Ratings Yet)

Loading...