wmacmill

Just coming back to this to confirm that this plugin is no longer compatible with Woocommerce subscriptions then because in the current state it does not work if the user leverages microdeposits.

Hmmm interesting. I feel like this is a new thing though in the plugin since micro deposit wasn’t supported until v 3.3.70? The specific issue with this is if they select this on a WooCommerce subscription and go to update their payment method microdeposits the shift never actually happens. This is the specific issue we’re running into is subscriptions end up being moved to manual renewal because the credentials aren’t updated, and even once they validate the bank account information it doesn’t update the subscription payment method. The validated bank also doesn’t show up in their payment methods as an option to tie to the subscription. Everything in Stripe looks fine, but basically breaks everything in Woo Subs.

Am I missing something on how this should be working?

So stripe does allow for you to require instant verification. It should be possible when the plugin is creating the payment intent to require instant. I would think this could be a checkbox in the settings under ACH for example that would allow you to “disable microdeposits” which would change the payment intent to require instant? Let me know what you think.

https://docs.stripe.com/payments/ach-debit/accept-a-payment?platform=web&ui=API#instant-only-verification

Got it. Damn I thought you could add one and apply to all active subscriptions but I guess not then! One at a time it is for now.

I sent this data to them as well:

removeClass( “selected_payment_method” );

in the bb-woocommerce.js file.

This line attempts to use removeClass as a standalone function, which is incorrect in the context of jQuery. In jQuery, removeClass is a method that must be called on a jQuery object. The correct usage should target an element or a set of elements from which you want to remove a class. For example, if the intention was to remove the “selected_payment_method” class from an element that has been checked (selected), you should first select the element using jQuery and then call .removeClass() on that selection.

Below is an example of how this can be fixed:

$( document ).on( “change”, “form[name=’checkout’] input[name=’payment_method’]”, function () {
? ? if ( $( this ).is( ‘:checked’ ) ) {
? ? ? ? $( this ).addClass( “selected_payment_method” );
? ? } else {
? ? ? ? // Assuming the intention is to remove the class from all inputs that are not checked
? ? ? ? $(“form[name=’checkout’] input[name=’payment_method’]”).removeClass( “selected_payment_method” );
? ? }
});

Basically this is the issue in a nutshell and needs to be updated in the core theme.

I did test those and suspect it’s something related to our server settings and/or how our developer has it set up as it still serves it. I have them digging into it and will update when I have more information. Thanks.

I can confirm this as well. Having a similar issue but only with the automatic save on posting, not if I run the search manually.

Also thanks for following up on it.

I was not able to – updates along the way seem to have resolved whatever the underlying issue was and we seem to be no longer experiencing it.

Found the conflicting plugin https://www.ads-software.com/plugins/woocommerce-product-price-based-on-countries/ but what’s weird is they haven’t had an update in over 2 months so trying to narrow down what it could be.

So no issue with the response – everything coming back 200 for ?wc-ajax=wc_stripe_frontend_request&elementor_page_id=3989&path=/wc-stripe/v1/plaid/link-token

I appreciate all the hard work from support on this! They were able to identify the issue and patch it. Thanks again for everything.

Super thanks I’ve sent the fatal error logs just now.

Got it ok good to know because I was searching around trying to figure out if I can put in my own API key and wasn’t sure where to do that! Thanks for looking into this.

v 5.6 is causing a lot of issues for multiple plugins for us. Do not recommend updating to this version until patched.