yamatomooo

Hi Frank,

Thank you very much for the detailed investigation and clarification.

I appreciate you escalating this internally to the development team.

I may be slower to respond over the next couple of days due to work, but I will continue to provide any additional information if needed.

Thank you again for your support.

Hi Frank,

Thank you for your confirmation.

I understand that the issue could not be reproduced in a clean environment using Square sandbox test cards.

Regarding your requested items, please see the following:

• System Status Report / WooCommerce Square logs
The previous QuickForget link had expired, so I uploaded the files again using a new link:
https://quickforget.com/s/8386518c387f816f0c305ba7c3f0817cc17c7e2d5fc20314

• VISA card issuing country
All failing VISA cards are Japanese-issued cards.

• curl timing test
I ran a curl timing test from the XSERVER environment against:
https://connect.squareup.com

Result:
DNS:0.189 Connect:0.196 SSL:0.244 TTFB:0.368 Total:0.368

The response time appears normal and does not seem to indicate significant latency.

Thank you again for your assistance, and I appreciate your continued support.

I may be slower to respond over the next couple of days due to work, but I will continue to provide additional information as needed.

• This reply was modified 2 weeks ago by yamatomooo.

Hi @lovingbro,

Thank you for your reply.

I will prepare the WooCommerce System Status Report and relevant logs, with sensitive information removed, and share them shortly. Please allow me some time.

Here is some additional information based on our current testing:

• The issue occurs mainly on desktop Chrome browsers.
• JCB cards work correctly.
• MasterCard also works correctly.
• Only VISA cards sometimes fail during the 3D Secure authentication flow.
• The same VISA card has successfully completed payment on mobile browsers in some cases.
• Similar behavior has been observed with multiple VISA cards.
• In the Square Dashboard, failed VISA transactions are recorded as “Not Authorized”.
• The WooCommerce checkout API response contains:
  "payment_status": "failure"
"payment_details": []
• The site response header only includes:
  Content-Security-Policy: frame-ancestors 'self';
  so it does not appear that our site is directly blocking Square CDN resources.

We also found additional behavior during testing.

When testing on another desktop PC environment, initially the Square card input fields did not appear at all, and the following error appeared in the browser console:

Web Payments SDK was unable to be initialized in time

However, after some time, the card fields appeared correctly and a VISA payment was completed successfully.

Immediately after that successful transaction, we repeated the test using the same VISA card, same browser, and same PC environment, but the payment failed again.

During the failed attempt, the VISA 3D Secure authentication screen (one-time password challenge) displayed correctly and authentication completed successfully, but the following console errors appeared afterward:

TokenizationError: Tokenization has failed
An error occurred while verifying the buyer

Based on this behavior, it appears the issue may not occur before the 3D Secure challenge starts, but rather during the buyer verification / tokenization process afterward.

We also confirmed that the CSP / font-related console warnings appear even during successful transactions.
Therefore, those warnings themselves may not be the direct cause of the payment failures.

I will share the logs and screenshots once they are ready.

Thank you.

早速のご回答、誠にありがとうございます！

近日中に検証して、またご連絡させていただきます。

ありがとうございます！