WooCommerce.com

WooCommerce Redsys Gateway 33.0.x

New branch 33.0.x of the Redsys plugin for WooCommerce: Bizum for subscriptions, Apple Pay and Google Pay Express at the classic checkout, a redesigned setup wizard, and security enhancements.

JC Jose Conti 10 min read
Ilustración de un checkout en portátil y móvil con pago recurrente, botones de pago exprés y un escudo de seguridad, con la versión 33.0

The development of this version has cost 3,950 euros. The accumulated cost for this year is 44,330 euros. The accumulated cost since the first version is 243,060 euros, but the cost for you is only the license of 79€.

New branch 33.0.x of the Redsys plugin for WooCommerce from WooCommerce.com.

It is a major version: Bizum for subscriptions, Apple Pay and Google Pay as Express buttons at the classic checkout and cart, and a completely redesigned setup wizard. It also brings security enhancements from an advanced audit and fixes found while testing all payment flows, one by one, against the Redsys testing environment.

Branch versions

33.0.0

New:

  • Bizum for subscriptions: first payment and automatic renewals with WooCommerce Subscriptions, YITH, SUMO, Advanced Subscriptions, Subscriptions for WooCommerce, WebToffee, and WPSubscription. It comes disabled: activate "Offer Bizum for subscriptions" only if your bank has enabled recurring payments for Bizum.
  • Customers can save Bizum in My account › Payment methods, add another number (when there is a maximum renewal amount), and change to Bizum the payment method of a subscription.
  • Bizum for subscriptions: new setting "Maximum renewal amount" in each Bizum gateway, the highest amount that Bizum can charge on a renewal. Without it, renewals must be exactly the amount of the first payment and Bizum is not offered in My account › Payment methods. It only works in the real Redsys environment.
  • Bizum for subscriptions: each saved Bizum remembers the amount it allows. A renewal that does not cover is not sent to Bizum (it would reject it) and fails with a note explaining the reason, so the customer can pay it manually.
  • Bizum is not offered for subscriptions that renew less than once a year: a saved Bizum expires one year after being created if no renewal uses it.
  • Apple Pay and Google Pay can be displayed as Express buttons at the classic checkout (at the top) and in the classic cart, instead of as another payment method. New setting "Payment type at the classic checkout" in each wallet; by default, the usual behavior is maintained.
  • Redesigned setup wizard in nine steps: first the license (key or connection with WooCommerce.com), then the payment methods, credentials, options for each method (one-click payment, Click to Pay, Bizum for subscriptions, Apple Pay and Google Pay), orders, testing mode only for administrators, logs, and a summary of what remains to be done.
  • After a failed or rejected payment, the checkout notifies the buyer that the payment has not been completed and asks them to pay again (when the KO URL returns to the checkout).
  • Express orders from Apple Pay and Google Pay now retain the origin of the WooCommerce order (UTM source, campaign, originating site), just like orders made from the checkout.

Updated:

  • The Redsys setup wizard no longer shows WordPress, WooCommerce, or other plugin administration notices, so its steps can be read clearly.

Security:

  • Apple Pay now charges the total order amount calculated by the store, never a total sent by the browser.
  • Apple Pay and Google Pay in the block checkout reject a shipping method that the cart has not calculated, instead of using a shipping cost sent by the browser.
  • Google Pay Express (product page and express orders) could charge an order without shipping costs when the request indicated a shipping method that the cart had not calculated. Now that payment is rejected and the buyer is asked to choose another method.
  • The get_product tool from the MCP of UCP no longer returns draft, private, or restricted products, just like the REST route of the catalog.
  • Payment notifications from Bizum, Bizum Checkout, PayGold, Direct Debit, Apple Pay, and Google Pay reject an unknown order number instead of failing with a PHP error.
  • PayGold accepts a card registration notification only when its Redsys signature is valid.
  • A payment notification from Inespay without an amount leaves the order pending instead of completing it.
  • The search for shipping methods in the gateway settings requires being a store manager and a valid security token.
  • The SHA-256 secret key of Redsys is no longer written in plain text in the redsys-global debug log (with WP_DEBUG active) nor in the settings dumps recorded by the plugin, and order keys are hidden. If you have worked with debugging active, delete the old redsys-global logs.

