569 produtos atualizados nos últimos 7 dias

Changelog do WooCommerce RedSys Gateway

O que mudou em cada versão, da mais recente para a mais antiga. As notas são as publicadas pelo desenvolvedor, no idioma original.

  • Mais recente 32.2.1 · 20 out 2026
  • 204 versões
  • Desde mar 2013

2026

24 versões

Versão 32.2.1

Mais recente
Notas da versão 32.2.1: 1 melhoria 1 correção

Melhoria

  • WooCommerce > Status > System status, section "Redsys for WooCommerce": each active Redsys method now shows whether it is in test or production, and, when test mode for users is on, which user IDs pay in test (for example "(production, test for users: 1)").

Correção

  • Google Pay (checkout and redirection), Apple Pay, Direct Debit and PayGold in test mode, or in test mode for some users, with a live key configured: Redsys authorised the payment and the notification reached the store, but the order stayed pending and was later cancelled, with "Received valid notification" followed by "Signature verification failed in successful_request" in the log. The first check of the notification used the key the payment was signed with (the test key) and the second one…
Assinar para baixar a versão 32.2.1

Versão 32.2.0

Notas da versão 32.2.0: 3 novidades 8 melhorias 90 correções

Novidade

  • Filter redsys_insite_form_language, to choose the language of the InSite card form from code (for example, one per site language).
  • Filter redsys_customer_tokens_limit, to change how many saved cards of a customer the plugin reads (500 by default).
  • The plugin license is now managed in WooCommerce > Settings > Redsys Advanced > General, at the top of the page, and no longer has its own entry in the WooCommerce menu. The license key, how it is activated and where it is stored do not change, and the old address still works: it takes you to the new place. The notice that asks for a license points there too.

Melhoria

  • Compatibility declared with WooCommerce 11.2 ("WC tested up to" is now 11.2), so WooCommerce.com no longer warns that the header does not declare the latest WooCommerce minor.
  • The package published on WooCommerce.com no longer includes the license and update client used by copies bought at plugins.joseconti.com (it was never loaded there). The plugin loads it only when the file is present.
  • Added phpstan.neon (bundled third-party libraries excluded, baseline of existing findings) so static analysis reports only new problems.
  • BEHAVIOUR CHANGE (security): UCP MCP (off by default): tool arguments are now checked against each tool's published input schema before the tool runs; calls that do not match (for example without meta.ucp-agent.profile) get a JSON-RPC -32602 error listing what is wrong.
  • BEHAVIOUR CHANGE (security): UCP (off by default): Dynamic Client Registration - any AI agent creating its own OAuth client in the store - is now off by default, and switched off once on update where it was only on by the old default. If your agents register themselves, turn "Allow Dynamic Client Registration" back on in the UCP settings.
  • BEHAVIOUR CHANGE (security): UCP OAuth (off by default) now accepts only the S256 PKCE method, as the UCP profile requires; "plain" is refused. A developer who needs it can return true from the redsys_ucp_allow_pkce_plain filter.
  • BEHAVIOUR CHANGE (security): UCP OAuth (off by default): the token introspection endpoint answered anyone. It now requires the calling client's credentials (client_id and client_secret) and only reports on that client's own tokens, as RFC 7662 requires.
  • BEHAVIOUR CHANGE (security): UCP and A2A (off by default) no longer accept the access token in the URL (?access_token=), where it ends up in server logs; send it in the Authorization header. A developer who needs the old behaviour can return true from the redsys_allow_bearer_in_query_string filter.

