Title: wmacmill's Replies | WordPress.org --- # wmacmill [ ](https://wordpress.org/support/users/wmacmill/) * [Profile](https://wordpress.org/support/users/wmacmill/) * [Topics Started](https://wordpress.org/support/users/wmacmill/topics/) * [Replies Created](https://wordpress.org/support/users/wmacmill/replies/) * [Reviews Written](https://wordpress.org/support/users/wmacmill/reviews/) * [Topics Replied To](https://wordpress.org/support/users/wmacmill/replied-to/) * [Engagements](https://wordpress.org/support/users/wmacmill/engagements/) * [Favorites](https://wordpress.org/support/users/wmacmill/favorites/) Search replies: ## Forum Replies Created Viewing 15 replies - 1 through 15 (of 36 total) 1 [2](https://wordpress.org/support/users/wmacmill/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/wmacmill/replies/page/3/?output_format=md) [→](https://wordpress.org/support/users/wmacmill/replies/page/2/?output_format=md) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Disable Microdeposit ACH Option?](https://wordpress.org/support/topic/disable-microdeposit-ach-option/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [2 years ago](https://wordpress.org/support/topic/disable-microdeposit-ach-option/#post-17842252) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Disable Microdeposit ACH Option?](https://wordpress.org/support/topic/disable-microdeposit-ach-option/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [2 years ago](https://wordpress.org/support/topic/disable-microdeposit-ach-option/#post-17826715) * 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? * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Disable Microdeposit ACH Option?](https://wordpress.org/support/topic/disable-microdeposit-ach-option/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [2 years ago](https://wordpress.org/support/topic/disable-microdeposit-ach-option/#post-17826145) * 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](https://docs.stripe.com/payments/ach-debit/accept-a-payment?platform=web&ui=API#instant-only-verification) * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Unable to add ACH under “Payment Methods” in my account](https://wordpress.org/support/topic/unable-to-add-ach-under-payment-methods-in-my-account/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [2 years, 2 months ago](https://wordpress.org/support/topic/unable-to-add-ach-under-payment-methods-in-my-account/#post-17681615) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Gateway Based Fees and Discounts for WooCommerce] Issue with BuddyBoss theme](https://wordpress.org/support/topic/issue-with-buddyboss-theme/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [2 years, 3 months ago](https://wordpress.org/support/topic/issue-with-buddyboss-theme/#post-17501191) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[W3 Total Cache] Rejected Files still being passed to CDN](https://wordpress.org/support/topic/rejected-files-still-being-passed-to-cdn/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [3 years, 3 months ago](https://wordpress.org/support/topic/rejected-files-still-being-passed-to-cdn/#post-16564148) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Cache Images] not working – for googleusercontent.com](https://wordpress.org/support/topic/not-working-for-googleusercontent-com/) * [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [3 years, 7 months ago](https://wordpress.org/support/topic/not-working-for-googleusercontent-com/#post-16276041) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Error processing payment. Reason: public_token must be a non-empty string](https://wordpress.org/support/topic/error-processing-payment-reason-public_token-must-be-a-non-empty-string/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [3 years, 10 months ago](https://wordpress.org/support/topic/error-processing-payment-reason-public_token-must-be-a-non-empty-string/#post-15947470) * Also thanks for following up on it. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Error processing payment. Reason: public_token must be a non-empty string](https://wordpress.org/support/topic/error-processing-payment-reason-public_token-must-be-a-non-empty-string/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [3 years, 10 months ago](https://wordpress.org/support/topic/error-processing-payment-reason-public_token-must-be-a-non-empty-string/#post-15947468) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Error processing payment. Reason: public_token must be a non-empty string](https://wordpress.org/support/topic/error-processing-payment-reason-public_token-must-be-a-non-empty-string/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [3 years, 11 months ago](https://wordpress.org/support/topic/error-processing-payment-reason-public_token-must-be-a-non-empty-string/#post-15886861) * Found the conflicting plugin [https://wordpress.org/plugins/woocommerce-product-price-based-on-countries/](https://wordpress.org/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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Error processing payment. Reason: public_token must be a non-empty string](https://wordpress.org/support/topic/error-processing-payment-reason-public_token-must-be-a-non-empty-string/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [3 years, 11 months ago](https://wordpress.org/support/topic/error-processing-payment-reason-public_token-must-be-a-non-empty-string/#post-15886357) * 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 * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Conflict with Paytrace plugin for Woocommerce](https://wordpress.org/support/topic/conflict-with-paytrace-plugin-for-woocommerce/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [4 years ago](https://wordpress.org/support/topic/conflict-with-paytrace-plugin-for-woocommerce/#post-15747948) * I appreciate all the hard work from support on this! They were able to identify the issue and patch it. Thanks again for everything. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Payment Plugins for Stripe WooCommerce] Conflict with Paytrace plugin for Woocommerce](https://wordpress.org/support/topic/conflict-with-paytrace-plugin-for-woocommerce/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [4 years ago](https://wordpress.org/support/topic/conflict-with-paytrace-plugin-for-woocommerce/#post-15747638) * Super thanks I’ve sent the fatal error logs just now. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[Instant Images - One-click Image Uploads from Unsplash, Openverse, Pixabay, Pexels, and Giphy] API rate limit exceeded?](https://wordpress.org/support/topic/api-rate-limit-exceeded/) * Thread Starter [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [4 years, 3 months ago](https://wordpress.org/support/topic/api-rate-limit-exceeded/#post-15529586) * 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. * Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/) In reply to: [[WooCommerce Stripe Payment Gateway] Version 5.6 Critical error with Elementor](https://wordpress.org/support/topic/version-5-6-critical-error-with-elementor/) * [wmacmill](https://wordpress.org/support/users/wmacmill/) * (@wmacmill) * [4 years, 9 months ago](https://wordpress.org/support/topic/version-5-6-critical-error-with-elementor/#post-14926878) * v 5.6 is causing a lot of issues for multiple plugins for us. Do not recommend updating to this version until patched. Viewing 15 replies - 1 through 15 (of 36 total) 1 [2](https://wordpress.org/support/users/wmacmill/replies/page/2/?output_format=md) [3](https://wordpress.org/support/users/wmacmill/replies/page/3/?output_format=md) [→](https://wordpress.org/support/users/wmacmill/replies/page/2/?output_format=md)