G pay and Apple pay showing incorrect shipping cost for the purchaser address

Hi there!

I understand your concern and I’m happy to assist you in resolving the issue.

To help troubleshoot further, could you please confirm whether you’re using any third-party plugin to add different shipping zones, or are you using the default WooCommerce settings? By default, Google Pay and Apple Pay should pick up the shipping methods set in WooCommerce > Settings > Shipping.

Additionally, can you confirm if you recently added Google Pay or Apple Pay to your site, or if they were working fine before and the issue started suddenly? If this issue started after adding Google Pay, it could indicate a configuration issue.

If you’re not using a shipping zone plugin, I recommend running a conflict test. You can follow the instructions in this article: How to Test for Plugin and Theme Conflicts.

Running the conflict test will help us identify whether the issue is caused by a plugin or theme conflict.

Also, Could you please send me a copy of your site’s System Status? You can find it via WooCommerce > Status. Select “Get system report” and then “Download for support” (after you scroll down a bit)”. Once done, please upload it to this chat.

Thank you

Here are the answers I have for you so far 

• I am using the default Woocommerce shipping zones (Not a third party plugin)
• I have had Google pay and Apple Pay running on my site only recently., So I believe this issue is likely to have been in place since I turned on the? Google pay and Apple Pay payment option.?
• I have already tested for plug-in conflicts by briefly turning off all plugins with no success?
• I will need to set up a staging site Or something similar to test for theme conflicts.
  • I am using the Divi ? by Elegant Themes / Divi builder. (Which is a very popular theme) so I assumed that if there was a conflict with Divi that I would find some discussion about this online.?
  • I have not set up a staging site before to test a different theme, But if you feel this is worthwhile I can do so.
• ?I will upload the Site’s System Status?

Thanks for your help it’s most appreciated 

G