Correção

  • InSite: the "Language Gateway" setting was ignored, so the card fields (placeholders and button) were always shown in Spanish. The chosen language is now sent to Redsys in the classic checkout and in the Checkout Block.
  • Updating with UCP enabled ended in a "critical error" (Call to a member function using_index_permalinks on null) on the first page load after the update. The public UCP discovery file is now rewritten once WordPress has finished loading.
  • Expired saved cards: the scheduled tasks that warn the customer and remove expired cards failed with a database error ("You have an error in your SQL syntax") and never did anything. They now work, remove cards that expired in an earlier year too, and only touch cards saved by this plugin.
  • Customers with more than 10 saved cards: subscription renewals and the Immediate Redsys Charge could use an older card instead of the newest one, a card already saved could be saved again, and the classic checkout did not list the newest cards. The plugin now reads all the Redsys cards of the customer for its own decisions.
  • License: when the license server refused the activation, the settings page only said "Your settings have been saved.". The error returned by the server is now shown, and a refused key is no longer displayed as "License is Active".
  • License: saving Redsys Advanced with the license already active sent it to be activated again on every save. An active license is no longer re-sent.
  • Immediate Redsys Charge (and any charge with a saved card): when Redsys rejected the charge at its first step, the order stayed pending with no explanation. The reason and the Redsys error code are now written in an order note.
  • InSite in the block checkout: a card saved for Pay with One Click after a 3DS challenge was stored as a subscription card. It is now stored with the type it was requested with.
  • InSite in the block checkout: the pay button always read "Pagar". It now shows the translated "Pay" label of the site language.
  • InSite in the block checkout: on a server without the PHP SOAP extension the payment ended in a "critical error". The customer now gets a message asking to choose another payment method, and the cause is written to the InSite log.
  • Classic checkout: with Bizum and Bizum Checkout both in test mode, the test-mode warning was shown twice.
  • One-click purchase from the product page: the shipping options showed "€" instead of the currency symbol.
  • Confirming a pre-authorisation wrote the order status note twice, and moved the order to Completed even when another status was configured for confirmed pre-authorisations.
  • Block checkout: when Bizum Checkout was denied the customer was sent back to the checkout with no message. The error is now shown, as it already was in the classic checkout.
  • Block checkout: an order paid with Bizum (or another gateway of this plugin that uses a payment page) by a customer with a saved card was recorded as paid by card. The order keeps the payment method it was placed with.
  • Bizum, Bizum Checkout, Google Pay, Apple Pay, Direct Debit and PayGold in test mode: with the test key configured and the real key field empty, the payment was authorised by Redsys but the order stayed pending, because the notification was rejected. In test mode the notification is now verified with the test key.
  • Block checkout: paying with a saved card (Pay with One Click) was rejected by Redsys with error SIS0574 (browserUserAgent not indicated). The 3DS browser data is now attached to the order in the block checkout too.
  • Apple Pay: the debug log now shows the parameters actually sent to Redsys, read back from the signed request. Before, its lines were written separately and could differ from the request: the subscription parameters were sent but not logged, and the Apple MerchantID line was logged even when it was not sent.
  • My account > Payment methods: the "Type" column printed PHP warnings (Undefined array key "delete", Undefined variable $token_type_name) on cards or accounts saved by other gateways, for example PayPal. It now describes only the cards saved by this plugin and shows "--" for any other saved method.
  • Bizum Checkout: the waiting page shown while the payment is confirmed loaded jQuery from ajax.googleapis.com. It now uses the copy WordPress ships, so the page makes no request to a third party.
  • Readme.txt declared a malformed license line and "Tested up to: 7.0" while the plugin header said 7.1. Both files now say GPL-3.0-or-later and 7.1.
  • ACP (off by default): with ACP on, WordPress could log "Translation loading for the woocommerce domain was triggered too early" when the hourly ACP clean-up was first scheduled. It is now scheduled on init.
  • Duplicated scheduled actions left by earlier versions are now removed on their own: the paired redsys_acp_process_webhooks / redsys_ucp_process_webhooks workers, a redsys_check_emails_cron with no group, and repeated daily clean-ups. Since 32.1.0 no new ones were created, but existing ones stayed.
  • The plugin's text domain is now its slug, woocommerce-gateway-redsys (it was woocommerce-redsys), in every string, in the bundled translation files and in the Checkout Blocks scripts. Custom translation files saved under the old name in wp-content/languages/plugins or by Loco Translate keep working. Translations stored in the database by a multilingual plugin (WPML String Translation, Polylang) and custom code that filters gettext by the old domain need the new name.
  • Three strings used WooCommerce's text domain and four order-status counters had none; one of them (the cancelled-order plain e-mail) could never be translated. They now use the plugin's.
  • Subscription renewals sent no description to Redsys, so the operation showed an empty description in the TPV (first payments were fine). Renewals and invoice charges of the redirect gateway, and renewals of InSite, now send the description chosen in the gateway settings, as they did before renewals moved to the REST API.
  • Paying at checkout with a saved card (redirect gateway) always sent "Order N" as the description, whatever the gateway setting said. It now follows the setting.
  • FIX (security): UCP MCP (off by default): an agent could ask lookup_catalog for any number of products and get an answer of any size. A lookup now takes at most 50 products and no tool returns more than 1 MB (both adjustable with filters).
  • FIX (security): UCP MCP (off by default) kept no record of what agents did. Every tool call is now written to an audit log (which agent client, which tool, the result and its duration; arguments only as a fingerprint and a masked summary), kept for 90 days.
  • FIX (security): UCP MCP (off by default) had no request limit. Each address also has a budget checked before authentication (300 calls per minute by default), and a batch request carries at most 20 calls.
  • FIX (security): UCP MCP (off by default) had no request limit. Each agent client now has a budget of 60 tool calls per minute, 600 per hour and 5000 per day (the same as A2A, adjustable with the redsys_ucp_mcp_rate_limits filter); past it, calls get a 429 error.
  • ACP (off by default): the public ACP document announced a limit of 60 requests per minute that was never applied. The announcement is removed.
  • FIX (security): ACP (off by default): its "HTTPS required" check believed an X-Forwarded-Proto or X-Forwarded-SSL header from anyone. These headers now count only from the proxies listed in the "Trusted proxies" setting (A2A > Status). HEADS-UP: behind a proxy or CDN that ends HTTPS, list its addresses there after updating.
  • FIX (security): UCP OAuth (off by default): authorization codes were stored in the database in plain text while tokens were hashed. They are hashed now too.
  • FIX (security): A2A (off by default): after the card authentication step, the shopper could be sent to any address the agent had given, including plain http or internal addresses. Only https addresses on public hosts are used now; otherwise the shopper lands on the order page. The redsys_a2a_sca_return_url filter can narrow this further.
  • FIX (security): UCP MCP (off by default): when a tool failed inside the store, the agent received the internal error text (which can include server paths). It now receives a correlation id; the detail is written to the plugin log.
  • FIX (security): UCP OAuth (off by default): two token requests sent at the same time with the same authorization code could both succeed. The code is now redeemed atomically; only one request gets tokens.
  • FIX (security): Inespay: after checking the notification's signature, the plugin still let unsigned fields of the request fill in values the signed data did not carry (such as the payment id). Only the signed data is used now.
  • FIX (security): Apple Pay and Google Pay marked the order paid without checking that the amount Redsys charged matched the order total, as card and Bizum payments already do. A different amount now puts the order on hold with a note, for you to review.
  • UCP OAuth (off by default): two refreshes sent at the same time with the same refresh token could both obtain a new token pair. The refresh token is now spent atomically; the second request gets invalid_grant.
  • FIX (security): A2A (off by default): when an operation failed inside the store, the agent received the internal error text (which can include server paths). It now receives a generic message with a correlation id; the detail is written to the plugin log.
  • A2A (off by default): the maximum amount set for create_payment and tokenize_card was not applied. Amounts above it are now refused before any order is created.
  • FIX (security): Redsys Manager app: an employee whose WordPress role was lowered to customer or subscriber kept their app profile, and with it access to orders and customer data. Their app profile is now removed when the role changes.
  • FIX (security): The public discovery documents for AI agents (UCP /.well-known/ucp and the ACP well-known document) published the WordPress administrator's e-mail address. They now publish the address set in the new "Support e-mail for AI agents" setting, or none.
  • FIX (security): A2A (off by default): the refund amount above which a store administrator must confirm ("sensitive threshold") was checked refund by refund, so splitting a refund avoided it. It now adds up what the same client refunded on the same order in the last 24 hours. HEADS-UP: a batch of small refunds on one order may now wait for your confirmation.
  • FIX (security): A2A (off by default): a client's IP allow-list could be passed by sending an X-Forwarded-For header with an allowed address. The plugin now checks the connection's own address and believes X-Forwarded-For only from the proxies listed in the new "Trusted proxies" setting (A2A > Status). HEADS-UP: if your site sits behind a CDN or load balancer and an A2A client has an IP allow-list, add the CDN's addresses to that setting after updating, or the client will be refused.
  • FIX (security): A2A (off by default): task streams ignored the client's rate limit, so one client could open enough of them to tie up the shop's PHP workers. Each stream now counts against the limit and a client can hold at most five at once.
  • FIX (security): Switching A2A off in the settings did not stop clients that were already set up. With A2A off, its JSON-RPC endpoint and task streams now answer 503 and no push notification is sent.
  • FIX (security): The Redsys bulk actions in the orders list (immediate charge, bulk refund, approve pre-authorization) now need the same permission as their single-order versions (manage WooCommerce) and only run while their setting is on.
  • FIX (security): A2A (off by default): the push address an agent gives for task notifications could make the shop call its own server or internal network, even over plain http. It must now be https on port 443 of a public host, and notifications use WordPress's safe HTTP transport.
  • FIX (security): ACP webhooks (off by default): a provider could register a webhook pointing at the shop's own server or internal network. A webhook URL must now be port 443 on a public host (a filter allows otherwise for development), webhooks registered earlier that break the rule are no longer called, and deliveries use WordPress's safe HTTP transport.
  • FIX (security): UCP (off by default): the platform profile address an agent sends in its UCP-Agent header could make the shop call its own server or internal network. Only https addresses on port 443 of public hosts are fetched now, through WordPress's safe HTTP transport.
  • FIX (security): UCP webhooks (off by default): a client could register a webhook pointing at the shop's own server or internal network, and a read-only token was enough. A webhook URL must now be https on port 443 to a public host, registering or deleting one needs the checkout write scope, webhooks registered earlier that break the rule are no longer called, and deliveries use WordPress's safe HTTP transport.
  • FIX (security): UCP, MCP and A2A (off by default) accepted an OAuth refresh token as if it were an access token. Only access tokens open those routes now.
  • FIX (security): Agentic checkouts (UCP and ACP, off by default): an AI agent could put on an order products the shop does not sell - drafts, private or out-of-stock products, variable or grouped parents. The order is now refused (422) and names the products.
  • FIX (security): The plugin's "View details" window read the update server's answer with a function that can build PHP objects. It now reads that answer as plain data only.
  • FIX (security): The checkout's 3-D Secure browser-data request could write that data onto any order number. It now writes only onto the visitor's own order and otherwise keeps it in their session.
  • FIX (security): Agentic checkout (ACP, off by default): an order created by an AI agent was attached to any registered customer whose e-mail the agent sent. It now stays a guest order; stores that want the old behaviour can return true from the redsys_acp_link_order_to_customer_by_email filter.
  • A failed or late payment notification (for example the "denied" result of an earlier attempt arriving after the order was paid) could cancel an order that was already paid - in Bizum and in the other Redsys payment methods. A paid order is now never cancelled by a notification; a note records what Redsys sent.
  • FIX (security): One-click buy took the shipping cost and name from the browser, so a logged-in customer could pay less shipping (or none). The shipping is now recalculated by the store and must be one of the options the store offers; a product that needs shipping cannot be bought without it.
  • FIX (security): Agentic catalogues (UCP catalog and ACP product feed, both off by default) listed draft and "Private products", and the UCP single-product lookup returned unpublished products. Agents now only see published products that are not private. A variation of a private product is private too.
  • FIX (security): The Users-screen bulk actions "Request Redsys card" and PayGold did not check that the request came from that screen, so a page on another site could make a logged-in administrator send card-request e-mails (or PayGold operations) to arbitrary users. They now require the Users screen's security token and shop-manager rights. The PayGold handler also stops interfering with other plugins' bulk actions on that screen.
  • FIX (security): Agentic checkout (ACP): revoking an access token did not clear its cached approval, so a revoked token kept working for up to five minutes. Revoking now takes effect immediately.
  • FIX (security): Agentic checkout (ACP, off by default): access tokens generated as "Read only" were accepted for creating, changing and cancelling orders and managing webhooks. They are now read-only.
  • FIX (security): Agentic checkout (ACP, off by default): a checkout session could be read, changed, completed or cancelled by any client that knew its id. Sessions now answer only the AI provider that created them.
  • FIX (security): Agentic checkout (ACP, off by default): a client using a WooCommerce REST API key could claim to be another AI provider and read, delete or add that provider's webhooks. The provider is now taken only from the credential; bearer tokens registered in WooCommerce's agentic settings now resolve to their provider (so ACP webhooks work as intended), and a session with no provider no longer sends its events to every provider's webhooks.
  • FIX (security): Agentic checkout (UCP, off by default): a checkout session could be read, changed, completed or cancelled by any client that knew its id, and the order endpoints skipped the owner check for a token with no user. Sessions now answer only the client and customer that created them, and a token with no user is refused.
  • FIX (security): Agentic checkout (ACP, off by default): an agent could change the address and total of an order that was already paid, cancel it without a refund, or send it to the payment page again. Those requests are now refused (409) once the order is no longer open; a preauthorized order is voided from the store admin, not by an agent.
  • FIX (security): Agentic checkout (UCP, off by default): an agent could still change the items and total of a checkout session after its order was paid, or cancel the paid order without a refund. A session whose order is paid, cancelled or failed can no longer be changed or cancelled.
  • "Private products" (off by default) did not work: products marked private were only removed from the shop listing and could still be viewed and bought by anyone, and the list of allowed users was saved empty. A private product is now hidden (product page, Blocks/Store API) and cannot be bought by anyone outside its list; shop managers always see it. IMPORTANT if you use this option: open each private product and select its allowed users again - earlier versions lost those lists. A notice on…
  • FIX (security): InSite on the Blocks checkout could attach another shopper's in-progress Redsys payment number to a new order, so that shopper's payment confirmation could land on the wrong order. A number that already belongs to another order is no longer attached.
  • FIX (security): The "add payment method" redirect link answered anyone, and when given an order number it rewrote that order's terminal and key settings with the defaults (breaking later refunds on multi-terminal stores). It now only answers the logged-in customer who started adding the card, and never writes order data.
  • FIX (security): The card payment notification set its "already processing" marker before checking the signature, so a forged request could make the store ignore Redsys's genuine notification for a minute and leave a paid order pending. The marker is now set only after the signature is valid.
  • FIX (security): Manager app (off by default): a staff profile allowed to edit customers could also edit an administrator's account, including the e-mail, which is enough to take it over with a password reset. The app's customer screens now only load and edit customer accounts, never staff.
  • FIX (security): Licence activation and update checks talked to plugins.joseconti.com without verifying its TLS certificate, and trusted whatever the reply said about which plugin to update and where to download it. TLS is now always verified, the update offered is always for this plugin, and the download must come over https from the licence server itself.
  • FIX (security): E-mail payment fallback (IMAP/Gmail, off by default): an e-mail whose sender merely contained the Redsys address could mark a pending order as paid, and so could a real Redsys e-mail about a denied payment. Now the sender must be exactly the address set in the settings, and the e-mail must show an approved payment for the order's amount and merchant code; otherwise the order is left as it was and gets a note. If you entered only part of the Redsys address (or only the domain)…
  • FIX (security): Removed an unused InSite REST address (woocommerce-redsys/v1/save_order_data) that let a request carrying only a matching Referer header change the Redsys order number stored on any order, which refunds rely on. The Blocks checkout has not used it since 31.0.4.
  • FIX (security): Agentic checkout (UCP, off by default): an order created by an AI agent was attached to whichever registered customer owned the e-mail the agent sent, which also put that customer's saved cards within reach. The order now belongs to the customer who authorised the agent, and never to someone because of an e-mail address.
  • FIX (security): Apple Pay express stored a temporary marker under a name taken from the browser, and that name could match the markers the plugin reads to confirm payments. Wallet markers (Apple Pay and Google Pay) now live under their own hashed names.
  • FIX (security): Completes the saved-card fix above for the redirect payment page. The card chosen at checkout was also carried into the signed Redsys payment form without checking whose card it was. The form now uses a saved card only if it belongs to the customer paying; otherwise it asks for a new card (a new subscription card when the order has a subscription).
  • FIX (security): Each order keeps the Redsys key it was paid with, so refunds and renewals keep working when several terminals are in use. WooCommerce's REST API returned that key to any integration with a read-only API key. It is no longer included in order or subscription REST responses; it is still stored and used exactly as before.
  • FIX (security): With "Show the Redsys page inside the store" (iframe mode), and for every Bizum Checkout order, the return links printed an order's cancel and order-received addresses, with its private key, to anyone who asked, for as long as the store kept a marker that never expired. They now answer only the buyer who owns the order (the return links sent to Redsys carry the order key for that), and the marker expires after a day.
  • FIX (security): A notification-endpoint link used by the retired 3-D Secure method step sent any visitor to the payment page of the order number in the link, including its private order key. It now only sends the buyer who owns the order there (card and InSite).
  • FIX (security): The extra fields that Apple Pay and Google Pay express buttons ask for (NIF/DNI and similar) stored whatever field names the request carried, on the order and on the customer's account. They now store only the fields your store defines, and never the plugin's internal data. Shops that show express buttons should update.
  • FIX (security): A saved card could be charged by someone it did not belong to. The card is identified in the checkout request by a row number, and the plugin did not check whose card it was, so a crafted request could charge another customer's saved card without the bank asking that customer to confirm anything. Every charge with a saved card now checks that the card belongs to the customer who is paying, and refuses the payment otherwise; a card id that does not exist no longer causes a fatal…
  • In test mode, "Show to this users" limits a gateway to the users you pick. The Blocks checkout ignored it and showed the gateway to every visitor, guests included; the order was then rejected, so the customer saw a payment method that failed when pressed. Every gateway now applies the list in the Blocks checkout as well as the classic one. A developer filter, redsys_gateway_shown_to_user, can adjust the decision. Reported with the cause already located - thank you.
  • Apple Pay and Google Pay (checkout) had the "Show to this users" field but never applied it, in any checkout. They now do.
  • With Inespay, a user on the "Show to this users" list could still be hidden, because the saved list was compared the wrong way. Listed users now see it.
  • With "Pay with One Click" from the product page active, the plugin added two headings - "Terms and Conditions" and "Select Shipping Method" - to every product page, even when nobody had opened those windows, which cluttered the page structure that search engines and accessibility tools read. Those windows are now built only when they are actually opened, and their title is no longer a heading: it names the window for screen readers instead, which the windows for terms and shipping did not do…
  • The script and the styles of "Pay with One Click" from the product page loaded on every product page, including where the button never appears because the option is off or the visitor is not logged in. They now load only where the button does.
Assinar para baixar a versão 32.2.0

Versão 32.1.1

Notas da versão 32.1.1: 1 novidade 1 melhoria 8 correções

Novidade

  • Deleting the plugin now removes its settings - the configuration of every payment method, the Redsys Advanced settings, the licence and the scheduled maintenance tasks - so a shop that uninstalls it is left clean. It never touches customers, orders or subscriptions, nor anything tied to them: saved cards, the order and invoice numbering and payments still in progress are all kept, so reinstalling the plugin carries on where it left off.

