• Resolved collithak1d

    (@collithak1d)


    Hello,

    We’re having a persistent issue with WooPayments on our site insygma.com, even after multiple reinstalls and resets.

    The admin panel (in every section in Payments) throws the following JS error:

    TypeError: Cannot read properties of undefined (reading ‘filter’)

    at Hg (https://insygma.com/wp-content/plugins/woocommerce-payments/dist/index.js?ver=10.1.0:2:558414)
    at Suspense
    at Pe (https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=f366037291a29b9582be:2:159395)
    at div
    at div
    at me (https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=f366037291a29b9582be:2:157939)
    at div
    at hw (https://insygma.com/wp-includes/js/dist/components.min.js?ver=865f2ec3b5f5195705e0:26:216841)
    at gw (https://insygma.com/wp-includes/js/dist/components.min.js?ver=865f2ec3b5f5195705e0:26:217484)
    at xw (https://insygma.com/wp-includes/js/dist/components.min.js?ver=865f2ec3b5f5195705e0:26:217829)
    at w (https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/admin-layout/index.js?ver=092d36684bd43b3c307d:1:1989)
    at Pn (https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=f366037291a29b9582be:2:220857)
    at O (https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=f366037291a29b9582be:2:126205)
    at P (https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=f366037291a29b9582be:2:125646)
    at a (https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=f366037291a29b9582be:2:120160)
    at https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=f366037291a29b9582be:2:223503
    at https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=16f5ad62bf91f83eb490:2:157128
    at https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=16f5ad62bf91f83eb490:2:158205
    at https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=16f5ad62bf91f83eb490:2:155018
    at https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=16f5ad62bf91f83eb490:2:155018
    at https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/data/index.js?ver=16f5ad62bf91f83eb490:2:156243
    at zn (https://insygma.com/wp-content/plugins/woocommerce/assets/client/admin/app/index.js?ver=f366037291a29b9582be:2:228602)

    The browser console shows multiple 404 responses for REST API requests such as:
    /wp-json/wcpay/settings
    /wp-json/wcpay/deposits
    /wp-json/wcpay/disputes

    and when accessed directly, /wp-json/wcpay/settings returns:
    {“code”:”rest_no_route”,”message”:”No route was found matching the URL and request method.”,”data”:{“status”:404}}

    So it seems WooPayments is not registering any of its REST routes (the /wcpay/* namespace).

    ✅ What we’ve already tried

    • Reinstalled WooPayments multiple times (versions 10.1.0, 10.0.1, and 9.6.0)
      → same result.
    • Ensured all plugins and WooCommerce core are on the latest versions.
    • Cleared all caches (OPcache, Redis object cache).
    • Manually deleted all WooPayments data from the database:
      wp_options entries with option_name LIKE ‘%wcpay%’ or ‘%woocommerce_payments%’
      wp_usermeta entries with meta_key LIKE ‘%wcpay%’
    • Ran WooCommerce > Status > Tools:
      Clear WooPayments account cache
      Clear WooCommerce.com cache
      Clear expired transients
    • Tested with incognito browser sessions.
    • Still, after reinstall, the plugin “auto-logs in” without asking to connect.

    🧩 Current behavior

    • WooPayments dashboard loads partially in the admin area.
    • Payouts tab always fails with 404 REST calls.
    • Even after full data deletion and cache clears, the plugin automatically reconnects to the same Stripe Express account (never shows the onboarding/login screen).

    ⚙️ Environment

    WordPress latest version
    WooCommerce latest version
    WooPayments tested versions: 9.6.0 → 10.0.1 → 10.1.0
    PHP 8.2
    NGINX server
    Redis object cache (flushed)
    Breakdance builder

    Please advise how to completely reset the WooPayments connection and force route registration.

    Thanks in advance for your help.

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

Viewing 1 replies (of 1 total)
  • Plugin Support Frank Remmy (woo-hc)

    (@frankremmy)

    Hi there,

    Thanks again for the detailed breakdown and all the troubleshooting you’ve already done—it’s clear you’ve been thorough in trying to resolve this.

    Since the issue appears to be isolated to WooPayments and not WooCommerce core functionality, I’ll go ahead and mark this thread as resolved on our end. For deeper investigation and support, I recommend opening a new topic in the dedicated WooPayments support forum.

    Looking forward to hearing from you there!

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.