` WordPress Environment</p> <p>WordPress address (URL): https://woodenbowl.co.nz<br>Site address (URL): https://woodenbowl.co.nz<br>WC Version: 9.3.3<br>Legacy REST API Package Version: The Legacy REST API plugin is not installed on this site.<br>Action Scheduler Version: ? 3.8.1<br>Log Directory Writable: ?<br>WP Version: 6.6.2<br>WP Multisite: –<br>WP Memory Limit: 512 MB<br>WP Debug Mode: –<br>WP Cron: ?<br>Language: en_US<br>External object cache: – Server Environment</p> <p>Server Info: Apache<br>PHP Version: 8.2.18<br>PHP Post Max Size: 516 MB<br>PHP Time Limit: 60<br>PHP Max Input Vars: 1000<br>cURL Version: 8.7.1<br>OpenSSL/1.1.1w</p> <p>SUHOSIN Installed: –<br>MySQL Version: 5.7.23-23<br>Max Upload Size: 512 MB<br>Default Timezone is UTC: ?<br>fsockopen/cURL: ?<br>SoapClient: ?<br>DOMDocument: ?<br>GZip: ?<br>Multibyte String: ?<br>Remote Post: ?<br>Remote Get: ? Database</p> <p>WC Database Version: 9.3.3<br>WC Database Prefix: wp_<br>Total Database Size: 34.59MB<br>Database Data Size: 29.39MB<br>Database Index Size: 5.20MB<br>wp_woocommerce_sessions: Data: 1.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_api_keys: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_attribute_taxonomies: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_downloadable_product_permissions: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_woocommerce_order_items: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_order_itemmeta: Data: 0.08MB + Index: 0.09MB + Engine InnoDB<br>wp_woocommerce_tax_rates: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_woocommerce_tax_rate_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_shipping_zones: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_woocommerce_shipping_zone_locations: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_shipping_zone_methods: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_woocommerce_payment_tokens: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_woocommerce_payment_tokenmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_woocommerce_log: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_actions: Data: 0.36MB + Index: 0.30MB + Engine InnoDB<br>wp_actionscheduler_claims: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_groups: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_actionscheduler_logs: Data: 0.17MB + Index: 0.13MB + Engine InnoDB<br>wp_blc_filters: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_blc_instances: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_blc_links: Data: 0.06MB + Index: 0.11MB + Engine InnoDB<br>wp_blc_synch: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_commentmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_comments: Data: 0.08MB + Index: 0.09MB + Engine InnoDB<br>wp_et_divi_ab_testing_stats: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_giftvouchers_activity: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_giftvouchers_list: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_giftvouchers_setting: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_giftvouchers_template: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_jetpack_sync_queue: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_links: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_ms_snippets: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_options: Data: 6.38MB + Index: 0.58MB + Engine InnoDB<br>wp_postmeta: Data: 8.28MB + Index: 1.80MB + Engine InnoDB<br>wp_posts: Data: 11.09MB + Index: 0.30MB + Engine InnoDB<br>wp_snippets: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_termmeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_terms: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_term_relationships: Data: 0.06MB + Index: 0.05MB + Engine InnoDB<br>wp_term_taxonomy: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_usermeta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_users: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_wc_admin_notes: Data: 0.09MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_admin_note_actions: Data: 0.09MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_category_lookup: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_customer_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_download_log: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_orders: Data: 0.02MB + Index: 0.11MB + Engine InnoDB<br>wp_wc_orders_meta: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_addresses: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_wc_order_coupon_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_operational_data: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_order_product_lookup: Data: 0.02MB + Index: 0.06MB + Engine InnoDB<br>wp_wc_order_stats: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_wc_order_tax_lookup: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_wc_product_attributes_lookup: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_product_download_directories: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_product_meta_lookup: Data: 0.05MB + Index: 0.11MB + Engine InnoDB<br>wp_wc_rate_limits: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_reserved_stock: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_wc_tax_rate_classes: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wc_webhooks: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_wpmailsmtp_debug_events: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_wpmailsmtp_tasks_meta: Data: 0.02MB + Index: 0.00MB + Engine InnoDB<br>wp_yoast_indexable: Data: 0.19MB + Index: 0.09MB + Engine InnoDB<br>wp_yoast_indexable_hierarchy: Data: 0.02MB + Index: 0.05MB + Engine InnoDB<br>wp_yoast_migrations: Data: 0.02MB + Index: 0.02MB + Engine InnoDB<br>wp_yoast_primary_term: Data: 0.02MB + Index: 0.03MB + Engine InnoDB<br>wp_yoast_seo_links: Data: 0.14MB + Index: 0.11MB + Engine InnoDB<br>wp_yoast_seo_meta: Data: 0.17MB + Index: 0.00MB + Engine InnoDB Post Type Counts</p> <p>attachment: 886<br>custom_css: 1<br>et_body_layout: 1<br>et_pb_layout: 43<br>et_template: 6<br>et_theme_builder: 1<br>nav_menu_item: 15<br>oembed_cache: 3<br>page: 31<br>post: 10<br>product: 101<br>project: 47<br>revision: 318<br>shop_coupon: 2<br>shop_order: 87<br>shop_order_refund: 1<br>wp_global_styles: 1<br>wp_navigation: 1<br>wpgv_voucher_product: 3 Security</p> <p>Secure connection (HTTPS): ?<br>Hide errors from visitors: ? Active Plugins (15)</p> <p>AJAX Thumbnail Rebuild: by junkcoder<br>ristoniinemets – 1.14</p> <p>Akismet Anti-spam: Spam Protection: by Automattic – Anti-spam Team – 5.3.3<br>Broken Link Checker: by WPMU DEV – 2.4.1<br>Code Snippets: by Code Snippets Pro – 3.6.5.1<br>Disable Lazy Load: by Jeff Starr – 2.2<br>Gift Up: by Gift Up – 2.26<br>Health Check & Troubleshooting: by The www.remarpro.com community – 1.7.1<br>Jetpack: by Automattic – 13.9.1<br>Sold Out Badge for WooCommerce: by Charlie Etienne – 4.4.0<br>Themify – WooCommerce Product Filter: by Themify – 1.5.2<br>UpdraftPlus – Backup/Restore: by TeamUpdraft<br>DavidAnderson – 1.24.6</p> <p>WooPayments: by WooCommerce – 8.4.0<br>WooCommerce: by Automattic – 9.3.3<br>Yoast SEO: by Team Yoast – 23.7<br>WP Mail SMTP: by WP Mail SMTP – 4.1.1 Inactive Plugins (0) Must Use Plugins (2)</p> <p>Health Check Troubleshooting Mode: by – 1.9.2<br>SSO: by Garth Mortensen<br>Mike Hansen – 0.4 Settings</p> <p>Legacy API Enabled: –<br>Force SSL: –<br>Currency: NZD ($)<br>Currency Position: left<br>Thousand Separator: ,<br>Decimal Separator: .<br>Number of Decimals: 2<br>Taxonomies: Product Types: external (external)<br>grouped (grouped)<br>simple (simple)<br>variable (variable)</p> <p>Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog)<br>exclude-from-search (exclude-from-search)<br>featured (featured)<br>outofstock (outofstock)<br>rated-1 (rated-1)<br>rated-2 (rated-2)<br>rated-3 (rated-3)<br>rated-4 (rated-4)<br>rated-5 (rated-5)</p> <p>Connected to WooCommerce.com: –<br>Enforce Approved Product Download Directories: –<br>HPOS feature enabled: –<br>Order datastore: WC_Order_Data_Store_CPT<br>HPOS data sync enabled: – Logging</p> <p>Enabled: ?<br>Handler: Automattic\WooCommerce\Internal\Admin\Logging\LogHandlerFileV2<br>Retention period: 30 days<br>Level threshold: –<br>Log directory size: 506 KB WC Pages</p> <p>Shop base: #3497 – /woshop/<br>Cart: ? Page does not contain the [woocommerce_cart] shortcode or the woocommerce/cart block.<br>Checkout: #3411 – /checkout/ – Contains the [woocommerce_checkout] shortcode<br>My account: #3412 – /my-account/<br>Terms and conditions: ? Page not set Theme</p> <p>Name: Divi<br>Version: 4.27.2<br>Author URL: https://www.elegantthemes.com<br>Child Theme: ? – If you are modifying WooCommerce on a parent theme that you did not build personally we recommend using a child theme. See: How to create a child theme<br>WooCommerce Support: ? Templates</p> <p>Overrides: – WooPayments</p> <p>Version: 8.4.0<br>Connected to WPCOM: Yes<br>WPCOM Blog ID: 166351546<br>Account ID: acct_1Kgyq72EWju2PiSk<br>Payment Gateway: Enabled<br>Test Mode: Disabled<br>Enabled APMs: card<br>WooPay: Not eligible<br>Apple Pay / Google Pay: Enabled (product,cart,checkout)<br>Fraud Protection Level: basic<br>Multi-currency: Enabled<br>Auth and Capture: Enabled<br>Documents: Disabled<br>Logging: Enabled Admin</p> <p>Enabled Features: activity-panels<br>analytics<br>product-block-editor<br>coupons<br>core-profiler<br>customize-store<br>customer-effort-score-tracks<br>import-products-task<br>experimental-fashion-sample-products<br>shipping-smart-defaults<br>shipping-setting-tour<br>homescreen<br>marketing<br>mobile-app-banner<br>navigation<br>onboarding<br>onboarding-tasks<br>pattern-toolkit-full-composability<br>product-custom-fields<br>remote-inbox-notifications<br>remote-free-extensions<br>payment-gateway-suggestions<br>printful<br>shipping-label-banner<br>subscriptions<br>store-alerts<br>transient-notices<br>woo-mobile-welcome<br>wc-pay-promotion<br>wc-pay-welcome-page<br>launch-your-store</p> <p>Disabled Features: experimental-blocks<br>minified-js<br>product-pre-publish-modal<br>settings<br>async-product-editor-category-field<br>product-editor-template-system<br>blueprint<br>reactify-classic-payments-settings</p> <p>Daily Cron: ? Next scheduled: 2024-10-25 03:47:46 +00:00<br>Options: ?<br>Notes: 210<br>Onboarding: completed Action Scheduler</p> <p>Canceled: 2<br>Oldest: 2024-09-27 04:31:41 +0000<br>Newest: 2024-09-29 22:50:49 +0000</p> <p>Complete: 330<br>Oldest: 2024-09-24 05:06:49 +0000<br>Newest: 2024-10-24 18:26:39 +0000</p> <p>Failed: 694<br>Oldest: 2020-04-08 01:47:54 +0000<br>Newest: 2024-05-21 21:44:12 +0000</p> <p>Pending: 3<br>Oldest: 2024-10-24 19:08:24 +0000<br>Newest: 2024-10-25 06:01:40 +0000 Status report information</p> <p>Generated at: 2024-10-24 19:06:28 +00:00<br>`

