Confermo che la soluzione trovata da Francesco funziona perfettamente. Per chiunque altro sia bloccato, il percorso esatto è: wp-content/plugins/cartasi-x-pay/src/classes/Nexi/BlockSupport/ Basta rinominare il file WC_Gateway_Xpay_Blocks_Support.php in WC_Gateway_XPay_Blocks_Support.php (cambiando semplicemente la “p” in “P” maiuscola).
Detto questo, vorrei lasciare un feedback diretto a Nexi: è estremamente frustrante e inaccettabile che un gateway di pagamento ufficiale faccia crashare un intero sito web mandandolo in Fatal Error per un errore di battitura così ridicolo.
È una vera e propria vergogna e la classica superficialità “fatta all’italiana”. Rilasciare un aggiornamento in produzione senza nemmeno fare un test di base per controllare se il plugin si attiva o meno è assurdo. Complimenti vivissimi agli sviluppatori per aver causato disservizi a chissà quanti negozi online per una lettera.
Thank you for your reply and clarification. However, I must express my strong dissatisfaction with how WooCommerce Payments handles Apple Pay and Google Pay during express checkout.
It is unacceptable that your plugin completely ignores the data entered in the standard WooCommerce checkout form, including required billing fields, custom fields, and terms & conditions — and that there is no built-in option to override or control this behavior.
Other payment gateways such as Mollie and Nexi allow Apple Pay and Google Pay to function after the checkout form is completed, preserving all the entered data and ensuring compliance with legal and tax requirements (especially important for countries like Italy).
This limitation makes WooCommerce Payments unusable for businesses that require accurate billing data and legal confirmations from customers.
Due to this critical issue, I will very likely switch to an alternative payment provider that offers better control and reliability.
I sincerely hope you will consider adding an option in your plugin to allow express checkout to respect the data entered in the WooCommerce form, or at least provide a developer hook to enforce this behavior.
Hello, I have already tested this thoroughly by disabling all plugins and switching to a default theme.
I have a simple and straightforward question regarding WooCommerce Payments.
When using Apple Pay or Google Pay via WooCommerce Payments, does the plugin actually consider the data entered in the standard WooCommerce checkout form (such as billing fields, custom fields, and terms & conditions), or is this data entirely ignored in favor of the information pulled from the Apple/Google Wallet?
I’m asking because with other gateways like Mollie or Nexi, even when Apple or Google Pay is selected, the payment is processed after the WooCommerce checkout form is completed — ensuring that all required fields (including tax-related fields and legal confirmations) are properly validated and included.
With WooCommerce Payments, however, it appears that the express checkout process bypasses the form entirely, which creates serious issues in countries like Italy, where collecting complete and accurate billing and tax information is a legal requirement.
Could you please clarify how this works, and whether there is any official way to enforce form validation or ensure the use of the form data when processing express checkout via Apple or Google Pay?
I understand the confusion and I’d like to clarify the issue in more detail.
In our checkout page (please refer to the first screenshot – sorry it’s in Italian), several fields are marked as required, such as first name, last name, email address, and acceptance of the terms and conditions, VAT…. When a customer tries to pay using a credit card without filling in these required fields, the system correctly prevents the order from being processed and displays validation errors.
However, when using Google Pay, the customer can proceed with the payment even if all and required fields are left empty, including the acceptance of the terms and conditions. This means that an order is created without collecting the required billing details, which is a major issue for us.
To answer your question: yes, the name and email do appear in the order after the Google Pay transaction, but they are pulled directly from the customer’s Google account, not validated through our checkout form. As a result, none of the other required billing fields are captured or enforced.
Please let us know how we can ensure that the required checkout validations are respected even when using express payment methods like Google Pay.
We confirm that we previously used some plugins that customized the checkout page, specifically:
Checkout Field Editor for WooCommerce
Direct Checkout for WooCommerce
However, these plugins have been uninstalled, and the issue with Google Pay / Apple Pay still persists: the billing details are not being saved in the order, unlike with traditional payment methods.
Additionally, please note that we sell only virtual products delivered via download, and therefore we do not use any shipping fields at checkout.
We are currently using the Woodmart theme, which may apply some styling or layout changes to the checkout page, but we haven’t implemented any custom code manually.
➤ Here is the System Status Report: https://pastebin.com/zYrhFtAh ➤ Please find attached a screenshot of one of the affected orders.
Let us know if you need temporary access or if you would like us to run specific tests.
