Hi there!
I understand the issue you’re facing with BLIK payments. The errors you’re seeing “Missing required customer field: address->city” and “Missing required customer field: address->country” usually indicate that the payment gateway isn’t receiving the billing/shipping address data correctly, even if it appears to be filled out in checkout.
To assist you further, I’d like to understand your site properly. Please share with us the necessary information below for us to investigate the issue further:
- System Status Report which you can find via WooCommerce > Status
- Fatal error logs (if any) under WooCommerce > Status > Logs.
Please use https://pastebin.com/ or https://gist.github.com/ and share a link to that paste in reply here. Once we have more information, we’ll be able to assist you further.
Thread Starter
manx89
(@manx89)
Hi,
in logs I have something like this. I tried just now to place order and this is how it looks like:
https://pastebin.com/F5gZPbE0
Thread Starter
manx89
(@manx89)
I fixed it by adding this hook.
https://pastebin.com/y2tW8LJH
Hi @manx89,
Thank you for sharing the logs and for detailing the hook you used, I can see the effort you put into tracking this down and implementing a fix.
From the log you shared, it is clear that Stripe is returning a missing_required_customer_field: address->city error during payment processing, even though the payment_method object already contains valid billing details such as city and country. This typically points to a timing or data sync issue where the billing details are not being properly attached to the Payment Intent at the moment it is created for BLIK transactions.
Your custom hook is a solid approach here. By hooking into wc_stripe_generate_create_intent_request and explicitly updating the payment_method billing details via the Stripe API before the intent is finalized, you are ensuring that the required address fields are present and available when Stripe validates the request. This aligns well with what the gateway expects for payment methods like BLIK that rely heavily on complete billing data.
This also explains why the checkout form appeared correct, but Stripe still raised the error, as the issue was not with WooCommerce form validation but with how the data was being passed to Stripe at processing time.
For reference, more details on how Stripe handles Payment Intents and required fields can be found here: https://docs.stripe.com/api/payment_intents.
Since your workaround is now ensuring the billing details are properly synced, it makes sense that the issue is resolved on your end. This could be specific to how BLIK interacts with the UPE flow, and your solution effectively bridges that gap.
If you notice any edge cases, such as guest checkout or different address formats behaving differently, feel free to share and we can take a closer look.
Appreciate you sharing the solution back here as well, it will definitely help others facing a similar issue.
It seems we haven’t heard back from you for a while, so I’ll go ahead and mark this thread as resolved. Feel free to reach out whenever you’re ready to continue.
We’d really appreciate if you could take a moment to leave us a review: https://wordpress.org/support/plugin/woocommerce-gateway-stripe/reviews/
