Home / Forums / WoodMart support forum / Stripe conflict
Home › Forums › WoodMart support forum › Stripe conflict
Stripe conflict
- This topic has 5 replies, 2 voices, and was last updated 1 month, 3 weeks ago by
Artem Temos.
-
AuthorPosts
-
May 7, 2026 at 12:21 pm #717837
Icy55ParticipantHi,
I’m using Woodmart theme with WooCommerce and Stripe payment gateway. Apple Pay and Google Pay (Express Checkout) buttons are not showing on the checkout page, even though they are enabled in Stripe settings and working correctly on product pages.
After debugging, I found that the Stripe parameter
has_blockis set totrueon the checkout page, which causes Stripe to use block mode and not render Express Checkout buttons properly.My checkout page uses Elementor custom layout . The page uses the classic
[woocommerce_checkout]shortcode.Could you please advise:
1. Why ishas_blockbeing set totruewhen using the Woodmart checkout layout?
2. How can this be resolved so Apple Pay / Google Pay buttons appear on the checkout page?Thank you.
May 7, 2026 at 12:33 pm #717838Hello,
Thank you for purchasing WoodMart and reaching out to our support team. We’re here to help you with any issues.
To troubleshoot this issue, please deactivate all plugins except these essential ones:
– WoodMart Core
– WooCommerce
– ElementorIf the problem is resolved, reactivate your other plugins one by one to identify which one is causing the conflict.
If the issue persists even with all other plugins deactivated, please provide your admin credentials in a private reply and confirm permission for us to temporarily deactivate plugins and switch themes for testing (15-20 minutes). Please backup your site before providing access.
Best regards
May 7, 2026 at 1:49 pm #717850
Icy55ParticipantThe site is in production. I can’t just deactivate all. Also, the client would not be happy with sharing credentials.
I see many users have the same issue. Again, could you please advise: Why is has_block being set to true when using the Woodmart checkout layout?
Kind regards, IvanaMay 7, 2026 at 2:17 pm #717854In this case, you need to create a staging development copy of your website. There, you will be able to do such kind of experiments without any harm to your production website.
Kind Regards
May 7, 2026 at 2:31 pm #717856
Icy55ParticipantThank You for the answer. I have been using WordPress since 2009, I know staging very well.
I have asked just one question – Why is has_block being set to true when using the Woodmart checkout layout? Please, I just need an answer on this one – as this the debug showed me.
Kind regards, Ivana
May 7, 2026 at 4:23 pm #717880Hi Ivana,
The has_block flag isn’t something the theme sets. It’s determined by the checkout environment and depends on a combination of conditions specific to your site (plugins, templates, custom layout, scripts, etc.). Because of that, we can’t reliably say why it’s true on your checkout without inspecting your setup.
To give you a clear, definitive answer, we need to debug it on a staging copy where we can reproduce the issue.
Kind Regards
-
AuthorPosts
- You must be logged in to create new topics. Login / Register