Hey! This is likely because your customers are using express payment buttons (Apple Pay, Google Pay) from the product page, which uses draft orders
Thread Starter
willf
(@willf)
@senadir I only have Apple Pay & Google Pay setup at the checkout page, not on a product page. I suspected this may be the culprit but then dismissed it because those customers that raise another order very often use a standard credit card checkout.
The ones on Checkout (both) also use Store API, you can test it yourself
Thread Starter
willf
(@willf)
@senadir I have tried replicating the problem but all works fine for me. I have disabled Apple/Google Pay and so far no Draft orders so it was obviously the problem.
Yes I’m aware 😀 In which case what you were seeing is perfectly normal.
Draft orders is part of the new system in which we process checkouts from anywhere, the legacy shortcode Checkout however, is on a different system. So you will continue seeing draft orders (though we’re working on making it show up less and instantly change to a valid status).
Thread Starter
willf
(@willf)
@senadir I see there is an updated Stripe plugin (v11.0) out that addresses several problems with Express checkouts, hopefully this will sort my problem. I know you say draft orders are normal but not when the customer has to comeback to the checkout page and start the whole process again.
Thread Starter
willf
(@willf)
@senadir I think I have figured it out now. I had a plugin called email validation that made customers enter their email twice just to make sure it was correct. It looks like Express checkouts have been failing because the checkout process was requesting both email sections be filled out but when Express was being used it was only using the primary email section. Funny though how it has been working for nearly 12 months.
2026-09-10T19:35:01+00:00 Error Missing required custom fields in express checkout.
Additional context
{
"stripe_version": "11.0.0",
"stripe_api_version": "2026-03-25.dahlia",
"missing_field_keys": [
"billing_email-2"
],
"error_message": "Confirm Email Address is a required field.",
Oh! Nice findings, @willf! Happy to know that you were able to spot that.
I’m pretty sure it should be working like a charm now, right?
Thread Starter
willf
(@willf)
@gabrielfuentes so far so good 🙂
awesome!! I’m glad to read that! 🙂
If you have a few minutes, we’d love it if you could leave us a review: https://wordpress.org/support/plugin/woocommerce/reviews/
have a great weekend!