How do you upload the  Site’s System Status file to this chat?

I’m sure it will be obvious but can’t find it

I tried pasting the report into the above but not sure it got all of it 

Just heading away for a couple days so might need to do this when I get home again 

Hello gavinbrunton,

Thank you for your reply.

I received the report, you shared it correctly.
You can also use the Code block to keep it in one line.

To confirm, this problem is only occurring with Google Pay and Apple Methods of WooPayments plugins. If we choose other payment methods the problem does not occur. Is that correct?

If that is the case, I suggest posting this issue at WooPayments plugin support.
Create a new topic, refer to this thread over there.

Additionally, share screenshots of your Shipping Zones and Shipping Methods.
This will help troubleshoot this issue more effectively.

Looking forward to your new topic. ??

You ask if the problem is isolated to  Google Pay and Apple Methods within WooPayments?

Yes I believe it is, So I will start a new post at WooPayments plugin support.

Could you just tell me if you can; does the Google Pay and Apple Pay rely on the address selected within Google Pay or Apple Pay to select the shipping methods and shipping cost built into the website?

Thanks

Hey @gavinbrunton ,

Thanks for creating a new topic in the WooPayments support forum!

If I’m not mistaken, Google Pay and Apple Pay typically rely on the address information selected within these wallet applications to calculate shipping options and costs on the site.