Melhoria

  • The MasterPass gateway has been removed, because Mastercard has shut the MasterPass service down and it can no longer take payments. Its settings screen, checkout option, express button colours and block-checkout integration are gone. Orders that were paid with MasterPass in the past are not affected: they keep their details and are still shown as Redsys orders. Its two leftover settings are left in the database untouched.

Correção

  • With the card gateway's "Pay with 1 click", a customer with no saved card who ticked "Save payment information" paid normally, but the card was never saved. The plugin asked the bank for a new card reference while telling it that the reference already existed, and when the bank sent it back the plugin believed its own message and threw the reference away. It now asks for a new card correctly, so the card is saved, and it only asks for one when the customer actually ticked the box. The same…
  • With InSite, one subscription payment could leave the customer with the same card saved twice under "Payment methods". The bank reaches the shop by two routes for the same payment - the answer to the payment itself and a separate notification - and each route saved the card. Every place that saves a card now first checks whether this customer already has that card from that same operation (the same card reference, type and transaction) and reuses it. A card saved again from a different…
  • The "Add a card for Subscriptions" option added in 32.1.0 (Redsys Advanced > Saved Cards) worked the wrong way round: the offer only ever appeared when a subscriptions plugin was active, and the option could only hide it. Products can save a subscription card without any subscriptions plugin, and when that card expired or was stolen the customer had no way to add a new one. The offer now appears whenever a supported subscriptions plugin is active, and also whenever the option is ticked, with…
  • With InSite, saving a new card during an ordinary one-click purchase asked the bank for a recurring (subscription) card instead of a one-click card. The value that should have decided it was never filled in, so every new card was treated as recurring. Orders that contain a subscription from any supported subscriptions plugin, or a product set to save a subscription card, still ask for a recurring card; ordinary one-click purchases now ask for a one-click card.
  • With InSite, a card saved for a subscription could be stored with an invalid type, which made it invisible to anything looking for one-click or subscription cards. It is now always stored as one or the other.
  • When collecting the remainder of a deposit, the plugin charged whichever saved card came first, of any type. It now charges the customer's most recent subscription card - the kind of card meant for charges the shop starts itself, and which also picks up a card the customer replaced from My account. A customer with no subscription card is charged exactly as before.
  • After entering the licence key and pressing "Activate licence", WordPress showed "Sorry, you are not allowed to access this page", although the licence had been activated correctly. The plugin returned to an address where that page does not exist; it now returns to the licence page. Reported by a shop that pointed at the exact line - thank you.
  • Orders paid by bank transfer or by Google Pay (redirection) were reported to AI shopping agents as card payments, because the plugin looked those two payment methods up under the wrong names. They are now reported as what they are.

Versão 32.1.0

Notas da versão 32.1.0: 2 novidades 6 melhorias 19 correções 5 reforços de segurança

Novidade

  • The WooCommerce status report (WooCommerce - Status) now also lists what is switched on in the Redsys "Advanced settings" tab: push notifications, sequential invoices, QR codes, saved cards, order status overrides, conditional rules, subscriptions, e-mail reconciliation, the agentic commerce protocols and the management app API. Credentials are never printed - each one is reported only as set or not set. It is included when you copy the report to send it for support, which is the point: a…
  • You can now decide whether customers are offered "Add a credit card for Subscriptions" in My account - Payment methods. Until now that option appeared by itself as soon as a subscriptions plugin was active, with no way to remove it, which is not what every shop wants: on a shop where the card for a subscription is always captured during the purchase, it only invited customers to store a card nothing would ever charge. The new switch is in Redsys - Advanced settings - Saved Cards, it starts…

Melhoria

  • When a subscription renewal fails, the note added to the order now says exactly which step failed and which merchant code and terminal were used for the attempt. Until now all six possible failures wrote the same uninformative note, which made a failed renewal almost impossible to diagnose without access to the store - especially on stores where the debug log is not being written.
  • When Apple Pay cannot validate the shop with Apple, the log now records Apple's own explanation and whether the certificate files can be read. Apple answers with a generic "Expectation Failed" and puts the real reason in the body of its reply, which was never being recorded, so those failures used to be a dead end.
  • The distributed plugin no longer contains the project's own development and build scripts, its local test environment configuration, its editor and git-hook directories, its developer README or an internal security review document. None of it was ever loaded when the plugin runs, but none of it belongs on a shop's server either. What the package contains is now checked automatically, before every release, against a list of what the plugin really ships, so something added to the project in the…
  • The e-mail reconciliation job now exists only while that feature is switched on, and only once. Before, it was created on every shop and woke up every five minutes doing nothing.
  • All the translations are complete again. Sixty-nine texts added by recent versions were still showing in English - settings labels, the status report, and a few messages a shopper can see. Spanish, Catalan, Basque, Galician, French and Portuguese are back at one hundred per cent.
  • The token that guards the "add a card" link is now compared in constant time, like every other secret this plugin compares. Timing that comparison over the internet is not a practical attack, so nothing was exploitable; the inconsistency was the defect, because this was the one comparison left behind when the rest were migrated during the signature work.

Correção

  • With InSite, paying with a card the shopper had saved could take the money and still show the order as failed. When the bank approves such a payment without asking the shopper to confirm with their bank app - which is what happens with a saved card - the plugin was looking for the result in the wrong place, found nothing, and treated "nothing" as a refusal. The charge had already gone through, so shoppers who were told the payment had failed paid a second time and were charged twice. The…
  • On the card gateway, a payment made with a saved card was completed on the strength of an authorisation number alone, without checking the bank's actual answer beside it. A refused payment that still carried something in that field would therefore mark the order as paid, and the shop would send the goods without having been paid. Both are now required to agree before an order is completed. If the bank's answer is missing altogether the payment is not completed, because there is nothing left…
  • On stores using certain checkout plugins - Fluid Checkout among them - every payment was refused by Redsys with the error SIS0574. The bank requires a short description of the shopper's browser with each payment (its language, its screen size and similar), which the plugin collects through hidden fields it adds to the checkout. Those fields were being added at the moment the card gateway was built, which on those stores happens after another plugin has already asked WooCommerce for the…
  • If a payment was cancelled or refused, the shopper came back to the shop but the order was left pending and the basket was not restored. The address the plugin gave the bank to send the shopper back to was written in the form used for links inside a web page, not the form used for a real address, so the shop received the return without the order reference, its number or its security token and had nothing to cancel. It affected Bizum, Google Pay, Apple Pay, direct debit, bank transfer, InSite…
  • In the pop-up (modal) payment mode, cancelling a payment did nothing and the shopper was left on the cart with the order still pending. The address the plugin sent the browser to was being written into the page in a way the browser reads as a link inside a document rather than as a web address, so everything after the first parameter was discarded - the order reference, its number and its security token all disappeared, and WooCommerce had nothing to cancel. The same flaw affected the address…
  • The checkout could die with a critical error, instead of sending the shopper to the bank, for a logged-in customer whose customer record had never been changed since it was created. The plugin builds a set of security data for the bank on every payment, and one of the fields is the date the customer account was last modified - which WooCommerce leaves empty for an account that has never been touched, typically one created by an import, a migration, or automatically by another plugin. The…
  • Redsys and the other gateways could disappear from the checkout for everyone, including ordinary shoppers, on stores where the "show only to these users" list in test mode had never been filled in. The plugin read that empty setting as "show it to one user whose id is nothing", which matches nobody, so the payment method was hidden from every visitor. It only affected stores whose settings were written by something other than the settings screen - an import, a migration, or the plugin's own…
  • Subscriptions paid with Apple Pay or Google Pay by a customer without an account never obtained the recurring payment permission from the bank, so the first renewal failed with a note saying there was no card. It happened on stores where the general "allow customers to create an account during checkout" option is switched off, which is common on stores that allow guest checkout: the wallet payment paths never saw WooCommerce Subscriptions' own override of that option, so no account was created…
  • The block checkout's payment script was built against a version of React that WordPress itself does not accept. A development-only dependency pulled a newer React into the build, and WordPress rejects elements produced by it, so the payment method could fail to appear on the block checkout. The build now pins the version WordPress uses and the script has been rebuilt.
  • The cart and the checkout could become noticeably slow, for logged-out visitors too, on stores with saved cards or subscriptions. The plugin's internal helper WCRed built a brand new copy of its global object every single time it was called, and that object registers three WordPress hooks the moment it is built. WordPress does not replace those hooks, it adds them, so on a store where the helper is called once per saved card or subscription the same three checks ended up registered hundreds of…
  • On a small share of stores the Agentic Commerce (UCP) message-signing key was written in a form that could never be used, so every signature check against it failed and the published key document did not follow the standard. When the plugin created that key, one of its two coordinates occasionally came back from OpenSSL one byte shorter than the standard requires - about 1 store in 135 - and the plugin stored it as it was instead of padding it. From that moment the store could not verify its…
  • On shops running PHP 8.0 or older, switching on the e-mail reconciliation broke the page with a server error instead of simply not working. The plugin now checks first and leaves a clear note in its log. The feature itself still needs PHP 8.1.
  • Background jobs were piling up into dozens of copies of themselves in the WooCommerce scheduled actions list. Fixed everywhere the plugin schedules anything, and the copies already there are cleared automatically.
  • A notification to the mobile app could be lost without any error if it was sent at the wrong moment.
  • PHP warnings appeared in the server log on every visit to the "pay for order" page, from the Apple Pay and Google Pay gateways. Nothing was broken for shoppers, but the debug log for those gateways was not recording anything from that step - so anyone trying to diagnose a problem there was looking at a fault, not at silence. Reported by a merchant, and found in three gateways rather than the one reported - thank you.
  • Turning the debug log on to look into a card payment problem produced warnings instead of the information you turned it on for.
  • The "Connect with Google" button in the e-mail reconciliation settings was never displayed. Granting access was already possible by filling in the Google details and pressing "Save changes", so this restores a shortcut rather than unlocking the feature.
  • The plugin sent the shop an e-mail saying "Redsys is not sending tokenization fields" after payments in which Redsys had sent every one of them. The check behind that notice tested a variable that does not exist anywhere in the plugin, and a test on something that does not exist is always true, so the warning went out on every payment that saved a card. Merchants were taking it to their bank, which correctly answered that the terminal was fine. The notice now reports only real absences, and it…
  • Searching the Redsys tokens screen (WooCommerce - Redsys tokens) by e-mail or username could not find any card saved after the first twenty-five. The screen asked the database for one page of tokens and then searched inside that page, and since it asked for them in no particular order, that page was always the twenty-five oldest tokens in the shop - so the recently saved cards, which are the only ones anybody looks for, were unreachable. The search now runs in the database, over every token…

Segurança

  • The plugin was writing the address of every shopper's order-received page into its own log file on every payment, and that address contains the order key - the private token that WooCommerce puts in the shopper's payment link and that this plugin requires before it will show an order. Anyone able to read the log file could therefore open those orders and see the name, email, telephone and addresses on them. It happened whether or not the shop had switched debug logging on, because this one…
  • The page that forwards a shopper to Redsys (and to Bizum) accepted any order number typed into its address, without checking that the person asking for it was the person who placed that order. Because order numbers run in sequence, someone could step through them and read the data the plugin sends to the bank for other customers' orders: name, email, telephone and the billing and delivery address, together with the amount and the description of what was bought. No card number, no security code…
  • The three preauthorization buttons in the order screen (authorise, cancel, charge a deposit) and the PayGold customer search accepted their requests without a security token. The permission check was already in place, so only a shop manager or administrator could ever use them, and nobody else could have run them - but an administrator who was already logged in could have been tricked into firing one from another website without noticing. All four now carry and verify a WordPress security…
  • The Agentic Commerce Protocol could end up switched on without anyone choosing it, on shops that update automatically. It publishes addresses that machines can talk to, so it is meant to be off unless you turn it on - and now it is. If you did switch it on, nothing changes for you.
  • The Google library bundled with the plugin has been updated, fixing two flaws in the part that makes network requests.
