The development of this version has cost 4,200 euros. The accumulated cost this year is 9,200 euros. The accumulated cost since the first version is 85,330 euros, but the cost for you is only the license of 79 dollars.
New branch 15.1.x of the Redsys plugin for WooCommerce from WooCommerce.com
Branch Versions
15.1.0
Added:
- NEW: Added 1-click payment to Redsys on the checkout page (by Jose Conti), InSite.
- NEW: Added a new function to the plugin API that allows passing the ID of an order and charging it directly if the customer has a saved R token (subscriptions).
- NEW: Added a column on the Payment Methods page in My Account that identifies what type of token it is (1-click payment or Subscriptions). This way customers will know what each saved token is for.
- NEW: You can now define what the “Name” field (billing_first_name) is in the Redsys settings on the checkout page (by Jose Conti) if you change it in any way, for example through checkout page customization plugins.
- NEW: Now the form reloads if the “Name” field on the checkout page is modified.
- NEW: You can now select the maximum amount you want Bizum to display. There are banks that limit the maximum amount of the cart with Bizum. Now you can hide it if it exceeds that amount to avoid payment issues.
- NEW: I have added dns-prefetch for all JS loaded from Redsys to improve loading on the checkout page.
- NEW: Added compatibility with SNI certificates not accepted by Redsys on the checkout page (by Jose Conti).
- NEW: You can now hide a payment method on the checkout page if you have it in test mode for everyone and show it only to the users you want.
Improved:
- Improved information in WordPress Site Health
- Now the checkout page only reloads if there is an error and Redsys on the checkout page (by Jose Conti) is active.
- All JS that my plugin loads now loads in the footer and is minified.
- The “pointer” cursor now appears when hovering over the pay button added by Redsys on the checkout page (by Jose Conti).
Updated:
- Updated the email text sent when some fields are not sent from Redsys along with the Token.
- Declared compatibility with WooCommerce 5.4.
- Updated the Spanish translation file.
Fixed:
- Fixed the SCA, TRA, and LWV that were unintentionally removed in some version in standard payments. They now work again in a way that facilitates not requesting payment verification from the customer so often.
- Fixed an issue that occurred on some servers where Bizum did not work correctly.
- Fixed an issue with flush_rules. Thanks to Fran Torres for the heads up.
- Fixed some undefined variables and properties.
1-click payment has been added to Redsys on the checkout page, allowing you to choose between using a saved card or saving and using a new card:
If a saved card is selected, the card form is hidden to remove distractions
If the order has a subscription product, whether from WooCommerce Subscriptions or Yith Subscriptions, or if it has been selected in the product settings that an R token is required (an option added by my plugin), obtaining a token will be forced if one is not available or a new card is selected.
I have also added the ability to customize the “Name” field in case you modify it through code or a plugin. If you do not provide the correct field name, InSite will not work.
In Bizum, I have added a transaction limit that you can use. I did this because there are banking entities that limit the minimum price of the cart, and if that limit is exceeded, the payment will be rejected. Now you can set that limit, and Bizum will not be displayed if you exceed it.
In all payment methods, I have added a new option that if you put the payment method in test mode globally, you can hide it for all users except for those you select. This will be very useful especially for testing new payment methods added by my plugin and not risking real customers using it to pay when it is not yet ready for that.
15.1.1
Fixed:
- I had unintentionally removed a jQuery. This jQuery is responsible for reloading the page in case of an error, which left InSite unusable in case of an error in data entry.
15.1.2
Fixed:
- Fixed an issue with the operation of Bizum introduced in version 15.1.1, apologies for the oversight.
