{"title":"Website v20.0.42 - 31 March 2026","slug":"website-v20-0-42","url":"https://support.storeconnect.com/articles/website-v20-0-42","url_markdown":"https://support.storeconnect.com/articles/website-v20-0-42.md","subtitle":null,"summary":"This patch fixes an Apple Pay merchant validation issue for stores using Westpac (Verifone) where domain formatting differences between environments could cause validation to fail.","type":"Release_Notes","video_url":"","keywords":"release notes, update","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"This patch fixes an Apple Pay merchant validation issue for stores using Westpac (Verifone) as their payment provider, where inconsistent domain formatting between sandbox and production environments could cause Apple Pay to fail at checkout.\n\n## Breaking changes and cautions\n\nNo breaking changes in this release.\n\n## Enhancements\n\nNo enhancements in this release.\n\n## Deprecated fields\n\nNo fields have been formally deprecated in this release.\n\n## Fixed bugs\n\n**Apple Pay not working reliably for Westpac (Verifone) merchants** [WEB-7771]\nWhen a customer initiated an Apple Pay payment, StoreConnect performs a merchant validation step with the Verifone API to confirm the payment session is legitimate. This validation was passing the store domain in different formats depending on whether the environment was sandbox or production, which caused validation to fail in some configurations. The domain is now always passed as a plain hostname (for example, `yourstore.com`) regardless of environment, matching what the Verifone API expects, and Apple Pay merchant validation works consistently across all environments."}