Assinar para baixar a versão 32.1.0

Versão 32.0.0

Notas da versão 32.0.0: 5 novidades 1 melhoria 2 correções

Novidade

  • Manage your store from a native app. This release turns on the management app API that until now shipped hidden inside the plugin. Your store can be connected to PackDesk, the native macOS management app, to work with orders, refunds, products and customers without opening the WordPress dashboard. The API is served under the redsys-manager/v1 namespace and is strictly opt-in: it is OFF by default, it requires HTTPS and an active license, and no app can reach the store until a merchant enables…
  • A new "Behaviors towards the APP" section in the Redsys advanced settings (WooCommerce - Settings - Redsys - Advanced Settings) to control how the store behaves towards the app: enable or disable the API, allow or restrict refunds for the Customer service profile (refunds are limited to the Administrator profile by default), require a minimum app version, and set the requests-per-minute limit per employee (default 300, set 0 to disable it).
  • A per-user "App profile" on the WordPress user edit screen, so each employee who connects from the app operates under a profile - for example Administrator or Customer service - that decides what the app lets them see and do, including whether they may issue refunds.
  • A new "Apps and Plugins" section in the Redsys advanced settings: a read-only overview of the native app and the rest of the plugins, websites and skills, all reachable from one place.
  • PackDesk is now published on the Mac App Store, and the official "Download on the Mac App Store" button is shown at the top of the "Behaviors towards the APP" section and in the featured-app area of "Apps and Plugins", so the app can be installed straight from the store settings. The button uses Apple's own artwork in the language of the administrator viewing it - English, Spanish, Catalan, French or Portuguese, with English used for Basque and Galician because Apple does not publish a badge…

Melhoria

  • Compatibility declared with WooCommerce 11. The plugin's "WC tested up to" header now reads 11.0, so WooCommerce no longer warns that the gateway has not been tested with the version you are running. The minimum supported WooCommerce is unchanged (7.4).

Correção

  • The product QR code did not appear on stores whose media library is offloaded to an external service such as Cloudflare Images. The QR image was registered in the media library correctly, but the plugin saved and displayed a URL it had built by hand from the local uploads folder instead of asking WordPress for the attachment's real URL, so on an offloaded store that address pointed at a file that is no longer served locally and the image was broken. The QR URL is now resolved through the media…
  • A Bizum payment could be charged at the bank yet leave the order pending, with the log showing "Signature verification failed in successful_request". The order-completion step in one of the two Bizum gateways verified the bank notification with the gateway's plain configured signature key, while the operation had been signed with the per-order key actually used for it - as happens on stores with a per-user or dual/test terminal, or the bizum_modify_data_to_send filter. The notification passed…
Assinar para baixar a versão 32.0.0

Versão 31.0.7

Notas da versão 31.0.7: 1 melhoria 14 correções

Melhoria

  • Apple Pay and Google Pay now always use the SECURE terminal, and the "Terminal type" selector has been removed from both wallets' settings. For a wallet the terminal type only affected the first payment (subscription renewals are charged through the card/redirection gateway, which keeps its own terminal setting), and the secure terminal already does everything that first payment needs: it charges and, for subscriptions, it requests the recurring token. The mixed terminal paid through a path…

Correção

  • Subscription products from Advanced Subscriptions for WooCommerce were never detected as subscriptions. The check guarded on function_exists( 'aswc_check_product_is_subscriptionn' ) - one letter n too many - while the body called the correctly spelled function, so check_subscription_aswc_checkout always returned false regardless of the product. The misspelling appeared exactly once in the whole plugin and dated from the rename of the sjcfwc_ prefix to aswc_. As a result the card used for those…
  • Any anonymous visitor could trigger a fatal error through admin-ajax.php. The plugin registered the AJAX action check_token_insite_from_action, for both logged-in and logged-out visitors, pointing at a method of WC_Gateway_InSite_Redsys that does not exist - the implementation is called check_token_insite_from_action_checkout, which is also the action name the JavaScript actually posts and which was registered correctly on the next two lines. Requesting…
  • The Redsys Tokens admin page registered a form handler that was never written. admin_post_redsys_tokens_search pointed at a process_search_tokens method that does not exist, so visiting admin-post.php?action=redsys_tokens_search produced a fatal for any logged-in user. Searching on that page has always worked through the page itself, not through that handler, so the obsolete registration has been removed and nothing changes for the user.
  • Twelve user-facing texts said "Redys" instead of "Redsys" - nine email titles shown in WooCommerce, Settings, Emails, and three in the Bank Transfer gateway description. The corresponding translations in Catalan, Basque, Galician, Spanish, French and Portuguese have been updated in the same release, so no translated text is lost.
  • A malformed or tampered bank notification could fill the log with "Trying to access array offset on null" warnings. When the notification could not be decoded, the routine that reads the order number from it accessed the decoded data anyway, and its fallback read an undefined index whenever neither spelling of the order key was present. It now returns an empty order number, which the callers already treat as an unresolvable notification.
  • With the order number format set to "Number created by WooCommerce only with zeros" (simpleorder), adding a payment method could be rejected by Redsys as a repeated order number (SIS0051). Real orders and card-additions were numbered from the same 12-digit zero-padded space: an order with id 42 was sent as 000000000042, and so was the 42nd card-addition, because the add-card counter started at 1 and walked straight through the range of existing order ids. The same collision had a second and…
  • The InSite tokenization number could collide with the default order number format. The number InSite uses to request the card token before the order exists begins with 1, while the default format ("3 random numbers followed by zeros") builds an order number from a random 1-999 prefix: whenever that random prefix came out as exactly 100 and the InSite counter matched the order id, both produced the same value (for example 100000000042 for order 42). Unlike the previous item this one did not…
  • Two card-additions started at the same instant could be issued the same number and save the card onto the wrong account. Both internal counters were read and written back as two separate operations, so two simultaneous requests read the same value, incremented it to the same number, and the second request overwrote the first request's stored user id - the number is the only key those operations have, so the card ended up attached to whichever user wrote last. The counters now claim each value…
  • Card-addition and InSite tokenization operations could not be traced from the logs. The number reserved for a card addition was never written to the log together with the customer it belonged to - the only link was a transient that expires in 48 hours - so a number seen later in the Redsys panel or in a log could not be matched to anyone. Worse, the card-addition flow logged its number under a variable named $order_id, so the log stated that an operation was a given order when no order existed…
  • A Redsys email arriving after a card-addition had expired could modify an unrelated order. When the IMAP email fallback processes a notification whose 48-hour card-addition transient is already gone, it resolved the number to an order id with a legacy heuristic that strips the first three characters - which, for a card-addition number, returned the id of a real order and wrote the transaction data onto it. Numbers in the reserved prefixes are now recognised as such and never resolve to an…
  • Apple Pay chosen as a normal payment method in the block-based (Blocks) checkout - not the express button - produced a paid order with no customer data at all: no first name, surname, email, phone or country, and DS_MERCHANT_TITULAR sent blank to Redsys. The payment was authorised regardless, so the store was left with money taken and nobody to ship to. Introduced in 31.0.6. The fix released in that version for Apple Pay Express - not handing the order to WooCommerce Blocks as its Store API…
  • Apple Pay chosen as a normal payment method in the block-based checkout could fail to pay when the shopper filled the address in on the checkout page. The Apple Pay sheet showed the pre-tax amount (for example 30.00) while the server sent the real total to Redsys (36.30), and the payment was rejected on the mismatch. The amount shown in the sheet was calculated once, when the checkout page was rendered, and never updated afterwards - so on a block checkout, where taxes and shipping are…
  • Apple Pay chosen as a normal payment method in the block-based checkout could open the Apple Pay sheet with required checkout fields still empty, taking the customer through Face ID or Touch ID only to fail afterwards, and left WooCommerce's own "Place order" button visible next to the Apple Pay button so it was not clear which one paid. The required fields are now checked before the sheet opens - the missing ones are marked in the checkout form instead - and the "Place order" button is hidden…
  • Apple Pay chosen as a normal payment method in the block-based checkout still produced a paid order with no customer data - no name, email, phone or country, DS_MERCHANT_TITULAR blank - when the gateway's terminal type was set to "mixed" instead of "secure". The fix earlier in this version populates the order from the checkout form on the payment page, but a mixed terminal does not go through the payment page: it charges through Redsys directly in the same step, so there was no page load to…

Versão 31.0.6

Notas da versão 31.0.6: 2 correções

Correção

  • The ACP webhook dispatcher no longer floods the logs with "as_next_scheduled_action / as_schedule_recurring_action was called before the Action Scheduler data store was initialized" notices. Redsys_ACP_Webhook_Dispatcher::init runs on plugins_loaded and scheduled the delivery worker straight away: at that point WooCommerce has already defined the as_* functions, so the function_exists guard passed, but Action Scheduler does not initialise its data store until the action_scheduler_init hook…
  • Apple Pay Express orders were saved without any of the customer data - no first name, surname, email, phone, billing or shipping address - and were recorded as guest purchases, even though the payment itself went through correctly and the order was marked as paid. Google Pay Express was never affected. The express flow registered the order it had just created in the WooCommerce session under 'store_api_draft_order', which tells WooCommerce Blocks that the order is a disposable draft it owns.…

Versão 31.0.5

Notas da versão 31.0.5: 1 correção

Correção

  • 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…

Versão 31.0.4

Notas da versão 31.0.4: 1 correção

Correção

  • Subscription renewals (with any subscription plugin) now respect the configured Redsys order-number type and no longer fail on retry with "número de pedido repetido" (SIS0051). Two problems are fixed. First, the renewal charge generated the Redsys order number ignoring the "Type of order number" setting (redsysordertype/subfix): it always fell back to the default random scheme instead of the type configured for the gateway, unlike the initial checkout payment. It now passes the gateway so…

Versão 31.0.3

Notas da versão 31.0.3: 1 novidade 1 melhoria 11 correções 1 reforço de segurança

