v1.0.2 has been released to the community, and i wanted to say a few words about it.

  • if you are installing square webPay for the first time, this is the version to use.
  • if you are currently running v1.0.1 with no errors, then there is NO need to upgrade.
  • if you have having errors in your processing, v1.0.2 provides a little better help in troubleshooting.
  • if your store is installed in a subfolder, then you should definitely upgrade to v1.0.2.
  • if you are looking for a language other than english, then v1.0.2 is definitely the way to go.


allow me to say a few things about some of these issues.

square makes use of two tokens; one is the OAuth token, the other token is for the specific customer transaction and points to the cardholder information on the square servers. if you are having problems with your OAuth token, that means the merchant can not process ANY transactions. if you have problems with the cardholder token, that is for the individual transaction.

if you have followed this thread, you may have noticed that there was a lot of work done to ensure that square plays nice with OPC. that problem was with the cardholder token. if you are running into problems with the handler that problem is with your OAuth token.

in general, cardholder token problems should come up on the console of the browser prior to final submittal to square. once submitted to square, any problems with processing the transaction will result in a message to your customer using the zen-cart message stack.

sporadic problems with cardholder tokens are most likely indicative of javascript problems. these can be quite difficult to troubleshoot.

with v1.0.2, problems with your OAuth token are much easier to troubleshoot. you can turn verbose to true in the squareWebPay_handler.php file, and logs will get generated that should point you to the problem.

with regards to international support; this is all done on the admin side by entering a 2 character locale setting. the download has docs on where to look for that code; however not all browsers provide international support via the locale setting. this is something that is WAY out of my arena for support; however based on some research on my part after a previous request, it seemed like an easy enough addition to the code. i would think that most major browsers have this feature; but again, way out of my arena for support if it does not work on a specific browser.

as always, support for this module is here on the forum.

best.