The development of this version has had a cost of 5,400 euros. This year’s cumulative cost is 25,400 euros. The cost from the beginning is already 75,000 euros, but the cost for you is only the license of $79.
New 12.0.x branch of the Redsys Gateway for WooCommerce from WooCommerce.com
- NEW: PSD2 (beta) support
- NEW: Added iframe browser
- NEW: Site Health Utilization
- NEW: Declared compatible with WooCommerce 4.6
- Fixed a problem with support for some languages and WPML.
This is the first PSD2-compatible version. Attention, it is in beta and is only compatible with Redsys (by José Conti), Bizum, MasterPass, direct debits, and bank transfers. Support for Redsys Preauthorizations (by Jose Conti) and InSite has not yet been added. The next version will be already compatible with everything, and as far as possible, I will try to make it a stable version with PSD2. But for that, I will need you to test your test terminals. The more you test and report me problems, the more robust the code will be. If you want to test, you must go to Redsys configuration (by Jose Conti) and activate PSD2.
I have been working on the adaptation of PSD2 since the beginning of August, creating a specific class to capture the necessary data from the users. The information that is sent is even higher than the one sent by the official Redsys plugin (for redirection), and all this is going to increase in future versions with specific functionalities that I will add that will improve fraud detection at a global level in Redsys.
Apart from all the hours I have had to invest in this version due to the development of the plugin, there have also been more than 90 emails crossed with support, several hours on the phone looking for joint solutions, bug detection in the developers’ documentation that I have been notifying and that they will fix in future versions or even ways to test according to what point that even in Redsys they didn’t know how to do it. Being something new even for dopers, it has been a joint discovery all the way to the API operation.
PSD2 is now compatible with all payment methods except for Redsys Preauthorizations (by Jose Conti). When I am sure that there is no problem in Redsys (by Jose Conti), I will transfer the code to preauthorizations.
Use of “Site Health”
As many of you know, WordPress added “Site Health,” a few versions ago. This is a feature that you will find in Tools > Site Health. This great tool that WordPress added can be extended and is something I have done for the Premium version, and you will find in this version. Accessing this screen of WordPress, you can see at a glance if your server or firewall will cause problems with for example SOAP for Redsys, which is one of the typical problems that have many installations. Little by little, I will add new tests that I find interesting. At the moment, these are implemented in this version:
Added iFrame Browser
If you want to activate it, you must go to the Redsys configuration (by Jose Conti) and activate it.
In this discovery of the whole new Redsys API, I have been discovering tricks that are allowed and that are not documented.
As many of you know, Redsys forbids the insertion of the payment gateway in the site by the iframe. Still, with the arrival of PSD2, which forces you to put things inside an iframe, now they let you put it, as long as the Redsys URL is shown, so I present you iFrame Browser, the way that your users NEVER leave your site, even if it is by redirection. Be careful; you must make sure that your bank accepts the iFrame Browser. I can’t guarantee that all banks will accept it. You can try it in the Redsys sample store and see how it works, or you can also see it in the following video.
- Fixed a problem with PSD2 when a user had never bought in the store before.
- Fixed a strange problem on some servers where there was 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.
- Now you can enable or disable the automatic removal of expired tokens. It is disabled by default. It must be configured from the Redsys configuration screen (by Jose Conti).
- Declared compatible with WooCommerce 4.7.
- I’ve improved several texts in “Site health” to clarify what’s going on and more precise instructions can be given (if necessary) to the hosting or Sysadmin.
- Fixed a bug in the credit card image widget.
- Fixed a problem with the receipt page if you have subscriptions.
- Fixed a bug with the tokens obtained before the PSD2 standard and if PSD2 was activated in the plugin.
- Deleted a ghost button that appeared in the iFrame Browser screen
- Fixed a problem related to tokens and 1-click payment.
If you don’t have the official WooCommerce.com extension for Redsys yet, you can purchase it here and enjoy all the features that no other plugin offers.
If you don’t know everything it offers, you can look at this box where I show the differences and you will see that the premium name of this plugin is for everything it offers and difference.