Corrections:

  • 3D Secure authentication was rejected by the issuing bank ("Areq N Response") when the customer entered the phone with +, spaces, parentheses, or dashes, or with a country prefix different from the billing one. Now the phone is sent in the format required by 3D Secure, with its own country prefix, or is not sent when it is not possible.
  • Express payments from Apple Pay and Google Pay with Premium Freelancers: the amount displayed on the payment sheet is now always the amount charged, with the IRPF calculated product by product and only for Spanish companies and freelancers.
  • An Express payment is no longer charged when a mandatory field of the Express form is missing or when the total order does not match the amount authorized by the customer.
  • With simple permalinks, the Redsys payment window within the store and Bizum Checkout no longer sends the customer to the homepage instead of opening the payment.
  • With the store name setting empty, the Redsys payment page no longer shows "Commerce: false".
  • InSite in the block checkout now loads in stores with simple permalinks and in stores installed in a subfolder.
  • Paying with a saved card for an order created from the administration (from its payment link) is no longer rejected by Redsys with SIS0574.
  • Renewals of WebToffee subscriptions no longer trigger the WooCommerce notice "incorrect call".
  • A payment completed more than an hour after opening the payment page is now associated with its order even when the order IDs are long (10 digits or more), instead of leaving a charged order pending. The relationship between the Redsys order number and the order now lasts 24 hours instead of 1, and is also saved in the order itself.
  • Apple Pay and Google Pay Express in the block checkout (WooCommerce 10.8 and later) now retain the order note, additional checkout fields, and data that other plugins save at checkout, such as a date or delivery window.
  • Google Pay in the block checkout now pays the order that the checkout had already prepared, like Apple Pay, instead of creating a second order from the cart, so that the data saved in that order before paying is retained. With WooCommerce 10.8 or later, the checkout no longer prepares that order until "Place order" is clicked.
  • The cleaning of duplicate scheduled actions could, when two requests executed it at the same time, cancel both copies of the email check; now it always retains the same one.
  • The logs of each payment method were not written until their settings were saved once, although the settings screen showed the log as activated.
  • Apple Pay and Google Pay Express on the product page: the "Accept terms and conditions" window now opens as a popup. With the Express custom fields disabled, it appeared without styles at the bottom of the page.
  • PHP notices are gone at checkout with products that do not have an assigned product type (created by some importers or with wp_insert_post).
  • Bizum, Bizum Checkout, Google Pay by redirection, PayGold, and Direct Debit: when the notified amount did not match that of the order, the notification failed with an error instead of leaving the order pending with its note.
  • Bank transfer: Redsys notifications did not reach any manager, so the order was not updated with them.
  • Bizum, Bizum Checkout, and Google Pay by redirection: the "Transaction limit" setting had no effect; now the method is hidden when the cart total exceeds it.
  • Bizum Checkout no longer fails with a fatal error when it cannot contact Redsys; the customer is asked to try again.
  • Bizum Checkout: the waiting page takes the buyer to the thank you page as soon as the order is paid, even if a cache returns an outdated payment indicator.
  • Bizum Checkout: reloading the waiting page no longer sends a new payment request for a paid order, never duplicates a request that the buyer can still approve, and uses a new order number when the previous one has expired.
  • Apple Pay Express in the block checkout could charge a new empty order and leave the buyer's addresses in another order that expired without payment.
  • Express orders from Apple Pay were not charged when the plugin created the buyer's account and started their session during payment (nonce verification failed).
  • Apple Pay (block checkout): paying for an existing order from its payment page (payment links, pay again after a failed payment) now charges that order and shows its total, instead of failing or using the cart.
  • The "Place order" button now uses the colors and text saved in the button settings of each gateway.
  • PayGold has its own default title and description.
  • ACP: the "Delegate payment" ability is now registered in the WordPress Abilities API (it never was), so MCP customers using the WordPress MCP Adapter can see it; the ACP status informs whether it is actually available.
  • Block checkout: Redsys payment methods now declare the WooCommerce block data store as a dependency, so they continue to load regardless of the order in which the page prints its scripts (and the WooCommerce development notice disappears).
  • Orders consisting only of virtual and downloadable products are now completed after payment, as WooCommerce does, when "Status of virtual-only orders" is left at its default value; they no longer remain in Processing.
  • InSite: when the 3D Secure page of the issuing bank resends its response after the payment has been completed, the buyer could end up on an error page ("Nothing to see here"); now they reach their order confirmation and no empty request is sent to Redsys.
  • InSite: cuando la página 3D Secure del banco emisor volvía a enviar su respuesta después de que el pago se hubiera completado, el comprador podía acabar en una página de error («No hay nada que ver aquí»); ahora llega a la confirmación de su pedido y no se envía ninguna petición vacía a Redsys.

¡No te pierdas las novedades!

¡No hacemos spam! y te puedes dar de baja cuando quieras

Share
JC
Jose Conti
Desarrollador WordPress y WooCommerce. Buceando en WordPress desde 2004.

Leave your comment

Your email address will not be published. Required fields are marked *