When Google Pay or Apple Pay is selected, the addresses stored within these wallets are passed to WooCommerce, which then uses this address to determine applicable shipping methods and rates for the order??.

Since further support for this will be provided in the WooPayments forum, I’m going to mark this topic as resolved, however feel free to create a new topic if you need any further help with WooCommerce core.

Hope this helps!

After some more testing I have narrowed down my issue.

When a client is using Google pay (or Apple Pay), if their shipping address is overseas, the correct shipping costs are displayed in google pay. 

BUT if their shipping address is within New Zealand (which is where I am based) the correct shipping cost is not displayed (instead the much more expensive “rest of world” shipping cost is displayed).

I believe the likely cause of this is;

For the correct shipping cost to be calculated on my checkout page both the country “New Zealand” and the Region within New Zealand needs to be selected. (I have different shipping zones set up for different regions within New Zealand). If somebody selects New Zealand on my checkout page but does not specify the region (Regardless of the delivery address they have entered) my website will display the “rest of world” shipping cost.

I am guessing that the address information coming from Google pay does not specify the region but simply supplies the address within New Zealand. 

Not sure if the answer lies in needing to modify my shipping zones within WooCommerce or request that Google pay includes Region as part of the delivery address?

Appreciate any suggestions you have on the best way forward.

Thanks

G

Hello gavinbrunton,

Thank you for your reply.

Since you have opened a new topic at the Woopayments forum, I suggest we continue this over there.

I will mark this issue as resolved on this forum.

Have a great day!