Square payment links have suddenly stopped working across multiple applications simultaneously

[ymym1100]

Square payment links have suddenly stopped working across multiple applications simultaneously. This issue seems to coincide with the mandated implementation of 3D Secure in Japan. We haven’t made any changes to our code. Could you clarify what’s causing this? Does Square sometimes implement sudden specification changes? We’re currently unable to process payments, which is significantly impacting our operations. Your prompt response would be greatly appreciated.

I’m currently experiencing an issue where subscription payments are not working correctly, which seems to be related to the enforcement of 3D Secure as of March 31st.

I couldn’t find any official documentation regarding this update. Could you please provide a link to the relevant documentation, if available?

Also, if there is any specific implementation or code required to enable 3D Secure for Payment Links, I would appreciate it if you could share that information as well.

In Japan, there have been forum posts stating that 3D Secure is not mandatory for Japanese users. In fact, similar issues have been reported by other Japanese users just recently. However, when I inquired about this through support, I was told to contact the global team for issues related to the API.

As of now, the only message I have received is that “no changes are required on my end due to 3D Secure.” That being said, the issue still persists.

Could you please clarify:

• Is there any known global issue related to 3D Secure and Payment Links?
• Are there any fixes or updates being worked on at the moment?
• Should I be implementing something differently to ensure compatibility?

[Square-Dev-AI]

I’m Square Dev AI, here to help answer your question!
Based on the information you’ve provided, the following documentation will help answer your question:

Payment API: Process Online and In-Person Payments

Square Developer

Additional Documentation

Guidelines and Limitations
Strong Customer Authentication
Strong Customer Authentication

If this documentation helped you find a solution, please check the box indicating that this reply solves the problem.
Otherwise one of our Developer Advocates will provide additional assistance shortly.

[Bryan-Square]

No, there isn’t anything that you additionally need to do for 3DS with payment links created with the Checkout API. Is every payment link failing? Do you have an example?

[ymym1100]

Thank you for your reply.
Yes, the same issue occurs with payment links across all applications using the Checkout API.
For now, I understood that as a merchant, there is nothing specific I need to do on my end regarding the Checkout API.

Is my understanding correct that since there is nothing for us to handle on our end, this is a Square-side issue and we need to wait for Square to address it?

By the way, even payment links created manually via the Square dashboard are also failing.

We are currently in contact with Square Japan regarding this issue.
It would be greatly appreciated if you could also check on the status of Japan’s 3D Secure support in relation to the March 31, 2025 deadline from a global perspective.

[Bryan-Square]

What’s your application ID?

[ymym1100]

I sent you the application ID in the message.