Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support shahzeen(woo-hc)

    (@shahzeenfarooq)

    Hi there!

    Just to confirm, are you looking to move the express checkout buttons under the cart collaterals section on the checkout page?

    If so, it’s worth noting that moving express checkout to the bottom of the checkout page can defeat its purpose. Express checkout is designed to let customers skip filling out billing and shipping information entirely — so placing it after those fields reduces its usefulness.

    By default, there isn’t a setting to change the position of the express checkout buttons, but it can be done with some custom code.

    I can recommend WooExperts and Codeable.io as options for getting professional help. Alternatively, you can also ask your development questions in the  WooCommerce Community Slack as custom code falls outside our usual scope of support.

    Thread Starter mcdeth

    (@mcdeth)

    Yes, I wanted to move the express checkout buttons to a different spot, still visible above the fold. Right now, after the page loads, there’s a slight delay while the JS processes, and then a dropdown appears — causing a layout shift (CLS), which looks pretty bad. I’ve never seen it on magento/shopify.

    I’m a bit surprised there’s no easy way to move the block, especially since this is built by Automattic. I would have expected it to follow WordPress best practices, like allowing repositioning with add_action or similar hooks.

    Crazy…

    Hi @mcdeth,

    Thanks for the clarification!

    You’re absolutely right, that layout shift can be frustrating. Since the express checkout buttons are injected via JavaScript, repositioning them isn’t currently possible through hooks like add_action.

    We agree this could be improved, and the best next step would be to submit a feature request here. That way, it can be reviewed for future updates.

    Thread Starter mcdeth

    (@mcdeth)

    yes, that answer could’ve been generated by ai too and Autoamtic could’ve saved some money so maybe they can hire devs?

    Because it’s not necessary to check on

    every

    single

    page view

    if user is still able to use google pay. i mean, God knows what’s going to happen on next page view right. why not discard caching too..

    Hi @mcdeth,

    Thanks for sharing your thoughts, we truly appreciate your feedback.

    Since WooPayments is an open-source plugin, we absolutely welcome contributions from the community. If you’d like to suggest improvements or propose a change to how Google Pay availability is handled, you’re very welcome to submit an enhancement request or even contribute directly through a pull request.

    Your input helps make the plugin better for everyone.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘moving express payment block’ is closed to new replies.