• Hi,

    I was looking to switch from the automatic stripe plugin to yours as we are growing frustrated with the many bugs the crop up. I was just wanting to see if this plugin supports custom checkout fields when using express checkouts?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Clayton R

    (@mrclayton)

    Hi @jack01732

    Thank you for contacting us. Our Stripe plugin does not bypass the standard checkout flow, so any required fields that are on your checkout page will continue to be required when WooCommerce performs the field validations during the checkout process. The checkout process won’t proceed to payment if a required field is missing.

    One thing to note is wallet based payment methods like Apple Pay or Google Pay don’t have the ability to render custom fields inside their UI’s, but I don’t think that is what you’re asking.

    It sounds like you might have a custom field like a delivery date and you need to ensure that a value is provided for that field, even if a customer chooses to use an express checkout payment method.

    What I recommend you do is try our plugin in test mode on your staging site so you can go through all your common checkout scenarios. If you run into any issues or find a functionality gap, we can work with you to get those features supported.

    Kind Regards,

    tilluca

    (@tilluca)

    I’m having the same issue, since I need to collect important data before payment.

    @mrclayton mentioned that required fields shouldn’t be bypassed, but when I tested the plugin, the custom fields I marked as required are still being skipped when using Express Checkout.

    Did I misunderstand something, or is it that Express Checkout doesn’t respect required fields?

    Ideally, I want Express Checkout to only be available after the required fields have been filled out – or any other logic that makes sense in this case.

    Plugin Author Clayton R

    (@mrclayton)

    Hi @tilluca

    the custom fields I marked as required are still being skipped when using Express Checkout.

    It’s not that the fields are being skipped, because WooCommerce will always validate required fields during the checkout process server side. However, the express buttons don’t perform browser based validations on custom fields. The reason for that is because the express checkout is rendered at the top of your checkout page, so it’s meant to be the first thing your customer sees and uses.

    It doesn’t make sense to require a customer to enter values for fields that are below express checkout, then have them scroll back up to the top of the page and use express checkout. They would be better off just using the payment methods section which is rendered after the checkout fields.

    Kind Regards

    tilluca

    (@tilluca)

    Hi @mrclayton ,

    thanks for the quick reply.

    That’s what I suspected as well, but I’d really like to keep Express Checkout, since otherwise I’d lose Apple Pay and Google Pay as options.

    I figured I could work around this with a multi step checkout, but as soon as I switch from the block checkout to the old shortcode checkout, the styling of my checkout page breaks completely.

    What would you suggest if I want to keep Apple Pay and Google Pay, but still require customers to complete the required fields before they can pay?

    Plugin Author Clayton R

    (@mrclayton)

    Hi @tilluca

    That’s what I suspected as well, but I’d really like to keep Express Checkout, since otherwise I’d lose Apple Pay and Google Pay as options.

    Apple Pay and GPay are available in the payment method section of the checkout page if you’re using the checkout shortcode and there are some great options to beautify it and improve conversion rate.

    We work closely with the folks at CheckoutWC because they have the best checkout plugin for WooCommerce. They give merchants using our plugin a nice discount and a 30 day trial. https://www.checkoutwc.com/payment-plugins-stripe-woocommerce/

    My recommendation would be to try CheckoutWC since it will allow you to offer Apple Pay and GPay in the payment method section and will likely improve your conversion rates.

    Kind Regards,

    tilluca

    (@tilluca)

    Hi @mrclayton ,

    When I switch to the shortcode-based checkout, the checkout styling completely breaks. Here’s a screenshot: https://drive.google.com/file/d/18tE0kYT9buSwmc9Tp-so34xWTRsC1oD8/view?usp=sharing

    Have you seen this issue before?

    Plugin Author Clayton R

    (@mrclayton)

    Hi @tilluca

    Have you seen this issue before?

    That just looks like your theme isn’t optimized for the checkout shortcode, which would just require some simple CSS to resolve. You can share your website url if you would like us to review.

    I would still highly recommend giving CheckoutWC a try. Nothing you use is going to look better than that.

    Kind Regards

    tilluca

    (@tilluca)

    Hi @mrclayton

    here is a temp. link for the checkout: https://4work.cloud/checkout/

    Its the same with the cart. Thank you!

    Plugin Author Clayton R

    (@mrclayton)

    Hi @jack01732

    The issue is with the CSS file located in your wp-content/uploads/uicore-global.css file. It’s using a grid layout

    I would use a different theme as this one isn’t geared toward eCommerce from what I can tell. I also see you’re not using our Stripe plugin but rather the WooCommerce Stripe Gateway plugin.

    Kind Regards

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

The topic ‘Does this plugin support custom checkout fields when using express checkout?’ is closed to new replies.