Autopay · Version history
Autopay changelog and version history
- Latest version
- 5.1.0
- Oct 26, 2026 (16 days ago)
- Releases
- 17
- since 2025
- In the last year
- 16
- about one every 22 days
- Tested up to
- WordPress 7.1.4
- PHP 7.4 or later
Releases each year
- 20252 releases
- 202615 releases
202615 releases
Autopay 5.1.0Latest
- Security: improved payment notification handling and order status processing. Immediate update is recommended.
- Added: integration with “Flexible Subscriptions” for WooCommerce, supporting recurring card payments, automatic renewals, manual renewal payments and one-time additional payments.
- Added: synchronization of subscription card activation/deactivation (RPAN/RPDN) and subscription cancellation, deactivation and suspension with Autopay.
- Added: support for mixed carts containing subscription and one-time products.
- Added: automatic filtering of payment channels as the cart changes in classic and block checkout.
- Added: recurring payment logs and subscription/order diagnostics.
- Added: a payment link for failed Autopay renewals in the WooCommerce customer “Failed order” email, when that email is enabled in the store settings.
Autopay 5.0.5
- Fixed: the BLIK Pay Later and instalments payment descriptions displayed as raw HTML code instead of formatted text on checkout.
Autopay 5.0.4
- Fixed: the ITN confirmation response sent back to Autopay declared an invalid standalone="" XML pseudo-attribute, causing Autopay to reject the response with an XML parse error (“Invalid XML pseudo-attribute ‘standalone'”). The attribute is no longer emitted.
Autopay 5.0.3
- Fixed: improved Apple Pay availability detection during checkout, preventing empty Apple Pay sections from appearing on unsupported devices and browsers, including when checkout scripts are loaded in a different order.
- Fixed: improved Google Pay error handling to prevent incomplete configuration data from disrupting the payment section during checkout.
Autopay 5.0.2
- Fixed: High-Performance Order Storage (HPOS) compatibility declared; order meta reads/writes across the plugin switched to the HPOS-safe order meta API.
- Fixed: payment channel selector on the “Pay for order” (order-pay) page — it previously rendered as a plain description instead of the actual list of payment channels.
- Fixed: BLIK-0 payment on the order-pay page now redirects to the order-received page after payment is started, instead of reloading the order-pay page.
- Fixed: retrying a payment (Google Pay, BLIK with redirect, or the default channel) on the order-pay page after a previous attempt now correctly redirects to the payment gateway again, instead of silently failing with the order left unpaid.
- Fixed: payment channel list on the order-pay page could stay permanently hidden due to a timing issue with WooCommerce’s own checkout script; the channel list now always displays.
- Fixed: gateway list API was being called on every page load; it is now only called where actually needed, and channel filtering on the order-pay page was corrected.
- Fixed: Apple Pay / Google Pay wallet group position and internal group configuration, restored after an earlier wallet group-type split.
- Fixed: recording a retry payment attempt for an order that was already tracked internally no longer fails silently — it now updates the existing status record instead of attempting a duplicate database insert.
- Fixed: the minimum PHP version check now correctly enforces PHP 7.4 (the plugin’s actual requirement); previously the check only enforced PHP 7.2, allowing the plugin to run — and potentially fail — on unsupported PHP versions.
- Fixed: gateway list cache invalidation (triggered by a site language change) now also clears the WordPress object cache, preventing stale payment channel data from being served on hosts using persistent object caching (Redis/Memcached).
- Security: customer personal data (name, email, phone, IP address, bank account number) is now redacted from ITN debug logs before being written to disk.
- Improved: express payment redirect now auto-detects from order meta when the URL parameter is absent, improving reliability of the redirect-to-gateway flow.
- Fixed: several internal diagnostics/logging bugs found during an internal refactor of the gateway class (a payment channel group title not displaying, a fatal error when an order contained virtual products only, incorrect GA4 event data types, and a PHP 7.4 compatibility issue with typed properties…
Autopay 5.0.1
- Fixed: XSS vulnerabilities — escaped output across all admin templates and settings fields using esc_html_e(), esc_attr_e(), esc_url(), and wp_kses_post() instead of unescaped _e() / echo.
- Fixed: CSRF protection hardened — nonce verification added to payment-on-account-page handler, CSS editor, and legacy configuration importer.
- Fixed: input sanitization improved — added wp_unslash() before sanitize_text_field() across all $_POST/$_GET reads; BLIK code validated as exactly 6 digits.
- Fixed: Test Connection security — added current_user_can('manage_woocommerce') check; previously unauthenticated users could trigger test transactions.
- Fixed: open redirect vulnerability — replaced wp_redirect() with wp_safe_redirect() combined with an explicit allowed-hosts list for the payment gateway domain.
- Fixed: direct file access guard — added defined('ABSPATH') || exit to all PHP source files.
- Fixed: stored CSS output sanitized via wp_strip_all_tags() to prevent </style> breakout in the custom CSS editor.
- Fixed: debug log output — replaced serialize() and print_r() with wp_json_encode() to avoid accidental data exposure in logs.
- Fixed: Polish translations now load correctly — bundled .mo file is prioritised, resolving partial Polish UI under WordPress 6.7+ JIT loading.
- Fixed: removed redundant load_plugin_textdomain() call from compatibility.php.
- Fixed: plugin entry point file reverted to bluemedia-woocommerce.php.
- Fixed: settings page — reset button (bm_reset_order) now works correctly.
- Fixed: payment channels list — class attribute properly escaped.
Autopay 5.0.0
- Added: card payments through the Autopay widget on classic and block checkout.
- Fixed: PHP Deprecated notice on PHP 8.4+ during GA4 event handling for Google Pay payments.
- Updated: isolated GA4 Measurement Protocol library to version 0.1.6.
- Updated: isolated Guzzle dependency to version 7.12.3 to resolve security advisories.
Autopay 4.9.3
- Improved: admin panel typography using locally hosted Open Sans and Roboto Condensed fonts aligned with the new design system.
- Fixed: GA4 transaction attribution by linking purchase events to the user’s session data.
- Fixed: test connection endpoint security, and HMAC typing and signature comparison.
Autopay 4.9.2
- Added: a new setting to choose how Google Pay works — redirect to the Google Pay website or pay directly in your store
- Added: settings to match the logo to the checkout color scheme, including light and dark versions
- Improved: interface styles in the plugin settings and on checkout (checkboxes, buttons)
- Improved: button focus visibility and accessibility during keyboard navigation
- Fixed: an error on pages using the block editor when the payment method list could not be retrieved
- Fixed: the selected bank was not preserved after the checkout refreshed on classic checkout
- Fixed: compatibility with PHP 8.4 and 8.5 — resolved issues causing notices on newer PHP versions
Autopay 4.9.1
- Fixed: the Payment started WooCommerce order status (Advanced → Payment statuses) is now applied when the customer begins checkout payment (standard redirect, Google Pay, and BLIK‑0). Previously the order was always set to Pending payment, ignoring this setting.
Autopay 4.9.0
- Google Pay on checkout is aligned with WooCommerce: the method is offered when shoppers must accept terms and conditions using a checkbox (classic checkout settings and block checkout with the Terms block checkbox enabled)
- Block checkout: payment method list reflects the same Google Pay availability rules as on classic checkout
- Classic checkout: smoother handling of the place order button in combination with Autopay checkout scripts
Autopay 4.8.3
- Analytics component – a new optional setting: “ITN SUCCESS triggering the event ‘Completion of transaction’ instead of order status”
Autopay 4.8.2
- Improved webhook processing logic for better integration with third-party plugins
- Adding a multilingual readme
Autopay 4.8.1
- Added support for additional currencies: USD (US Dollar) and GBP (British Pound).
- Improvements in ITN processing
- Updated library versions (php-ga4-mp, GuzzleHTTP)
- Fixed handling of unsupported currencies
- Fixed in the “Login during checkout” flow
- Minor fixes and improvements
Autopay 4.8
20252 releases
Autopay 4.7.1
- Changes to messages for test connection for the new supported version of PHP 8.3
- Changes to the text of the plugin configuration instructions
- Changes to the currency verification logic on the website
- Fix for test connection verification when sandbox mode is enabled for the administrator
- Fixed an issue with the Autopay plugin working in conjunction with other currency plugins
Autopay 4.7.0
- Added: gatewayList/v3 Added – integration with new endpoint
- Details:
- Extended configuration parameters
- Advanced communication with payment gateways
- Support for more payment options
- Improved: Test Connection – PHP 8.3 integration updated
- You can find all previous changes on Our Github..
Questions about Autopay’s releases
What is the latest version of Autopay?
5.1.0, released on Oct 26, 2026 (2 weeks ago). It’s tested up to WordPress 7.1.4 and needs PHP 7.4 or later.
How often is Autopay updated?
16 releases in the last year, about one every 22 days. Its first release on WordPress.org dates from August 2025.
Know when your rivals ship
Track your plugin and its rivals: TrackWP sees each new release in the nightly snapshot and alerts you, with what it did to their rank.
Start freeRelease dates come from the day each version’s folder was made in Autopay’s WordPress.org SVN repository; the notes from its readme’s changelog, as its authors wrote it.