• Resolved Wayne

    (@waynep16)


    When using plugins which allow product customisations that alter the price, eg https://www.studiowombat.com/plugin/advanced-product-fields-for-woocommerce/ the stripe BUY NOW Chrome pay button always charges the default product price and not the customised price from custom values.

    The Paypal buy now button works as expected and charges accordingly but not the Chrome / apple pay buttons. When doing from cart or checkout its fine but not from the single page.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Maarten

    (@maartenbelmans)

    Note this is also the case for the official WooCommerce Product Addons plugin. Any idea if/when an integration between Stripe and other Woo plugins will be possible?

    Plugin Support AW a11n

    (@slash1andy)

    Automattic Happiness Engineer

    Hey there!

    This is the case, yes. That is because the product add-ons (additional fields in your use case) are not a part of the product price, and are not picked up by payment requests like Apple Pay or Google Pay. This is not something that the plugin/services can do.

    Hopefully that helps! Have a great one!

    Thread Starter Wayne

    (@waynep16)

    Actually AW @slash1andy that is not true. The PayPal buy now buttons handle and manage this just fine and charge the correct amount with no problems what so ever. Your Dev team should use this as an example on how to support your customers instead of just disregard it. There are thousands of users facing the same issue and plus ones going back a year on your support board for this. Please take a look and issue a fix so we can re enable buy now buttons on the single item page. Thank you.

    Maarten

    (@maartenbelmans)

    Hi @slash1andy

    As far as I can see by diving into the code, all that would be needed are some actions & filters in your plugin so the developers of the WooCommerce Addons plugin (and other relevant plugins) can tie into it and update the product price sent by the plugin. Please note this is also the top user-request on the idea board (at the time of writing it has 100 votes): https://ideas.woocommerce.com/forums/133476-woocommerce?category_id=209980

    I think if your plugin adds an action to the end of its “build_display_items” function, other developers can start integrating their plugin. So as far as I can see, not much is needed to get things moving.

    @waynep16 is correct in saying that the plugin “WooCommerce PayPal Checkout Gateway” (also developed by WooCommerce) seems to do things differently and can therefore pick up addons from WooCommerce Addons. As such, it displays the price correctly in PayPal with addons attached to the product. Note I didn’t test this with advanced configurations but at least there seems to be a difference in how the plugin does things that would suggest this is possible.

    • This reply was modified 4 years, 6 months ago by Maarten.
    • This reply was modified 4 years, 6 months ago by Maarten.
    Thread Starter Wayne

    (@waynep16)

    Please can you come back to us @slash1andy

    • This reply was modified 4 years, 5 months ago by Wayne.
    Plugin Support dougaitken

    (@dougaitken)

    Automattic Happiness Engineer

    Hey all,

    To confirm – this compatibility would either be from the “add-on” plugin or our Stripe extension. There was some work done with the Stripe extension to add compatibility here:

    You can see how this was added for our Product Add-Ons extension here – https://github.com/woocommerce/woocommerce-gateway-stripe/issues/1099 and fixed in https://github.com/woocommerce/woocommerce-gateway-stripe/pull/1100

    I’m going to ask the developers to take a look and understand if we need to create a brand new issue to scope out this change better.

    Thanks,

    Maarten

    (@maartenbelmans)

    Hi @dougaitken

    That’s part of the problem: today, the Addon plugin can’t integrate as the Stripe plugin doesn’t offer any actions/filters to integrate with. The way I see it, your team has 2 options:

    1) implement actions/filters so other plugins can integrate with your plugin. This is the easiest solution for your team.

    2) Do things the way the official Woo PayPal plugin does (as stated earlier, that one seems to work with the addons plugin). This probably means rewriting some of your code and is likely more work.

    The pull request you linked does not seem to fix it, looking at the comments on the ideas board and my own testing. If I’m wrong, it would be great to have an official word on whether or not the Woo addons plugin is/will be supported.

    Plugin Support dougaitken

    (@dougaitken)

    Automattic Happiness Engineer

    Hey @maartenbelmans

    Would you or @waynep16 be able to open a new GitHub issue about this to restart the discussion with examples, please? After you’ve done that, let me know here.

    Thanks,

    Maarten

    (@maartenbelmans)

    @waynep16 I leave that up to you since it’s your initial request ??

    Plugin Support dougaitken

    (@dougaitken)

    Automattic Happiness Engineer

    Hey all,

    I’m going to mark this thread as Resolved and log this issue on GitHub in the next day or two.

    I’ll reply here with a link so we can loop back if needed

    Thanks,

    Maarten

    (@maartenbelmans)

    Thank you! Much appreciated ??

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘Not working with customisable products with the single item BUY NOW button’ is closed to new replies.