The development of this version has cost €5,400. The total for this year is €25,400. The cost since the beginning has already risen to €75,000, but the cost for you is only the license for $79.
New 12.0.x branch of the Redsys gateway for WooCommerce from WooCommerce.com
Branch Versions
12.0.0
Added:
- NEW: PSD2 compatibility (beta).
- NEW: Added Browser iframe
- NEW: Site Health usage
- NEW: Declared compatibility with WooCommerce 4.6
- Fixed a compatibility issue with some languages and WPML.
PSD2 Compatibility
This is the first version compatible with PSD2. Attention, it is in beta and is only compatible with Redsys (by José Conti), Bizum, MasterPass, direct debits, and bank transfers. Compatibility with Redsys Preauthorizations (by Jose Conti) and InSite has not yet been added. The next version will be compatible with everything and I will try to make it a stable version with PSD2 as much as possible. But for that, I will need you to perform tests on your test terminals. The more you test and report issues, the more robust the code will be. If you want to perform tests, you must go to the Redsys (by Jose Conti) configuration and activate PSD2.
I have been working on adapting to PSD2 since the beginning of August, creating a specific class for capturing the necessary data from users. The information sent is even greater than what the official Redsys plugin (for redirection) sends, and all of this will continue to increase in future versions with specific functionalities that I will add to improve fraud detection globally in Redsys.
Apart from all the hours I have had to invest in this version for plugin development, there have also been more than 90 emails exchanged with support, several hours on the phone looking for joint solutions, detection of errors in the documentation for developers that I have been notifying and that will be fixed in future versions or even ways to test certain points that even Redsys did not know how to do. Being something new even for the support team, it has been a joint discovery of the whole API functionality.
PSD2 is currently compatible with all payment methods except for Redsys Preauthorizations (by Jose Conti). When I am sure that there are no problems with Redsys (by Jose Conti), I will transfer the code to preauthorizations.
Usage of “Site Health”
As many of you may know, WordPress added “Site Health” a few versions ago. It is a feature that you will find in Tools > Site Health. This magnificent tool added by WordPress can be extended, and that is something I have done for the Premium version and that you will find in this version. By accessing this WordPress screen, you can quickly see if your server or firewall will cause you problems with, for example, SOAP for Redsys, which is one of the typical problems that many installations have. I will gradually add new tests that I find interesting. For now, these are implemented in this version:
Added Browser iFrame
If you want to activate it, you must go to the Redsys (by Jose Conti) configuration and activate it.
In this discovery of the entire new Redsys API, I have been discovering allowed tricks that are not documented.
As many of you may know, Redsys prohibits the insertion of the payment gateway via iframe on the site, but with the arrival of PSD2, which requires certain things to be placed inside an iframe, they now allow it, as long as the Redsys URL is displayed, so I present to you the Browser iFrame, the way for your users to NEVER leave your site, even if it is through redirection. Be careful, you must ensure that your bank accepts the Browser iFrame; I cannot guarantee that all banks accept it. You can test it in the Redsys example store and see how it works, or you can also see it in the following video.
12.0.1
Fixed:
- Fixed an issue with PSD2 when a user had never purchased in the store.
- Fixed a strange issue on some servers that caused a 500 error in the Redsys notification.
- Fixed a problem in the logs related to an array().
- Updated the name of a variable from uppercase to lowercase.
- Declared compatibility with WordPress 5.5, which I had forgotten to declare.
12.0.2
Added:
- Now you can enable or disable the automatic deletion of expired tokens. By default, it is disabled. It must be configured from the Redsys (by Jose Conti) settings screen.
- Declared compatibility with WooCommerce 4.7.
Improved:
- I have improved several texts in “Site Health” to make it clearer what is happening and to provide more precise instructions (if necessary) to hosting or Sysadmin.
Fixed:
- Fixed a bug in the credit card images widget.
- Fixed an issue with the receipt page if subscriptions are enabled.
- Fixed a bug related to tokens obtained prior to the PSD2 regulation, and if PSD2 was activated in the plugin.
12.0.3
Fixed:
- Removed a ghost button that appeared on the Browser iFrame screen
- Fixed an issue related to tokens and one-click payment.
If you still do not have the official extension from WooCommerce.com for Redsys, you can purchase it at this address and enjoy all the features that no other plugin offers.
If you are not familiar with everything it offers, you can check this table where I show the differences and you will see that the premium surname of this plugin is due to everything it offers and differentiates.
