Black Friday: 30% OFF on all plans, applied automatically at checkout View plans
Log in Cart

Clover for WooCommerce (ex FirstData) Changelog

Every recorded version, newest first, with what changed in each one.

Latest 5.4.115 versions

Undated · 15 versions

  1. 5.4.1

    Latest
    1 change
    Changes
    • Misc - Warn merchants on legacy First Data gateways (Payeezy, Payeezy Gateway, Global Gateway) to switch to Clover before they are retired
  2. 5.4.0

    2 improvements2 fixes3 changes
    Improved
    • Pass the WooCommerce customer ID to Clover when creating a charge
    • Add a filter to pass the customer billing name, email, phone to Clover charges so they appear in the transactions list
    Fixed
    • Subscription renewals should not fail with a missing payment token when the original subscription is purchased through the Blocks checkout
    • Replace deprecated `wc_enqueue_js` with `wp_add_inline_script` to address some WooCommerce deprecation notices
    Changes
    • Misc - Improve compatibility with more recent PHP versions
    • Misc - Update the SkyVerge Plugin Framework to v6.2.0
    • Misc - Require WordPress 6.3 or newer
  3. 5.3.3

    1 improvement1 change
    Improved
    • Trim whitespaces from postcodes at checkout to minimize AVS postal code mismatch errors in some cases
    Changes
    • Misc - Strip sourcemap comments from minified JS and CSS files in release builds to prevent browser console warnings
  4. 5.3.2

    1 improvement1 fix
    Improved
    • Improve error messaging when API credentials are invalid or unavailable
    Fixed
    • Do not bundle JavaScript .map files in the release to avoid console errors
  5. 5.3.1

    1 fix
    Fixed
    • Ensure the checkout works properly with the WooCommerce shortcode checkout
  6. 5.3.0

    2 fixes1 change
    Fixed
    • Ensure the card holder name is shown on the checkout block fields when enabled
    • Address WordPress deprecation notices concerning translations loading too early
    Changes
    • Misc - Update SkyVerge Plugin Framework to v5.15.12 (along with various security and bugfix updates)
  7. 5.2.9

    1 fix
    Fixed
    • Bump the framework version constant to the correct version
  8. 5.2.8

    4 fixes1 change
    Fixed
    • If a customer deletes their payment method directly by following an email response from Clover, ensure that it can be manually removed in WooCommerce as well
    • If a customer is deleted in Clover, ensure that payment methods can be deleted in WooCommerce without error
    • Ensure the "Capture Charge" bulk action is not shown on screens other than orders
    • Account for Subscriptions Core library when checking for Subscriptions
    Changes
    • Misc - Update SkyVerge Plugin Framework to 5.15.2
  9. 5.2.7

    1 new
    New
    • Add setting to enable AVS Cardholder name field on checkout
  10. 5.2.6

    1 improvement
    Improved
    • Allow changing payment method on subscriptions that aren't active when Clover is the set payment method
  11. 5.2.5

    1 fix
    Fixed
    • Do not show non-configured gateway notes in the admin area if the merchant has switched over another configured gateway
  12. 5.2.4

    1 fix
    Fixed
    • When adding a payment method from the My Account area, a pending draft order should not be created
  13. 5.2.3

    2 improvements2 fixes1 change
    Improved
    • Allow removing a payment token associated with a subscription due to Clover limitation of a single payment method per customer
    • Disallow paying with a new card with Clover for an order containing a subscription if there is already a saved card available, until removed
    Fixed
    • Address an issue with Subscriptions and recent WooCommerce versions when trying to output notices but the session is not set
    • Pass the locale information to Clover in the expected format
    Changes
    • Misc - Limit saving one payment method per customer as per Clover requirements
  14. 5.2.2

    1 fix
    Fixed
    • Ensure that the Clover payment form loads on the order-pay/customer payment page
  15. 5.2.1

    1 fix
    Fixed
    • Ensure that the Payeezy payment form wouldn't throw an error in some circumstances

Changelog published by the developer, in their original language.