What’s your application ID? 
Sent this to you in your DMs
Mind sharing it here? Any ID I ask for is safe to share. Only an access token isn’t safe to share. Also the team made additional changes to help this. Let us know if your still facing this issue.
sq0idp-5Sc3Su9vHj_1Xf4t6-9CZg
Are you seeing any improvements since the team has made a change?
It’s a stall that I can’t reproduce myself. I only get notification from some percentage of customers that run into the problem. I’m not sure how many customers run into the problem and don’t bother to reach out. All I can tell you is Square devs broke something and they should revert whatever A/B testing they’re doing that might be causing it because it has caused a regression in production. Because of this and the Sept 2023 outage I’ll be looking into building in alternative payment processors into my application. I would ask @johnbona @shaebukhan34 @spiffybrian to see if they can still reproduce.
I’d echo the concerns voiced here. This is something that we can’t verify as we only get feedback from the percentage of customers who make a complaint. We have no way of monitoring these failures.
Firstly, this issue should not be happening at all. This is a failure on the part of Square and so far, they have not been forthcoming about the bug or its impact on merchants and customers.
Secondly, there is a fundamental bug in the payments widget API in that it allows a call to the tokenize routine that never returns. If the API was properly written, when the new Proof of Work functionality was added, the developers should have realized that they are able to define conditions that mean the routine goes into an essentially infinite loop, and should have provided a timeout exception to cover this possibility. If we had a timeout on the condition, we would then be able to monitor the level of failures.
This is a massive failure on the part of Square that has allowed this sort of flawed execution to get into production, affecting many merchants world-wide. Who knows how much has been lost in sales over the Christmas period due to this error?
1 Like
Any updates on this issue? Have square devs been able to reproduce it?
We made some updates on our end. Are you still experiencing this?
I checked with two nice customers that were willing to attempt to place an order. It looks like it has now been fixed! Can we get a postmortem on this?
Pretty much everything on this is internal to Square. An internal service was degraded which caused the issue. The team was able to identify the issue and deployed a fix.