Novidade

  • "Apps and Plugins" section under Redsys Advanced -> Redsys Advanced Settings. A read-only landing page that showcases the native macOS management app (with download, requirements and "coming soon" platforms) and lists the rest of the free and premium plugins, websites and portals, Claude skills and developer profiles by José Conti, each grouped by type with a link. Every list is filterable (redsys_apps_plugins_mac_app, redsys_apps_plugins_free, redsys_apps_plugins_premium…

Melhoria

  • Removed the noisy debug console.log output from the production (minified) frontend scripts (Apple Pay, Google Pay, capture-order-id and the express-checkout modals). The Apple Pay express script in particular logged on every DOM change (it watches the whole document for its button), which flooded the browser console on the Blocks checkout. The minified files now strip console.log/console.warn/console.info/console.debug while keeping console.error; the un-minified sources are unchanged for…

Correção

  • Bizum notifications were rejected with a signature verification error, leaving the order unpaid even though the payment had been authorized at Redsys. The merchant key and the order number were correct (the request signature matched perfectly), but the notification signature is an HMAC computed over the Ds_MerchantParameters string exactly as received, and Bizum notifications arrive with the trailing base64 "=" padding stripped while Redsys signs over the canonically padded value, so the…
  • Card and wallet notifications could be rejected with a "signature mismatch", so the customer returning to the thank-you page (and the server-to-server IPN) failed to mark the order as paid until a later IPN retry happened to succeed; refunds and PayGold links paid later could stay unconfirmed. Two padding issues are involved: besides the Bizum payload padding above, Redsys delivers the notification signature (Ds_Signature) in URL-safe base64 with the trailing "=" stripped, while the locally…
  • Bizum notifications on multi-currency / dual-terminal stores (those routing each order to a different terminal through the bizum_modify_data_to_send filter or a conditional rule) now resolve the real per-order signing key before verifying the signature (the customer-adjusted settings key, the transient saved when the payment form was generated, or the _redsys_secretsha256 order meta), and an unverifiable notification is rejected with HTTP 400.
  • InSite card payments that required a 3DS challenge showed a blank verification screen in Safari (iPhone/Mac), so the customer could not enter the SMS code/PIN and the payment failed (the same flow worked in Chrome). The challenge itself was already a full-page, top-level navigation, but before it the plugin redirected the browser to the issuer's 3DS Method URL (threeDSMethodURL) to fingerprint the browser, and Safari's Intelligent Tracking Prevention blocks the third-party cookies that step…
  • When an InSite card payment failed because a required checkout field was missing or its data did not match (for example an empty surname produced a "signature mismatch"), the error message blamed the card ("...enter your card details again"), so customers thought their card had been rejected and abandoned the order. The message is now neutral and points to the checkout fields first: it asks the customer to check that all the checkout fields (name, surname, address, etc.) and the card details…
  • Refunds and delayed payments of orders with large order IDs (the "1 billion bug" already fixed for instant checkout) were recorded against the wrong order, or not recorded at all. The Redsys notification (IPN) recovers the WooCommerce order ID from the order number through clean_order_number, which first looks up a transient saved when the order number was generated and otherwise fell back to a substr/ltrim heuristic that drops the high-order digits of IDs with 10 or more digits. That…
  • InSite card payments on the block-based (Blocks) checkout failed the FIRST time with "msg18" (the customer saw "check that the checkout/card fields are filled in") and only worked on the second attempt. The Redsys InSite SDK requires the page to send a "domain" message to the card iframe so Redsys can validate the merchant; the SDK does this through an inline onload="setMerchantDomain(0)" on the iframe. The block script overwrote that handler with its own iframe.onload (used to size the…
  • InSite Blocks checkout - made the Redsys postMessage handling more robust and added end-to-end diagnostics. The handler now accepts messages from any Redsys subdomain (sis.redsys.es, sis-t.redsys.es, sis-d.redsys.es) instead of requiring an exact host/port match (Redsys posts from more than one host), removes any listener left by a previous render so a single token cannot trigger multiple submissions, and clears the token/error fields after reading them so a stale re-fire cannot resend. When…
  • InSite card payments on the block-based (Blocks) checkout were rejected by Redsys with SIS0574 ("EMV3DS authentication operation rejected, browserUserAgent not indicated"): the 3DS browser fingerprint (user agent, screen size, language, colour depth, timezone) never reached the order, because the hook that normally copies it onto the order (woocommerce_checkout_create_order) does not run on the Store API (Blocks) checkout. The InSite Blocks form now collects the fingerprint and sends it…
  • InSite card payments on the block-based (Blocks) checkout were rejected with an "error code without token" (shown to the customer as "check that the checkout/card fields are filled in"), so the card could not even be tokenised after a few attempts. Because the order does not exist yet on the Blocks checkout (order id 0), the prepared Redsys order number was generated from id 0, which produced an almost constant value - only ~999 possible numbers, all ending in nine zeros - and Redsys rejects a…
  • InSite card payments on the block-based (Blocks) checkout failed: the customer saw a misleading "check that the checkout/card fields are filled in" error and the order was never paid (the browser console showed a 404 on the save_order_data request). The cause is that current WooCommerce no longer creates the order until the customer presses "Place order" - during card entry the Blocks checkout store returns order id 0 - so the InSite operation token (idOper) and the prepared Redsys order…

Segurança

  • Removed a notification signature-bypass that could let an anonymous request mark an order as paid when the SHA-256 secret was left empty/misconfigured. The Redsys IPN listener (public wc-api endpoint) had a legacy fallback that, when no secret was configured, accepted a notification solely because the posted Ds_MerchantCode matched the merchant FUC - a public, non-secret value an attacker can supply. That merchant-code-only acceptance has been removed from every gateway (Redirection, Bizum…
Assinar para baixar a versão 31.0.3

Versão 31.0.2

Notas da versão 31.0.2: 2 melhorias 3 correções 3 reforços de segurança

Melhoria

  • The redsys_modify_data_to_send filter now receives 'context' => 'add_payment_method' and 'user_id' in the data array for the "Add payment method" flow, so custom snippets and conditional rules can route the tokenization to the right terminal (terminal + SHA256) without relying on an order that does not exist in this flow.
  • Updated all translations.

Correção

  • Adding a card from My Account ("Add payment method") on multicurrency stores could be rejected by Redsys with a currency error. The request was sent with the customer's session currency (e.g. ARS, 32) but the default terminal, which is configured for another currency (e.g. EUR, 978). Card tokenization is a zero-amount operation with no order behind it, so if no filter or conditional rule routes the request to another terminal, the store base currency is now sent, always matching the default…
  • Adding a card from My Account (or via the profile email link) always registered the card at Redsys as one-click (DS_MERCHANT_COF_TYPE 'C'), even when the customer selected the subscriptions option. The token type was read from the wrong internal key, so 'R' was never sent. The token was stored correctly as R in WooCommerce, but the COF agreement was created as C at Redsys, which could cause some issuers to decline later subscription renewals (MIT) made with those tokens. Cards added with the…
  • Payments made with a saved card (token R) and subscription renewals did not honor the preauthorization settings. With "Preauthorize all orders" enabled (or a product marked for preauthorization), the charge was executed as a regular sale (type 0) but the order was still marked as "Preauthorized", so confirming the preauthorization later failed at Redsys with SIS0059 ("No operation exists on which to perform the confirmation"). Both flows now send a real type 1 preauthorization that can be…

Segurança

  • The merchant SHA-256 secret key is no longer written in plain text to the WooCommerce debug logs. All debug entries now mask the key, showing only its last 4 characters, via the new WCRed ->mask_secret helper. Applied across all gateways (Redirection, InSite, Bizum, Google Pay, Apple Pay, PayGold, Direct Debit and the Blocks support classes).
  • Redsys notification (IPN) signatures are now verified with hash_equals (constant-time comparison) in all notification handlers, unifying them with the verification already used by InSite and the REST client. Hardening against timing attacks.
  • The single-token delete AJAX handler in the tokens management screen now requires the manage_woocommerce capability in addition to the nonce, matching the bulk-delete handler.

Versão 31.0.1

Notas da versão 31.0.1: 1 melhoria 1 correção

Melhoria

  • The countdown in the Bizum payment-page modal showed 7 minutes. It now correctly shows 5 minutes, and the server-side time control that redirects to the checkout has been adjusted accordingly (60 iterations * 5 seconds = 5 minutes).

Correção

  • Bizum on the payment page (Bizum InSite) did not send the description to Redsys. The actual charge from the modal is made through the REST API (trataPeticionREST), and that request did not include the DS_MERCHANT_PRODUCTDESCRIPTION parameter, so the configured "Redsys Description" (for example "Order ID") reached the Redsys panel empty. The description is now computed from the selected setting and sent in the REST request.
Assinar para baixar a versão 31.0.1

Versão 31.0.0

Notas da versão 31.0.0: 12 novidades 3 melhorias 10 correções

Novidade

  • A2A (Agent2Agent) protocol surface. Opt-in (disabled by default). Publishes an Agent Card at /.well-known/agent-card.json and a JSON-RPC 2.0 endpoint at /wp-json/wc-redsys-a2a/v1/rpc with seven skills: query_payment_status, create_payment, capture_payment, refund_payment, list_payments, tokenize_card and recurrent_charge. Authentication reuses the UCP OAuth 2.1 + PKCE authorization server with a2a:payments:* scopes (and an optional sandbox bearer for testing under WP_DEBUG).
  • Resumable Server-Sent Events stream at /wp-json/wc-redsys-a2a/v1/tasks/{taskId}/stream for live task updates, with Last-Event-ID resume and 15s heartbeats.
  • Signed outbound push notifications to a client-registered push_url. X-A2A-Signature: sha256= over., retries 1m/5m/30m/2h (4 max), delivered via Action Scheduler.
  • Admin tab "A2A (Agent2Agent)" under Redsys Advanced -> Agentic Commerce, with Status / Clients (create / revoke / rotate sandbox bearers) / Limits & modes (max_amount, sensitive_threshold and exposed payment modes) / Confirmaciones (approve refunds or recurrent charges parked at input-required).
  • Per-skill ceilings - max_amount is a hard cap that fails the task with limit_exceeded; sensitive_threshold parks the task at input-required until an admin confirms it. Both default to no cap (opt-in).
  • Append-only audit log at wp_redsys_a2a_audit_log. Raw payloads are never stored - only a SHA-256 hash plus a sanitized one-line summary that masks PAN, tokens, secrets and email local-parts.
  • Self-healing storage. The four A2A tables are recreated on demand by every store's ensure_table so a dropped table never fatally errors.
  • Support for AI shopping agents (ChatGPT, Claude, Gemini, Perplexity and others). AI agents can now discover your products, build carts, complete checkouts and receive order updates from your store. Both the OpenAI/Stripe ACP standard and the open UCP standard (backed by Google, Shopify and others) are supported, and each one can be enabled or disabled independently.
  • New "Agentic Commerce" subsection under Redsys Advanced settings, with per-feature toggles (carts, discounts, fulfillment, buyer consent, dynamic client registration, etc.) and one-click buttons to test the agent discovery, OAuth and webhook flows.
  • Webhook signing with a "Rotate signing key" button. Rotated keys remain valid for 7 days so existing integrations keep working during the rollover.
  • Express custom fields modal (Apple Pay / Google Pay) now also picks up fields registered through the Blocks API on classic checkouts, so NIF/DNI and similar fields always appear regardless of which checkout you use.
  • Optional "Approve Pre-authorization" bulk action for the orders list (Redsys Redirection). Disabled by default for security; enable it under the gateway settings only if you need to confirm preauthorized orders in bulk.

Melhoria

  • Enabling this support does NOT mean AI assistants will start completing purchases in your store from day one. The full agent-driven checkout flow is still rolling out, especially in Europe, where SCA/3DS, PSD2 and GDPR consent requirements mean that most agents today stop at product discovery or pre-cart and hand the final payment back to the customer. Your store is ready for the day each agent activates the full flow in your market.
  • Express custom fields modal now prefetches its configuration when the page loads and starts Apple Pay synchronously on click, fixing cases where iOS Safari aborted the payment sheet.
  • Product page Express custom fields use the modal again by default. The inline form introduced in 30.4.1 is now opt-in via a filter.

Correção

  • FIX [Critical]: Subscription renewals could fail with Redsys SIS0502 ("Id Oper not matching") on hosts running Redis, Memcached or other persistent object caches. Two parallel renewal workers could send two different order references to Redsys for the same subscription, causing the renewal to fail and to be retried many times. The duplicate-payment lock and the order reference are now stored in a way that is reliable regardless of the cache backend. Affects the Redsys Redirection and InSite…
  • InSite subscription renewals had no concurrency guard at all (the lock was deleted on errors but never created). The same protection used by the redirect gateway is now applied to InSite renewals too.
  • Internal cached state used during checkout (3DS data, saved-card identifier, signature cache, OAuth state, IMAP scratch state, etc.) is now stored in a way that works correctly on hosts with persistent object caches. Previously, on misbehaving caches this state could silently disappear mid-checkout and cause SIS0502 errors.
  • Apple Pay and Google Pay Express buttons (block checkout and product page) failed on iOS Safari with "Must create a new ApplePaySession from a user gesture handler" when the Express custom fields modal was enabled. The modal no longer consumes the user's click before launching Apple Pay.
  • Autonomos Premium IRPF was being miscalculated in Express Payment (Apple Pay / Google Pay) on the product page when the customer chose the user type in the Express modal, because the modal save raced against Apple Pay's first server callback. The user type is now sent in-band with every Express Pay request so totals are always correct.
  • On product pages with virtual products, the Apple Pay sheet briefly displayed the correct total (subtotal + tax) and then reverted to the pre-tax product price. The shipping callback now keeps the latest total returned by the server.
  • Saving the Agentic Commerce settings used to silently discard the WooCommerce "Save changes" submit because of nested HTML forms. The settings page has been restructured and all single-action buttons (test discovery, test OAuth, webhook actions, etc.) now work correctly alongside the main Save button.
  • Apple Pay and Google Pay Express buttons on the product page assigned the wrong shipping zone when the customer's region was restricted by province. Apple/Google Pay send the localized state name (e.g. "Barcelona") in administrativeArea, but WooCommerce shipping zones match by state code (e.g. "B"); the country-by-state zone failed to match and the cart fell through to a more expensive zone (e.g. "Rest of Europe"). State names are now normalized to WooCommerce state codes before the shipping…
  • InSite Blocks checkout could create duplicate orders when Redsys emitted the same payment token postMessage more than once (or when the save ran concurrently). A guard now prevents duplicate/concurrent order creation and is reset if the payment form is refreshed after an error.
  • InSite REST debug logging referenced the wrong object to read the debug flag, so the "REST trataPeticion" payload could be logged (or skipped) regardless of the gateway's own debug setting. It now uses the gateway's own debug flag.

Versão 30.4.1

Notas da versão 30.4.1: 4 novidades 6 correções

Novidade

  • "Redsys email to customer" toggle in Redsys Advanced Settings → General to control whether DS_MERCHANT_EMAIL_TITULAR is sent to Redsys. When enabled and the Redsys terminal is configured to notify customers, Redsys sends its own purchase confirmation email to the buyer. Disabled by default, WooCommerce already sends its own order email, so existing installations stop forwarding the customer email to Redsys after the update. Applied to both Redsys Redirection and InSite gateways (classic and…
  • Inline Express custom fields on the product page. When the feature is enabled and there are fields to collect, the form is now rendered above the Apple Pay / Google Pay buttons instead of in a post-click modal, with debounced auto-save to session. The click handler validates locally and starts ApplePaySession.begin synchronously, preserving the iOS user gesture.
  • Inespay periodic mandate now sends the recurring amount of the subscription instead of the parent order total. The gateway reads the recurring price from WooCommerce Subscriptions, SUMO Subscriptions, YITH WooCommerce Subscriptions, Subscriptions for WooCommerce (WP Swings) and Advanced Subscriptions for WooCommerce, and falls back to the order total only when no subscription amount can be detected. The order note created on mandate creation now includes the recurring amount that was actually…
  • Advanced Subscriptions for WooCommerce (ASWC) support in Inespay, the gateway detects the subscription id from order meta (aswc_subscription) and reads frequency, next payment date, end date and recurring amount via aswc_get_meta_data to build the periodic mandate.

Correção

  • Apple Pay Express button on the product page failed to open the payment sheet on iOS Safari mobile when the Express custom fields feature was enabled. The pre-payment AJAX call (modal lookup or modal save) ran between the click handler and ApplePaySession.begin, invalidating the iOS user-activation gesture so Safari silently aborted the session. The button still worked on desktop because desktop Safari is more permissive about gesture propagation.
  • Express custom fields modal AJAX no longer fires when there are no fields to collect on the current page. The product page now precomputes whether any classic or Blocks-registered additional fields exist and disables the modal lookup entirely when the field set is empty, avoiding the gesture-breaking AJAX even on pages where the feature is enabled but no fields apply.
  • Inline Express custom fields on the product page now try both Blocks and Classic contexts when reading additional fields, so fields registered through the Blocks API are also rendered on classic product pages.
  • Inespay return handler now keeps the intermediate "Creating the mandate…" screen visible for a few seconds even when the periodic mandate link is already known on first load, so customers can read what is happening before being redirected back to Inespay to authorize the recurring mandate.
  • Limited Inespay and Google Pay Redirection gateway icons to the same maximum size as Google Pay (max-width 110px, max-height 40px) in the classic checkout, preventing oversized logos when the bank-supplied image is too large.
  • PHP warnings "Undefined variable $ship_address_usage / $ship_address_usage_ind" in class-wc-gateway-redsys-psd2.php when a guest customer (not logged in and no user id) checked out with a shipping address. Both variables were only initialized inside the logged-in branch but read in the outer block; they now default to first-use today, matching the existing else-branch behavior.
Assinar para baixar a versão 30.4.1

Versão 30.4.0

Notas da versão 30.4.0: 1 novidade 2 melhorias 8 correções 1 reforço de segurança

Novidade

  • Subscriptions section in Redsys Advanced settings to configure credentials and behavior for subscription renewal payments.

Melhoria

  • SECURITY [High]: Added missing cryptographic signature verification in successful_request for 9 payment gateways: Apple Pay, Bizum Checkout, Bizum Redirect, Google Pay Checkout, Google Pay Redirect, Direct Debit, MasterPass, PayGold, and Bank Transfer. Without this check, payment notifications could be forged to complete orders without actual payment.
  • SECURITY [Low]: Fixed unauthenticated access to order status and user data.

Correção

  • SUMO Subscriptions renewal orders failed because sumo_save_subscription_payment_info was called with 'payment_method' => 'insite' instead of 'redsys' in the redirect gateway callback. This caused SUMO to set the wrong payment method on renewal orders, triggering the wrong gateway filter and using incorrect credentials.
  • YITH WooCommerce Subscriptions were being cancelled prematurely on failed renewals for the Redsys Redirect, InSite, Apple Pay Checkout and Google Pay Checkout gateways. The "no token / expired card" path in doing_scheduled_subscription_payment (class-wc-gateway-redsys.php and class-wc-gateway-insite-redsys.php) called ywsbs_register_failed_payment and then returned false, causing the YITH wrapper renew_yith_subscription to call it again. The double increment of failed_attempts cancelled…
  • PayGold link generated from admin order metabox was never saved correctly due to an impossible response code condition in send_paygold_link. The function now uses the same validation logic as the checkout flow (response code 9998).
  • Fixed undefined $description variable in paygold_metabox_save when sending a PayGold link from the order edit screen.
  • Custom notification domain (redsys_url_notify) was broken by check_url prepending home_url to URLs that already had a different domain. check_url now detects absolute URLs and preserves them as-is.
  • Get_notify_home_url now automatically adds https:// when the custom notification domain is saved without a scheme.
  • PHP 8.3+ compatibility, Fixed deprecated warnings for passing null/false to string functions (trim, strlen) from get_option calls in get_txnid, get_token_type, and connect_standard_imap.
  • PHP 8.3+ compatibility, Fixed add_submenu_page(null...) in setup guide causing strpos /str_replace deprecation warnings.

Segurança

  • SECURITY [Medium]: Fixed an authenticated account takeover vulnerability that could allow an attacker to assume any user account, including administrators.
Assinar para baixar a versão 30.4.0

Versão 30.3.0

Notas da versão 30.3.0: 5 novidades 6 correções

Novidade

  • Virtual / Downloadable Products order status override in Advanced Settings. When all products in an order are virtual or downloadable, the order status can be automatically set to Completed instead of Processing.
  • Redsys response code 0115 (card cancelled or account closed) now automatically deletes the stored card token, notifies the customer with instructions to add a new payment method (My account > Payment Methods), and notifies the admin.
  • Admin email notification when a customer's credit card is automatically removed due to Redsys hard-decline response codes (0115, 0172, 0173).
  • Improved customer email when a card is removed, now includes the last 4 digits of the card, the error code, and a direct link to add a new payment method.
  • COF_INI (Credential on File initial) flag is now saved to order meta (_redsys_cof_ini) for all COF transaction types (R and C), preventing duplicate token creation when COF_INI=N.

Correção

  • Conditional Rules test mode now correctly applies to the Redsys gateway URL. Previously, orders with conditional rules overriding test mode still used the default gateway URL.
  • Fixed duplicate token creation when customer already has a saved card and COF_INI=N is sent to Redsys.
  • Fixed undefined array key warnings in save_field_update_order_meta when conditional rules data is incomplete.
  • Fixed $redsys->debug reference using wrong variable in preauthorization logging (now uses $this->debug).
  • Fixed sanitize_text_field applied before substr for HTTP_ACCEPT_LANGUAGE in Google Pay and Apple Pay Checkout, ensuring correct sanitization order.
  • Google Pay Checkout now ensures WooCommerce transactional emails are initialized before calling payment_complete in payment callbacks.
Assinar para baixar a versão 30.3.0

Versão 30.2.1

Notas da versão 30.2.1: 1 correção

Correção

  • Google Pay Express Checkout now triggers WooCommerce transactional emails after successful payment (customer and admin).
Assinar para baixar a versão 30.2.1

Versão 30.2.0

Notas da versão 30.2.0: 5 novidades 1 melhoria 7 correções

Novidade

  • Full support for WBTE WC Subscriptions plugin across all payment gateways.
  • Subscriptions settings section in Advanced Settings to choose credentials for renewal payments.
  • PayGold auto-cancellation when the payment link expires, with cleanup of metadata and scheduled events.
  • SOAP endpoint connectivity checks (test and live) in WooCommerce System Status report.
  • Automatic deactivation of conflicting plugins (including Woo Redsys Gateway Light) on activation.

Melhoria

  • Improved error logging for Apple Pay, Google Pay and subscription renewal payments.

Correção

  • Fixed WooCommerce System Status report showing empty values and incorrect export format.
  • Fixed Apple Pay Block checkout stability issues (event handler timing, error handling, and shipping updates).
  • Fixed Apple Pay and Google Pay Express Pay not working correctly with FSE block themes.
  • Fixed Apple Pay and Google Pay country codes not normalized to uppercase, causing shipping calculation failures.
  • Fixed PayGold reading expiration setting from wrong option key and incorrect cancellation message.
  • Fixed subscription renewal errors not being properly handled, logged, or reported to YITH/SUMO Subscriptions.
  • Fixed Redsys REST API error responses with errorCode not being properly detected.

Versão 30.1.0

Notas da versão 30.1.0: 4 novidades 1 melhoria 4 correções 1 reforço de segurança

Novidade

  • Conditional Rules, visual rule builder to override payment parameters (terminal, merchant code, SHA256, transaction type, test mode, etc.) based on order conditions (category, tag, amount, currency, language, user role).
  • Added preauthorization support for Google Pay and Apple Pay.
  • Google Pay and Apple Pay now save merchant code to order meta for preauthorization operations.
  • Added post_payment_complete hooks for Bank Transfer, IMAP email processing and Inespay gateways.

Melhoria

  • Refactored InSite payment form error handling with AJAX-based refresh instead of full page reload.

Correção

  • Fixed InSite COF_TYPE detection that caused incorrect credential-on-file type in REST payments.
  • Fixed Ds_Card_PSD2 using wrong variable in REST payment path.
  • Fixed InSite orders being marked as paid without Redsys authorization when a third-party plugin filters woocommerce_cart_needs_payment.
  • Improved InSite checkout routing using REST_REQUEST instead of checkout_use_block for reliable shortcode/block detection.

Segurança

  • Masked secret SHA256 key in debug logs.
Assinar para baixar a versão 30.1.0

Versão 30.0.1

Notas da versão 30.0.1: 3 correções

Correção

  • Fixed Express Payment (Google Pay / Apple Pay) not applying IRPF correctly when using Autonomos Premium. Totals now reflect the correct amount including retention.
  • Improved compatibility between Express Payment custom fields and Autonomos Premium surcharge calculation.
  • Fixed EMV 3DS timezone fields not being saved for users in UTC+0 timezone (e.g. Canary Islands), which could cause errors in 3D Secure authentication.
Assinar para baixar a versão 30.0.1

Versão 30.0.0

Notas da versão 30.0.0: 6 novidades 9 correções

Novidade

  • Added test environment URL selector (SIS-T / SIS-I) to all payment gateways with configurable test mode (Redsys Redirection, InSite, Bizum, Bizum Checkout, Google Pay Redirection, Google Pay Checkout, Apple Pay Checkout, Direct Debit, Masterpass).
  • Added Apple Pay and Google Pay express checkout buttons on product pages (simple and variable products).
  • Apple Pay and Google Pay product buttons now support subscription products.
  • Apple Pay and Google Pay express checkout on product pages now detect custom checkout fields and prompt for them before payment (NIF/DNI, date of birth, etc.).
  • Full compatibility with Advanced Subscriptions for WooCommerce.
  • Full compatibility with Autonomos Premium in Express Payments (Google Pay / Apple Pay) on product, cart and checkout pages. IRPF retention is now correctly applied based on user type selection (particular, autonomo, empresa).

Correção

  • Fixed IRPF retention being applied for all user types in Express Payment (Google/Apple Pay). Now correctly applies only for "business" and "self_employed" users, not for "particular". Affects product, cart (Blocks), and checkout (classic and Blocks) pages.
  • Fixed stale Autonomos user type session not being overridden when user selects a different type in Express Payment custom fields modal.
  • Google Pay checkout-price endpoint now recalculates totals instead of using cached values, ensuring correct IRPF amounts.
  • Added missing save_express_fields_to_order in Apple Pay Blocks support, ensuring custom fields (user type, DNI) are saved to orders.
  • Fixed race condition in subscription renewal payments that could trigger duplicate payment_complete calls. The _redsys_done meta is now saved immediately after payment_complete instead of at the end of the function, closing a window where a simultaneous IPN notification could process the same payment again.
  • Added transient lock to doing_scheduled_subscription_payment to prevent duplicate processing of the same renewal order.
  • Removed excessive logging from Inespay gateway is_available function.
  • Fixed PHP 8.2+ deprecation notice for dynamic property creation in Inespay gateway (notify_url).
  • PayGold now sets order status to on-hold (like bank transfer) so Pay/Cancel buttons are not shown on the order-received page, stock is reduced immediately, and customers see an informational message instead.

Versão 29.1.2

Notas da versão 29.1.2: 4 correções

Correção

  • Google Pay Redirection now uses strict equality check to prevent it from appearing in checkout block when disabled.
  • Fixed YITH Subscriptions renewal payments not processing - added missing return false when customer has no saved token (Redsys and InSite gateways).
  • Fixed YITH Subscriptions renewal payments staying on-hold - added missing return false when Redsys returns an error response (Redsys and InSite gateways).
  • Added ywsbs_register_failed_payment call when token is missing to properly notify YITH Subscriptions of the failure.
Assinar para baixar a versão 29.1.2

Versão 29.1.1

Notas da versão 29.1.1: 3 correções

Correção

  • Fixed PHP 8.4 compatibility - nullable parameters are now explicitly declared in REST controller methods.
  • Fixed "$this" usage in static methods for Apple Pay Checkout and Redsys gateway subscription renewal processing.
  • Apple Pay and Google Pay Express Checkout no longer appear as regular payment methods in the checkout block (they only appear in the Express Checkout section as intended).
Assinar para baixar a versão 29.1.1

Versão 29.1.0

Notas da versão 29.1.0: 5 novidades 4 correções 1 reforço de segurança

Novidade

  • Added subscription renewal support for Apple Pay Checkout gateway (WooCommerce Subscriptions, YITH Subscriptions, SUMO Subscriptions, Advanced Subscriptions for WooCommerce).
  • Added subscription renewal support for Google Pay Checkout gateway (WooCommerce Subscriptions, YITH Subscriptions, SUMO Subscriptions, Advanced Subscriptions for WooCommerce).
  • Added subscription renewal support for Inespay gateway (WooCommerce Subscriptions, YITH Subscriptions, SUMO Subscriptions, Advanced Subscriptions for WooCommerce).
  • Added subscription renewal support for InSite gateway (WooCommerce Subscriptions, YITH Subscriptions, SUMO Subscriptions, Advanced Subscriptions for WooCommerce).
  • Added Autonomos Premium IRPF compatibility - Apple Pay and Google Pay Express Checkout buttons are automatically hidden when the cart contains products that require IRPF retention.

Correção

  • Google Pay Redirection is now available in the Checkout Block without requiring Google Pay Checkout to be enabled.
  • Standard IMAP email processing now works on servers without the PHP IMAP extension (ext-imap) by using a bundled fallback IMAP client.
  • Prevented update checks from triggering warnings when the update server is unreachable or returns invalid data.
  • Fixed the "Card payment problem" customer email to always use the correct order object and avoid WooCommerce email structured-data fatal errors when the order date is missing.

Segurança

  • Updated node dependencies to fix vulnerabilities (qs, express, react-router, react-router-dom, @remix-run/router, node-forge, cipher-base, sha.js, tar-fs, validator, tmp, inquirer, js-yaml, playwright, pbkdf2, form-data, on-headers, compression).

2025

29 versões

Versão 29.0.0

Notas da versão 29.0.0: 2 novidades 1 melhoria 2 correções

Novidade

  • Added Google Pay Express Checkout for the Checkout Block.
  • Added Apple Pay and Google Pay Express Checkout for the Cart Block.

Melhoria

  • Agentic Commerce flow aligned with WooCommerce core (wc/agentic/v1 routes, bearer auth registry, provider/payment-method metadata for supported Redsys gateways).

Correção

  • Apple Pay Express Checkout orders are now correctly marked as Apple Pay (instead of Redsys).
  • Apple Pay Express Checkout now triggers WooCommerce transactional emails after successful payment (customer and admin).
Assinar para baixar a versão 29.0.0

Versão 28.0.1

Notas da versão 28.0.1: 2 correções

Correção

  • Load Redsys IMAP support before scheduling the email checker cron, avoiding “no callbacks registered” warnings for redsys_check_emails_cron.
  • Hid the development-only “App & Push” settings section so it no longer appears in production admin menus.
Assinar para baixar a versão 28.0.1

Versão 28.0.0

Notas da versão 28.0.0: 5 novidades 1 correção

Novidade

  • Added Inespay (Transferencia Online) gateway with sandbox/production toggle, callbacks, refunds API, and direct redirect/modal flow.
  • Inespay now supports subscription flows with two-step (single + periodic mandate) handling and customer redirection.
  • Inespay refunds implemented via official REST endpoint with callbacks for success/error.
  • Redsys and Inespay notifications are now WooCommerce email classes that can be configured in WooCommerce > Emails (payment error alerts, missing tokenization data, unpaid thank-you warning, card reminder/request, card expiry/removal, Inespay transfer review, and periodic mandate failure).
  • The Inespay transfer review email includes a direct link to the management screen (redsys-inespay-subscriptions&tab=review) and allows choosing the recipient from WooCommerce > Emails.

Correção

  • PayGold link generation and storage corrected so admin actions send the proper URL.
Assinar para baixar a versão 28.0.0

Versão 27.1.4

Notas da versão 27.1.4: 2 melhorias 4 correções

Melhoria

  • TEMP: InSite uses SOAP again while the newly introduced REST flow issues are fixed.
  • One-click product button now disables after click and shows a processing spinner to prevent duplicate submissions.

Correção

  • Only register/schedule the Redsys email IMAP cron when the Redsys_Imap_Connection class is available, preventing missing-callback warnings on sites without Gmail/IMAP support (e.g., PHP < 8.1).
  • Token C COF/renewal REST flows no longer send DS_MERCHANT_DIRECTPAYMENT; it is still sent for token R.
  • Block checkout now procesa tokens C directamente (REST) respetando 3DS, en vez de redirigir a Redsys para pedir una tarjeta nueva.
  • Persist 3DS transients/context for token C so CRes callbacks finish en sitio sin caer en la pantalla “There is nothing to see here”.
Assinar para baixar a versão 27.1.4

Versão 27.1.3

Notas da versão 27.1.3: 2 correções

Correção

  • Redsys redirection token payments (C and R) now send complete EMV3DS browser data (accept header, JavaScript enabled, etc.) to avoid SIS0573/SIS0653 authentication rejects, and force DS_MERCHANT_DIRECTPAYMENT to true for COF flows.
  • Improved token payment debug logs to include saved meta and order status when finishing the flow, making troubleshooting clearer.
Assinar para baixar a versão 27.1.3

Versão 27.1.2

Notas da versão 27.1.2: 1 correção

Correção

  • Fixed InSite checkout fatal error by removing static $this usage in token validation (check_token_insite_from_action_checkout).

Versão 27.1.1

Notas da versão 27.1.1: 1 correção

Correção

  • Fixed Redsys redirection subscription renewals by forcing the correct DirectPayment flow and avoiding SIS0644 errors.

Versão 27.1.0

Notas da versão 27.1.0: 1 novidade 1 melhoria 1 correção

Novidade

  • Added terminal type selection (Mixed/Secure) for Apple Pay and Google Pay to choose the proper flow (direct vs. secure redirect).

Melhoria

  • Migrated InSite payment flow from SOAP to REST using the unified Redsys REST client, keeping token/COF handling, preauthorizations, and step-by-step debug logs intact for Apple/Google Pay and subscriptions reuse.

Correção

  • Prevented PHP 8.1+ deprecation notices in the onboarding/setup page by validating the menu slug before calling add_submenu_page.
Assinar para baixar a versão 27.1.0

Versão 27.0.0

Notas da versão 27.0.0: 3 novidades 2 melhorias 5 correções

Novidade

  • Added Agentic Commerce Protocol integration with product feed export (including OpenAI format) and checkout/payment delegation services.
  • Added compatibility for Subscriptions for WooCommerce and Advanced Subscriptions recurring payments.
  • Added Bizum in the Checkout (Bizum sin salir del sitio) compatibility with the Checkout Block, including the phone field and in-page modal flow.

Melhoria

  • Refreshed the onboarding/setup wizard with clearer basic configuration steps, logging/test guidance, and modernized styling for payment method selection.
  • Refactored Redsys gateway helpers to streamline URL handling and logging; bumped Playwright, axios, tar-fs, and related dependencies.

Correção

  • Get token with InSite in the checkout block only when it is checked.
  • Applied domain validation to url_ok redirects in Apple Pay, Google Pay, and PayGold flows using WCRed ->check_url.
  • Prevented duplicate scheduled actions from being registered repeatedly.
  • Guarded payment method rendering with check_user_show_payment_method to avoid undefined method errors.
  • Applied domain validation to url_ok redirects in Apple Pay, Google Pay, and PayGold flows using WCRed ->check_url.
Assinar para baixar a versão 27.0.0

Versão 26.2.3

Notas da versão 26.2.3: 7 melhorias 1 reforço de segurança

Melhoria

  • Corrected automatic user login flow after account creation by replacing wp_set_current_user and wp_set_auth_cookie with wp_signon.
  • Added username existence check to avoid conflicts when generating usernames from email addresses.
  • Sanitized $_POST['apple-token-redsys'] input variable.
  • Added permission_callback checks for REST endpoints using referer validation to avoid public access.
  • Enabled CURLOPT_SSL_VERIFYHOST = 2 and CURLOPT_SSL_VERIFYPEER = 1 in Redsys API library to enforce proper SSL certificate validation and prevent MITM attacks.
  • Justified use of wp_redirect for external OAuth flow with proper comment.
  • Escaped dynamic CSS output for safe rendering.

Segurança

  • Secured wp_remote_* calls with host validation to prevent SSRF vulnerabilities.

Versão 26.2.2

Notas da versão 26.2.2: 1 correção

Correção

  • Prevented fatal error with SimplePie by storing only feed item data arrays instead of serializing objects in Dashboard widgets.

Versão 26.2.1

Notas da versão 26.2.1: 1 melhoria 1 correção

Melhoria

  • Dashboard widgets optimization and disabled by Default.

Correção

  • Undefined variable $imap_enabled

Versão 26.2.0

Notas da versão 26.2.0: 2 melhorias 1 correção

Melhoria

  • Improved IMAP integration and email parsing reliability for Redsys email processing, with better logging.
  • Get_last_four now supports card numbers with masking characters (e.g., *1234) or shortened versions (e.g., 2345).

Correção

  • Apple Pay now correctly recognizes the province from Apple shipping data, allowing WooCommerce to load the corresponding shipping methods.

Versão 26.1.0

Notas da versão 26.1.0: 3 novidades 2 melhorias 3 correções

Novidade

  • Apple Pay is now compatible with buttons configured in the Checkout Block settings.
  • Support for accepting terms and conditions with Apple Pay.
  • Option to display only the card form in Redsys or all available payment methods.

Melhoria

  • Improved checkout_use_block and cart_use_block functions.
  • Enhanced the get_order method in the Redsys API.

Correção

  • Resolved an issue when editing the Checkout page using a shortcode.
  • Only valid shipping methods are now displayed during Apple Pay Express Checkout.
  • Corrected the final price display when using Apple Pay with the Checkout shortcode.

Versão 26.0.0

Notas da versão 26.0.0: 1 novidade 1 melhoria 2 correções

Novidade

  • Full compatibity with Apple Pay Express Block Checkout.

Melhoria

  • Get_user_id to get_customer_id.

Correção

  • Warning Undefined variable $textthabks.
  • Warning $redsys NULL.

Versão 25.9.1

Notas da versão 25.9.1: 1 correção

Correção

  • Custom URL notification field.

WooCommerce RedSys Gateway

Versão na DROPE: 32.2.1
Ver produto

As versões disponíveis na DROPE são liberadas para assinantes e para quem comprou o produto.

O que mudou

1.044 mudanças em 204 versões

  • Novidade 304
  • Melhoria 257
  • Correção 470
  • Segurança 13

Versões

204
  1. 32.2.120 out 2026
  2. 32.2.014 out 2026
  3. 32.1.111 set 2026
  4. 32.1.09 set 2026
  5. 32.0.028 jul 2026
  6. 31.0.720 jul 2026
  7. 31.0.619 jul 2026
  8. 31.0.52 jul 2026
  9. 31.0.41 jul 2026
  10. 31.0.327 jun 2026
  11. 31.0.216 jun 2026
  12. 31.0.19 jun 2026
  13. 31.0.06 jun 2026
  14. 30.4.15 maio 2026
  15. 30.4.021 abr 2026
  16. 30.3.07 mar 2026
  17. 30.2.127 fev 2026
  18. 30.2.026 fev 2026
  19. 30.1.016 fev 2026
  20. 30.0.111 fev 2026
  21. 30.0.011 fev 2026
  22. 29.1.220 jan 2026
  23. 29.1.114 jan 2026
  24. 29.1.014 jan 2026
  25. 29.0.021 dez 2025
  26. 28.0.115 dez 2025
  27. 28.0.010 dez 2025
  28. 27.1.41 dez 2025
  29. 27.1.329 nov 2025
  30. 27.1.228 nov 2025
  31. 27.1.128 nov 2025
  32. 27.1.028 nov 2025
  33. 27.0.018 nov 2025
  34. 26.2.310 jul 2025
  35. 26.2.22 jul 2025
  36. 26.2.11 jul 2025
  37. 26.2.026 jun 2025
  38. 26.1.07 jun 2025
  39. 26.0.019 maio 2025
  40. 25.9.15 maio 2025
  41. 25.9.02 maio 2025
  42. 25.8.022 abr 2025
  43. 25.7.210 abr 2025
  44. 25.7.19 abr 2025
  45. 25.7.07 abr 2025
  46. 25.6.21 abr 2025
  47. 25.6.124 mar 2025
  48. 25.6.023 mar 2025
  49. 25.5.016 mar 2025
  50. 25.4.315 mar 2025
  51. 25.4.214 mar 2025
  52. 25.4.114 mar 2025
  53. 25.4.014 mar 2025
  54. 25.3.519 dez 2024
  55. 25.3.46 dez 2024
  56. 25.3.328 nov 2024
  57. 25.3.228 nov 2024
  58. 25.3.127 nov 2024
  59. 25.3.027 nov 2024
  60. 25.2.012 nov 2024
  61. 25.1.57 nov 2024
  62. 25.1.45 nov 2024
  63. 25.1.34 nov 2024
  64. 25.1.222 out 2024
  65. 25.1.122 out 2024
  66. 25.1.017 out 2024
  67. 25.0.216 abr 2024
  68. 25.0.114 mar 2024
  69. 25.0.014 mar 2024
  70. 24.3.421 fev 2024
  71. 24.3.321 fev 2024
  72. 24.3.27 fev 2024
  73. 24.3.15 fev 2024
  74. 24.3.04 fev 2024
  75. 24.2.118 dez 2023
  76. 24.2.026 nov 2023
  77. 24.1.06 nov 2023
  78. 24.0.130 out 2023
  79. 24.0.027 out 2023
  80. 23.0.326 out 2023
  81. 23.0.220 out 2023
  82. 23.0.114 out 2023
  83. 23.0.013 out 2023
  84. 22.2.119 set 2023
  85. 22.2.05 set 2023
  86. 22.1.119 ago 2023
  87. 22.1.018 ago 2023
  88. 22.0.016 jul 2023
  89. 21.2.112 jul 2023
  90. 21.2.030 jun 2023
  91. 21.1.019 jun 2023
  92. 21.0.218 jun 2023
  93. 21.0.115 jun 2023
  94. 21.0.030 maio 2023
  95. 20.4.014 maio 2023
  96. 20.3.02 abr 2023
  97. 20.2.11 mar 2023
  98. 20.2.027 fev 2023
  99. 20.1.09 fev 2023
  100. 20.0.325 jan 2023
  101. 20.0.219 jan 2023
  102. 20.0.118 jan 2023
  103. 20.0.018 jan 2023
  104. 19.1.013 jan 2023
  105. 19.0.123 dez 2022
  106. 19.0.019 dez 2022
  107. 18.1.124 mar 2022
  108. 18.1.021 mar 2022
  109. 18.0.014 mar 2022
  110. 17.1.119 fev 2022
  111. 17.1.015 fev 2022
  112. 17.0.34 dez 2021
  113. 17.0.211 nov 2021
  114. 17.0.17 nov 2021
  115. 17.0.025 out 2021
  116. 16.1.113 set 2021
  117. 16.1.012 set 2021
  118. 16.0.15 jul 2021
  119. 16.0.04 jul 2021
  120. 15.2.221 jun 2021
  121. 15.2.121 jun 2021
  122. 15.2.019 jun 2021
  123. 15.1.29 jun 2021
  124. 15.1.11 jun 2021
  125. 15.1.01 jun 2021
  126. 15.0.326 mar 2021
  127. 15.0.23 mar 2021
  128. 15.0.023 fev 2021
  129. 14.0.328 jan 2021
  130. 14.0.218 jan 2021
  131. 14.0.118 jan 2021
  132. 14.0.014 jan 2021
  133. 13.0.028 dez 2020
  134. 12.2.06 dez 2020
  135. 12.1.14 dez 2020
  136. 12.1.030 nov 2020
  137. 12.0.314 nov 2020
  138. 12.0.211 nov 2020
  139. 12.0.110 nov 2020
  140. 12.0.06 nov 2020
  141. 9.4.06 ago 2020
  142. 9.3.024 jul 2020
  143. 9.2.316 jul 2020
  144. 9.2.213 jul 2020
  145. 9.2.112 jul 2020
  146. 9.2.09 jul 2020
  147. 9.1.110 jun 2020
  148. 9.1.09 jun 2020
  149. 9.0.22 jun 2020
  150. 9.0.131 maio 2020
  151. 9.0.025 maio 2020
  152. 8.0.022 maio 2020
  153. 7.1.023 abr 2020
  154. 7.0.222 abr 2020
  155. 7.0.121 abr 2020
  156. 7.0.021 abr 2020
  157. 6.1.07 fev 2020
  158. 6.0.01 jan 2020
  159. 5.4.56 nov 2019
  160. 5.4.4.15 nov 2019
  161. 5.4.45 nov 2019
  162. 5.4.330 out 2019
  163. 5.4.215 out 2019
  164. 5.4.114 out 2019
  165. 5.4.07 out 2019
  166. 5.3.118 set 2019
  167. 5.3.011 set 2019
  168. 5.2.09 set 2019
  169. 5.1.36 set 2019
  170. 5.1.225 ago 2019
  171. 5.1.123 jul 2019
  172. 5.1.022 jul 2019
  173. 5.0.115 jul 2019
  174. 5.0.015 jul 2019
  175. 4.7.012 jul 2019
  176. 4.6.27 mar 2019
  177. 4.6.1.14 mar 2019
  178. 4.6.14 mar 2019
  179. 4.6.04 mar 2019
  180. 4.5.125 fev 2019
  181. 4.5.015 jan 2019
  182. 4.4.122 jun 2018
  183. 4.4.018 jun 2018
  184. 4.3.014 maio 2018
  185. 4.2.010 maio 2018
  186. 4.1.09 mar 2018
  187. 4.0.15 mar 2018
  188. 4.0.021 fev 2018
  189. 3.2.020 fev 2017
  190. 3.1.117 fev 2016
  191. 3.0.03 nov 2015
  192. 2.1.05 ago 2015
  193. 2.0.02 jun 2015
  194. 1.9.011 fev 2015
  195. 1.8.08 ago 2014
  196. 1.7.021 jun 2014
  197. 1.6.015 jun 2014
  198. 1.5.16 maio 2014
  199. 1.5.030 abr 2014
  200. 1.4.023 abr 2014
  201. 1.3.010 jan 2014
  202. 1.2.09 out 2013
  203. 1.1.025 jun 2013
  204. 1.0.021 mar 2013
Vídeo ·

Black Friday R$ 19,90 por mês Plano Budget no cartão, preço travado na Black Friday Lote 1 termina em 00d 00h 00m Próximo lote R$ 24,90 Ver a oferta Ver oferta
Ver o carrinho

GANHE 5% DE DESCONTO na sua primeira compra

Preencha o formulário abaixo e garanta 5% de desconto na sua primeira compra. Válido por tempo limitado.