Support » Plugin: WooCommerce Square » Cannot Add/Save a Payment Method (Credit Card)

  • Resolved mgraska


    The plugin is working great in terms of checkout but what doesn’t work is adding/saving credit card info in the “Payment Methods” section of the user account (/account/add-payment-method/):

    Whenever you try to add/save a payment method it results in a critical error:

    This is the log response:

    CRITICAL Uncaught Error: Call to a member function getTimestamp() on null in /wp-content/plugins/woocommerce-square/includes/Gateway.php:1138
    Stack trace:
    #0 /wp-content/plugins/woocommerce-square/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway.php(1687): WooCommerce\Square\Gateway->get_order_with_unique_transaction_ref(Object(WC_Order))
    #1 /wp-content/plugins/woocommerce-square/vendor/skyverge/wc-plugin-framework/woocommerce/payment-gateway/class-sv-wc-payment-gateway-direct.php(550): SkyVerge\WooCommerce\PluginFramework\v5_4_0\SV_WC_Payment_Gateway->get_order(Object(WC_Order))
    #2 /wp-content/plugins/woocommerce-square/includes/Gateway.php(264): SkyVerge\WooCommerce\PluginFramework\v5_4_0\SV_WC_Payment_Gateway_Direct->get_order(Object(WC_Order))
    #3 /wp-content/plugins/woocommerce-square/vendor/skyverge/wc-plugin-fram in /nas/content/live/reddyvineyards/wp-content/plugins/woocommerce-square/includes/Gateway.php on line 1138

    This also goes for attempting to add a card in the backend of the site ( except it doesn’t submit but throws an error in the console (

    What’s going on here?

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Support Aashik P. a11n


    Hi there!

    EDIT: Testing the latest version of Square and WooCommerce, I could replicate the same behavior.

    I’m reporting this to our developers as a bug. Please keep an eye out for the changelogs at to confirm when this is fixed

    • This reply was modified 2 months, 1 week ago by Aashik P. a11n. Reason: Answer updated after testing latest version
    Plugin Contributor mattdallan


    Hi @mgraska,

    We’ve just released v2.3.2 which fixes this fatal error you found.

    Thanks for reporting to us and apologies for any inconvenience this bug may have caused.

    I’m going to mark this as resolved, however, let us know if you’re still seeing the issue.

    Thread Starter mgraska


    I can confirm that this has been resolved. Thanks!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.