The development of this version has cost €2,950. The accumulated cost for this year is €40,380. The accumulated cost since the first version is €239,110, but the cost for you is only the license of €79.
New 32.2.x branch of the Redsys plugin for WooCommerce from WooCommerce.com.
It is a maintenance version: security reinforcement and fixing issues found while testing all payment flows against the Redsys testing environment. It does not bring any major new functionality.
Branch versions
32.2.0
New:
- New filter redsys_insite_form_language, to choose the language of the InSite card form from code (for example, one for each site language).
- New filter redsys_customer_tokens_limit, to change how many saved cards a customer can read (500 by default).
- The plugin license is now managed in WooCommerce – Settings – Redsys Advanced Settings – General, at the top of the page, and no longer has its own entry in the WooCommerce menu. The license key, how to activate it, and where it is stored do not change, and the old address still works: it redirects to the new site. The notice asking for a license also points there.
Security:
- UCP MCP (disabled by default): an agent could request lookup_catalog any number of products and receive a response of any size. A query now supports a maximum of 50 products and no tool returns more than 1 MB (both limits can be adjusted with filters).
- UCP MCP (disabled by default) did not keep any record of what agents did. Each call to a tool is now written in an audit log (which client agent, which tool, the result, and its duration; the arguments only as a footprint and a masked summary), which is kept for 90 days.
- UCP MCP (disabled by default) had no limit on requests. Each address also has a budget that is checked before authentication (300 calls per minute by default), and a batch request takes a maximum of 20 calls.
- UCP MCP (disabled by default) had no limit on requests. Each client agent now has a budget of 60 tool calls per minute, 600 per hour, and 5000 per day (the same as A2A, adjustable with the filter redsys_ucp_mcp_rate_limits); exceeding that budget results in calls receiving a 429 error.
- Behavior change. UCP MCP (disabled by default): the arguments of the tools are now checked against the published input schema of each tool before executing it; calls that do not comply (for example, without meta.ucp-agent.profile) receive a JSON-RPC -32602 error listing what is wrong.
- Behavior change. UCP (disabled by default): dynamic client registration, meaning that any AI agent creates its own OAuth client in the store, is now disabled by default, and when updating, it is disabled only once where it was only enabled by the old default value. If your agents register themselves, re-enable "Allow dynamic client registration" in the UCP settings.
- ACP (disabled by default): its check for "HTTPS required" believed an X-Forwarded-Proto or X-Forwarded-SSL header came from anywhere. These headers now only count if they come from the proxies indicated in the "Trusted proxies" setting (A2A – Status). NOTE: if you are behind a proxy or a CDN that terminates HTTPS, indicate their addresses there after updating.
- UCP OAuth (disabled by default): authorization codes were stored in the database in plain text, while tokens were stored as hashes. Now codes are also stored as hashes.
- Behavior change. UCP OAuth (disabled by default) now only accepts the PKCE S256 method, as required by the UCP profile; "plain" is rejected. A developer who needs it can return true from the filter redsys_ucp_allow_pkce_plain.
- Behavior change. UCP OAuth (disabled by default): the token introspection endpoint responded to anyone. It now requires the credentials of the calling client (client_id and client_secret) and only reports on tokens of that same client, as required by RFC 7662.
- A2A (disabled by default): after the card authentication step, the buyer could be sent to any address indicated by the agent, including unencrypted http addresses or internal addresses. Now only https addresses on public hosts are used; otherwise, the buyer reaches the order page. The filter redsys_a2a_sca_return_url allows further restriction.
- UCP MCP (disabled by default): when a tool failed within the store, the agent received the internal error text (which may include server paths). Now it receives a correlation identifier; the detail is written in the plugin log.
- Behavior change. UCP and A2A (disabled 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 previous behavior can return true from the filter redsys_allow_bearer_in_query_string.
- UCP OAuth (disabled by default): two token requests sent at the same time with the same authorization code could succeed both. The code is now redeemed atomically; only one request obtains tokens.
- Inespay: after checking the notification signature, the plugin still allowed unsigned fields of the request to fill in values that the signed data did not bring (such as the payment identifier). Now only signed data is used.
- Apple Pay and Google Pay marked the order as paid without checking that the amount charged by Redsys matched the total order amount, as card payments and Bizum already do. A different amount now leaves the order pending with a note for you to review.
- A2A (disabled by default): when an operation failed within the store, the agent received the internal error text (which may include server paths). Now it receives a generic message with a correlation identifier; the detail is written in the plugin log.
- Redsys Manager App: an employee whose WordPress role was downgraded to customer or subscriber retained their app profile and, with it, access to orders and customer data. Their app profile is now deleted when the role changes.
- The public discovery documents for AI agents (UCP /.well-known/ucp and the well-known document of ACP) published the email address of the WordPress administrator. They now publish the address indicated in the new setting "Support e-mail for AI agents", or none.
- A2A (disabled by default): the refund amount at which a store administrator must confirm ("sensitive threshold") was checked refund by refund, so splitting a refund bypassed it. Now it sums what the same customer has refunded in the same order in the last 24 hours. NOTE: a series of small refunds on the same order may now be pending your confirmation.
- A2A (disabled by default): a client's allowed IP list could be exceeded by sending an X-Forwarded-For header with a permitted address. The plugin now checks the address of the connection itself and only believes X-Forwarded-For if it comes from the proxies indicated in the new setting "Trusted proxies" (A2A – Status). NOTE: if your site is behind a CDN or load balancer and a client A2A has an allowed IP list, add the CDN addresses to that setting after updating, or the client will be rejected.
- A2A (disabled by default): task streams ignored the client's request limit, so a single client could open enough to occupy the store's PHP processes. Each stream now counts towards the limit and a client can maintain a maximum of five at a time.
- Disabling A2A in the settings did not stop clients that were already configured. With A2A disabled, its JSON-RPC endpoint and task streams now respond 503 and no push notification is sent.
- Redsys batch actions from the order list (immediate charge, batch refund, approve pre-authorization) now require the same permission as their single order versions (manage WooCommerce) and only execute while their setting is enabled.
- A2A (disabled by default): the push address that an agent indicates for task notifications could cause the store to call its own server or its internal network, even over unencrypted http. It must now be https on port 443 of a public host, and notifications use WordPress's secure HTTP transport.
- ACP Webhooks (disabled by default): a provider could register a webhook pointing to the store's own server or its internal network. The URL of a webhook must now be on port 443 of a public host (a filter allows otherwise for development), webhooks registered before that violate the rule are no longer called, and deliveries use WordPress's secure HTTP transport.
- UCP (disabled by default): the platform profile address that an agent sends in their UCP-Agent header could cause the store to call its own server or its internal network. Now only https addresses on port 443 of public hosts are queried, using WordPress's secure HTTP transport.
- UCP Webhooks (disabled by default): a client could register a webhook pointing to the store's own server or its internal network, and it was sufficient with a read-only token. The URL of a webhook must now be https on port 443 to a public host, registering or deleting one requires checkout write permission (scope), webhooks registered before that violate the rule are no longer called, and deliveries use WordPress's secure HTTP transport.
- UCP, MCP, and A2A (disabled by default) accepted an OAuth refresh token as if it were an access token. Now only access tokens open those routes.
- Agent checkouts (UCP and ACP, disabled by default): an AI agent could add products to an order that the store does not sell: drafts, private or out-of-stock products, variable or grouped parent products. The order is now rejected (422) and indicates which products are involved.
- The 'View details' window of the plugin read the server response from updates with a function that could build PHP objects. It now reads that response only as plain data.
- The browser's data request for 3-D Secure from the checkout could write that data to any order number. It now only writes it to the visitor's own order and, otherwise, saves it in their session.
- Agent checkout (ACP, disabled by default): an order created by an AI agent was associated with any registered customer whose email the agent sent. It now remains as a guest order; stores that want the previous behavior can return true from the filter redsys_acp_link_order_to_customer_by_email.
- One-click purchase took the cost and name of shipping from the browser, so a logged-in customer could pay less for shipping (or nothing). The store now recalculates shipping and it must be one of the options the store offers; a product that requires shipping cannot be purchased without it.
- Agent catalogs (the UCP catalog and the ACP product feed, both disabled by default) listed drafts and 'Private Products', and querying a single UCP product returned unpublished products. Agents now only see published products that are not private. A variation of a private product is also private.
- The batch actions 'Request Redsys card' and PayGold from the Users screen did not check that the request came from that screen, so a page from another site could make an administrator with an active session send card request emails (or PayGold operations) to arbitrary users. They now require the security token from the Users screen and store manager permissions. Additionally, the PayGold handler no longer interferes with batch actions from other plugins on that screen.
- Agent checkout (ACP): revoking an access token did not delete its cached approval, so a revoked token continued to work for up to five minutes. Revocation now takes immediate effect.
- Agent checkout (ACP, disabled by default): access tokens generated as 'Read-only' were accepted for creating, modifying, and canceling orders and for managing webhooks. They are now read-only.
- Agent checkout (ACP, disabled by default): a checkout session could be read, modified, completed, or canceled by any customer who knew its identifier. Sessions now only respond to the AI provider that created them.
- Agent checkout (ACP, disabled by default): a customer using a WooCommerce REST API key could impersonate another AI provider and read, delete, or add webhooks from that provider. The provider is now taken solely from the credential; bearer tokens registered in the WooCommerce agent settings now resolve to their provider (so ACP webhooks work as intended), and a session without a provider no longer sends its events to the webhooks of all providers.
- Agent checkout (UCP, disabled by default): a checkout session could be read, modified, completed, or canceled by any customer who knew its identifier, and order endpoints skipped the owner check for a token without a user. Sessions now only respond to the customer and buyer who created them, and a token without a user is rejected.
- Agent checkout (ACP, disabled by default): an agent could change the address and total of an already paid order, cancel it without refund, or send it back to the payment page. Those requests are now rejected (409) once the order is no longer open; a pre-authorized order is canceled from the store administration, not by an agent.
- Agent checkout (UCP, disabled by default): an agent could continue changing the items and total of a checkout session after their order was paid, or cancel the paid order without refund. A session whose order is paid, canceled, or failed can no longer be modified or canceled.
- InSite in the block checkout could associate a new order with the ongoing Redsys payment number of another buyer, so that the payment confirmation of that buyer could end up in the wrong order. A number that already belongs to another order is no longer associated.
- The 'add payment method' redirect link responded to anyone, and when given an order number, it rewrote the terminal and key settings of that order with the default values (which broke subsequent refunds in stores with multiple terminals). It now only responds to the logged-in customer who started adding the card, and never writes order data.
- The card payment notification marked its status as 'already in process' before checking the signature, so a forged request could make the store ignore the authentic Redsys notification for a minute and leave a paid order pending. The mark is now only placed after verifying that the signature is valid.
- Management app (disabled by default): a staff profile with permission to edit customers could also edit an administrator's account, including the email, 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 accounts.
- License activation and update checks communicated with plugins.joseconti.com without verifying its TLS certificate, and relied on what the response said about which plugin to update and where to download it from. TLS is now always verified, the offered update is always for this plugin, and the download must come via https from the license server itself.
- Email payment reconciliation (IMAP/Gmail, disabled by default): an email whose sender simply contained the Redsys address could mark a pending order as paid, and a real email from Redsys about a denied payment could also do so. Now the sender must be exactly the address indicated in the settings, and the email must show an approved payment for the order amount and with its merchant code; otherwise, the order remains as it was and receives a note. If in those settings you wrote only part of the Redsys address (or just the domain), write the full address.
- A REST address of InSite that was not used (woocommerce-redsys/v1/save_order_data) has been removed, which allowed a request that only carried a matching Referer header to change the Redsys order number saved in any order, which refunds depend on. The block checkout has not used it since 31.0.4.
- Agent checkout (UCP, disabled by default): an order created by an AI agent was associated with the registered customer who owned the email sent by the agent, which also made the saved cards of that customer accessible. The order now belongs to the customer who authorized the agent, and never to someone by an email address.
- Express Apple Pay stored a temporary mark under a name taken from the browser, and that name could match the marks that the plugin reads to confirm payments. Wallet marks (Apple Pay and Google Pay) are now stored under their own names with hash.
- Complete, for the redirect payment page, the arrangement of the saved cards of this same version. The chosen card in the checkout was also transferred to the signed Redsys payment form without checking whose it was. The form now uses a saved card only if it belongs to the paying customer; otherwise, it requests a new card (a new subscription card when the order has a subscription).
- Each order retains the Redsys key used for payment, so that refunds and renewals continue to function when multiple terminals are used. The WooCommerce REST API used to return that key to any integration with a read-only API key. It is no longer included in the REST responses for orders or subscriptions; it is still stored and used exactly as before.
- With "Show the Redsys page inside the store" (iframe mode), and in all Bizum Checkout orders, the return links displayed the cancellation and order received addresses of an order, with its private key, to anyone who requested them, for as long as the store retained a non-expiring brand. Now they only respond to the buyer who owns the order (the return links sent to Redsys carry the order key for that), and the brand expires after one day.
- A link from the notifications endpoint, used by the now-removed 3-D Secure method step, sent any visitor to the payment page of the order number indicated in the link, including its private order key. Now it only sends there to the buyer who owns the order (card and InSite).
- The additional fields requested by the express buttons of Apple Pay and Google Pay (NIF/DNI and similar) stored any field name that carried the request, in the order and in the customer's account. Now they only store the fields defined by your store, and never the internal data of the plugin. Stores displaying express buttons should update.
- A saved card could be charged by someone to whom it did not belong. The card is identified in the checkout request with a row number, and the plugin did not check whose card it was, so a manipulated request could charge the saved card of another customer without the bank asking that customer to confirm anything. Each charge with a saved card now checks that the card belongs to the customer who is paying, and otherwise rejects the payment; a non-existent card identifier no longer causes a fatal error. Stores offering saved cards should update. Reported privately, with the cause already located, by a store that chose to notify us first and not publish anything. Thank you.
Fixed:
- Updating with UCP activated 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 when WordPress has finished loading.
- Expired saved cards: the scheduled tasks that notify the customer and remove expired cards failed with a database error ("You have an error in your SQL syntax") and never did anything. Now they work, also removing cards that expired in a previous year and only touching the cards saved by this plugin.
- InSite: the "Gateway Language" setting was ignored, so the card fields (the example texts and the button) were always displayed in Spanish. The chosen language is now sent to Redsys in the classic checkout and in the block checkout.
- Customers with more than 10 saved cards: subscription renewals and "Immediate charge in Redsys" could use an older card instead of the most recent one, a card already saved could be saved again, and the classic checkout did not list the most recent cards. The plugin now reads all Redsys cards of the customer for its own decisions.
- License: when the license server rejected activation, the settings page only said "Your settings have been saved." Now the error returned by the server is displayed, and a rejected key no longer appears as "The license is active."
- License: saving the Advanced Redsys Settings with the license already active sent it to activate again on each save. An active license is no longer sent again.
- "Immediate charge in Redsys" (and any charge with a saved card): when Redsys rejected the charge in its first step, the order remained pending without any explanation. The reason and the error code from Redsys are now written in a note of the order.
- InSite in the block checkout: a saved card for "One-click payment" after a 3DS challenge was stored as a subscription card. Now it is stored with the type with which it was requested.
- InSite in the block checkout: the payment button always said "Pay." Now it shows the label "Pay" translated into the site's language.
- InSite in the block checkout: on a server without the PHP SOAP extension, the payment ended in a "critical error." The customer now receives a message asking them to choose another payment method, and the cause is written in the InSite log.
- Classic checkout: with both Bizum and Bizum Checkout in test mode, the test mode notice was displayed twice.
- One-click purchase from the product page: the shipping options showed "€" instead of the currency symbol.
- Confirming a pre-authorization wrote the order status note twice, and moved the order to Completed even though another status was configured for confirmed pre-authorizations.
- Block checkout: when Bizum Checkout was denied, the customer was returned to the checkout without any message. Now the error is displayed, as it already occurred 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 with card. The order retains the payment method with which it was made.
- 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, Redsys authorized the payment but the order remained 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 (One-click payment) was rejected by Redsys with the error SIS0574 (browserUserAgent not specified). The browser data for 3DS is now also attached to the order in the block checkout.
- Apple Pay: the debug log now shows the parameters actually sent to Redsys, read from the signed request itself. Previously, its lines were written separately and could differ from the request: subscription parameters were sent but not recorded, and the Apple MerchantID line was recorded even when it was not sent.
- My account – Payment methods: the "Type" column printed PHP notices (Undefined array key "delete", Undefined variable $token_type_name) on cards or accounts saved by other gateways, such as PayPal. Now it only describes the cards saved by this plugin and shows "–" for any other saved method.
- Bizum Checkout: the waiting page shown while confirming payment loaded jQuery from ajax.googleapis.com. Now it uses the copy included with WordPress, so the page does not make any requests to third parties.
- 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 (disabled by default): with ACP activated, WordPress could log "Translation loading for the woocommerce domain was triggered too early" when the hourly cleanup of ACP was first scheduled. It is now scheduled in init.
- The duplicated scheduled actions that left previous versions are now removed on their own: the paired workers redsys_acp_process_webhooks / redsys_ucp_process_webhooks, a redsys_check_emails_cron without a group, and the repeated daily cleanups. Since 32.1.0, no new ones were created, but the existing ones remained.
- The plugin's text domain is now its slug, woocommerce-gateway-redsys (it was previously woocommerce-redsys), in all strings, in the included translation files and in the block checkout scripts. Custom translation files saved with the old name in wp-content/languages/plugins or by Loco Translate continue to work. Translations saved 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 the WooCommerce text domain and four order status counters had none; one of them (the plain text email for canceled order) could never be translated. They now use the plugin's domain.
- Subscription renewals did not send any description to Redsys, so the operation appeared with an empty description in the POS (the first payments were fine). Renewals and invoice charges from the gateway by redirection, and InSite renewals, 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 (gateway by redirection) always sent "Order N" as the description, regardless of what the gateway setting said. Now it follows the setting.
- ACP (disabled by default): the public ACP document announced a limit of 60 requests per minute that was never applied. The announcement has been removed.
- UCP OAuth (disabled by default): two refreshes sent at the same time with the same refresh token could each obtain a new pair of tokens. The refresh token is now consumed atomically; the second request receives invalid_grant.
- A2A (disabled by default): the maximum amount set for create_payment and tokenize_card was not applied. Higher amounts are now rejected before creating any order.
- A failed or late payment notification (for example, the 'denied' result of a previous attempt that arrives after the order has been paid) could cancel an order that was already paid, in Bizum and in other Redsys payment methods. A paid order is never canceled by a notification; a note records what Redsys sent.
- "Private products" (disabled by default) did not work: products marked as private were only removed from the store listing, and anyone could still see and purchase them, and the list of allowed users remained empty. A private product is now hidden (product page, Blocks/Store API) and cannot be purchased by anyone not on its list; store managers always see it. IMPORTANT if you use this option: open each private product and re-select its allowed users, because previous versions lost those lists. A notice on the product screens reminds you of this.
- In test mode, "Show to these users" limits a gateway to the users you choose. The block checkout ignored it and showed the gateway to all visitors, including guests; then the order was rejected, so the customer saw a payment method that failed when clicked. All gateways now apply the list in the block checkout just like in the classic one. A filter for developers, redsys_gateway_shown_to_user, allows adjusting the decision. Reported with the cause already located. Thank you.
- Apple Pay and Google Pay (checkout) had the "Show to these users" field but never applied it, in any checkout. Now they apply it.
- With Inespay, a user on the "Show to these users" list could still not see it, because the saved list was compared incorrectly. Users on the list can now see it.
- With the "One-click payment" from the product page active, the plugin added two headers, "Terms and Conditions" and "Select Shipping Method", to all product pages, even if no one had opened those windows, which cluttered the structure of the page 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 header: instead, it names the window for screen readers, which the terms and shipping windows did not do before. It does not change anything in what the customer sees. Reported by a store that found it in its header audit. Thank you.
- The script and styles for "One-click payment" from the product page were loaded on all product pages, even where the button never appears because the option is disabled or the visitor is not logged in. Now they are loaded only where the button appears.
Development:
- The package published on WooCommerce.com no longer includes the license and update client used by copies purchased on plugins.joseconti.com (it was never loaded there). The plugin loads it only when the file is present.
- phpstan.neon has been added (with third-party libraries included in the plugin excluded and a baseline of existing findings) so that static analysis only reports new issues.







