Square WebPay support thread.

[OJ_SIMON]

take a screenshot of when it hangs.

[BigB]

take a screenshot of when it hangs.

Screenshot of the hang at Step 2 of 3...

[royaldave]

Screenshot of the hang at Step 2 of 3...

Have you tried putting a real credit card number in there?

It won't charge it if you don't go past step 3.

[OJ_SIMON]

Have you tried putting a real credit card number in there?

It won't charge it if you don't go past step 3.

If that was the case the plugin should and would give a error and if not the API would return an error so either way the end user would know if it was that.

[OJ_SIMON]

If that was the case the plugin should and would give a error and if not the API would return an error so either way the end user would know if it was that.

but you only get to see API errors (if not show to screen) either in you dashboard or in web browser developer tools kit. both of which the OP has been asked to look in and has not reported there is any issues in either else we would of been able to advise a solution.

[BigB]

Have you tried putting a real credit card number in there?

It won't charge it if you don't go past step 3.

Indeed... I'm using the faux CC info Square provides for sandbox mode transactions... checkout just keeps getting stuck at Step 2... Nothing is getting over to Square... I have no info reaching the API so, no info in the logs on Square's end..

[BigB]

Some more information on this problem...
I want to mention @OJ_SIMON and thank him out here on the thread for his help with this. He has been kind enough to do some investigating in areas I don't know too much about and has found the "error" message that points to the problem. There's a few screenshots attached that give the error and what is causing it but, as of right now it's up in the air as to where exactly the problem is occurring.

The token info hs been checked to see if the issue/error was occuring there but, the token info appears to NOT be the source of the problem.. it appears to be somewhere else...


That's all on this as of yet.. any isnights, suggestion on where else to look is greatly appreciated

[BigB]

Some more information on this problem...
I want to mention @OJ_SIMON and thank him out here on the thread for his help with this. He has been kind enough to do some investigating in areas I don't know too much about and has found the "error" message that points to the problem. There's creenshots attached that give the error and what is causing it but, as of right now it's up in the air as to where exactly the problem is occurring.

We did inspect the token info to see if the issue/error was occuring there but, the token info appears to NOT be the source of the problem.. it appears to be somewhere else...


That's all on this as of yet.. any isnights, suggestion on where else to look is greatly appreciated

Two more screenshots..

[OJ_SIMON]

Two more screenshots..

what have you got set here: