Hello Sarah,
Thank you for reaching out to us.
This behavior is often related to how “Express Checkout” buttons (like Apple Pay or Google Pay on the product page) function. These buttons frequently bypass the standard WooCommerce “Add to Cart” process and its associated hooks, which our plugin relies on to capture and save custom field data to the cart and subsequently to the order. When the standard flow is bypassed, the metadata may not be correctly attached to the line item.
To help us investigate this matter further, please try the following troubleshooting step:
- Check AJAX settings: In many cases, the “AJAX add to cart” feature can interfere with the data transmission of custom fields. Please verify if this feature is enabled in your theme settings or under WooCommerce → Settings → Products → General. If it is active, please try disabling it temporarily and test if the Apple Pay checkout then includes the field data.
If the issue persists, we would appreciate it if you could provide us with the following information:
- WooCommerce System Status Report: You can find this in your WordPress dashboard under WooCommerce → Status → Get system report. This will help us identify your current environment and the payment gateway plugin you are using for Apple Pay.
- Screenshots of your field configuration: Specifically the settings for the fields that are missing from the orders.
Please note that if the payment gateway’s express button is designed to completely skip the WooCommerce cart validation and processing, it may require a custom integration to ensure compatibility with product add-ons. If that’s the case, we may be unable to help.
Kind regards,
Hi @sebastianrybacki thank you for your really helpful answer.
I tried disabling Ajax but the issue persisted.
– For the next step, where would I send the system reports and screenshots to?
– How do I check if Stripe Apple Pay meets this condition ‘ if the payment gateway’s express button is designed to completely skip the WooCommerce cart validation and processing’ ?
Hello Sarah,
Thank you for your follow-up message — I appreciate you checking the AJAX setting.
Okay, we can forward without your system status and screenshots. What would be most helpful for us now is to know exactly which plugin you are using to handle Apple Pay (for example, the Stripe integration plugin name and version).
Once we have that information, I can review how that specific integration handles Express Checkout and verify whether this is something we can address on our side, or if it’s a limitation of the payment gateway’s implementation.
Kind regards,
Hi thank you, a check would be super useful
I’m using WooCommerce Stripe Gateway v10.5.3
I’ve enabled express payments under WooCommerce > Settings > Payments > Stripe > Payment Methods
Thank you for looking into this
Sarah
Hello Sarah,
Thank you for your message.
Based on the plugin you’re using (WooCommerce Stripe Gateway v10.5.3) and the enabled Express Payments, I can confirm that this behavior is caused by the way Express Checkout (Apple Pay on the product page) works.
In this flow, the checkout is initiated directly from the product page and bypasses the standard WooCommerce cart and checkout process. Unfortunately, our plugin relies on that standard flow to correctly capture and attach Flexible Product Fields data to the cart and order. Because of this, the field data is not reliably saved when using Apple Pay via Express Checkout.
At the moment, our plugin is not compatible with Express Payment methods like this.
To ensure everything works correctly, the recommended approach is to use the standard purchase flow:
- Add the product to the cart
- Proceed to the checkout page
- Complete the order there
This ensures all custom fields are properly validated and saved to the order metadata.
For now, we’re not able to provide an immediate fix or workaround for Express Checkout compatibility. However, this is something we’re aware of and have already noted as a potential improvement for future updates.
I’ve also added you to our internal list of users interested in this functionality — if we’re able to introduce compatibility in the future, I’ll be happy to let you know.
Kind regards,
Thank you very much @sebastianrybacki for explaining fully and clearly. I find it much better to understand the issue, so I will now turn off the Express Checkout compatibility.
Thank you for adding me to the list for future updates if this happens, I would love to hear and implement it if it becomes possible.
Thanks again for your help, I’m sure this thread will help others, I’ll close and resolve.
Sarah
