Square WebPay support thread.

carlwhat:

it does not work.

best.

Would you please then change the compatibility with 1.5.6 on the module? It says it is compatible and I installed in a customer's store and not only is not showing up I can't configure any payment module because the config box is not coming up on any of them.

ideasgirl:

Would you please then change the compatibility with 1.5.6 on the module? It says it is compatible and I installed in a customer's store and not only is not showing up I can't configure any payment module because the config box is not coming up on any of them.

here is an idea... don't misquote me...

i clearly stated not compatible with v1.5.5.

your image has now clearly deteriorated in my book.

maybe someone else can help you...

best.

Sorry for the misunderstanding carlwhat. I quoted you because you said IT'S NOT COMPATIBLE and I thought that on the module downloads area said 1.5.5 compatible but I just rechecked and it says 1.5.6. This is a combination of not using glasses and lack of sleep these days.... I apologize for not checking 5 times instead of 2 times before my post. :blush:

ok.

based on what you said, you should have log files getting generated.

post them if you would like some help.

carlwhat:

ok.

based on what you said, you should have log files getting generated.

post them if you would like some help.

ok, i'm the ones that needs glasses now. if you are running zc v155, square webpay is not supported.

best.

@ideasgirl 1.5.5 is over 5 years old, and only runs on PHP versions that are no longer supported. Your client needs to upgrade.

carlwhat:

ok, i'm the ones that needs glasses now. if you are running zc v155, square webpay is not supported.

best.

:laugh: Thank you! Don't worry.... I uninstalled both plugins and everything is fine now.

@ideasgirl 1.5.5 is over 5 years old, and only runs on PHP versions that are no longer supported. Your client needs to upgrade.
Yes, she has been advised but it has been 2 bad years for her in terms of revenue. She's planning to start the transition in the 1stQ of 2023.

Don't forget the option of the El-Cheapo Quickie Econo-Upgrade (tm) procedure:

https://docs.zen-cart.com/user/upgrading/db_only_upgrade/

ideasgirl:

Yes, she has been advised but it has been 2 bad years for her in terms of revenue. She's planning to start the transition in the 1stQ of 2023.

We are looking after a site where the owner is in a similar cashflow position. (We stopped developing 3rd-party sites over 10 years ago, but the owner of this site is a long-standing business acquaintance).

We agreed to keep the site "current" for him, on the basis of getting a small percentage of sales revenue.
Effectively, it's in our interest therefore, to ensure the site's functionality. The more sales he makes, the greater our commission. It will definitely take a while before we get "fully paid", but at least we're seeing a trickle of revenue, and more importantly, the website is operational and efficient, so our client is scraping by as well.

Perhaps you could discuss a similar arrangement with your customer...

I have Square WebPay logging set to Always and Verbose set to true in the handler. Should I receive a log on successful token refresh when the handler is run from a cron job (the automated token refresh method), and when the manual token refresh approach documented in storeowner docs, i.e., click edit then click update in the admin Square WebPay payment module?
Thank you!
Dave

Dave224:

I have Square WebPay logging set to Always and Verbose set to true in the handler. Should I receive a log on successful token refresh when the handler is run from a cron job (the automated token refresh method), and when the manual token refresh approach documented in storeowner docs, i.e., click edit then click update in the admin Square WebPay payment module?
Thank you!
Dave

dave,
i do not run a production site using square. so hard for me to say exactly.

when running a cron job for the handler, you should check how you have the output configured for your cron jobs. there will be output there, but that output is completely handled via cron.

it does NOT look like this module will generate a php log (ie, a zen-cart log) on successful token refresh. but the cron job will have output.

when doing a manual refresh, there will be a php log (ie a zen-cart log) even when there is a successful token refresh.

hope that helps.

best.

Any interest in adding Affirm Afterpay to the premium version of this plugin?

swguy:

Any interest in adding Affirm to the premium version of this plugin?

it is not a bad idea. but it looks to be afterpay. see:

https://squareup.com/us/en/buy-now-pay-later

i am not sure which of the three is the best, affirm v afterpay v klarna; or if they are all just similar products from different payment processors.

i will take a look time permitting.

thanks.

swguy:

Any interest in adding Affirm Afterpay to the premium version of this plugin?

yeah, in briefly looking at the code, it's probably best to build a separate payment module to extend square webpay. similar to what i did with auth.net card on file transactions.

the selection method does NOT allow for multiple selections within a payment module. it looks for an array with the keys: id, module, and fields.

little thought for food.

best.

Thanks for that suggestion :smile: I've thought about that before but I'm struggling myself, too. :lookaroun I will give it a thought again and discuss it with her (since she's also a friend). She's been a customer and a ZC user since v1.2.6.

I found this error in the log files after the customer had trouble with payment:
--> PHP Fatal error: Uncaught TypeError: Square\ApiHelper::serialize(): Return value must be of type string, bool returned in /home2/rcracean/public_html/silversalt/includes/modules/payment/square_webPay/square/square/src/ApiHelper.php:113

I did not receive any Square Alert mail about this error.
I use Zen Cart v1.5.7d and php 8.0.25

Has anybody any idea what could cause this error?

todoonada:

I found this error in the log files after the customer had trouble with payment:
--> PHP Fatal error: Uncaught TypeError: Square\ApiHelper::serialize(): Return value must be of type string, bool returned in /home2/rcracean/public_html/silversalt/includes/modules/payment/square_webPay/square/square/src/ApiHelper.php:113

I did not receive any Square Alert mail about this error.
I use Zen Cart v1.5.7d and php 8.0.25

Has anybody any idea what could cause this error?

i have not seen this error.

it will be a tricky one to figure out as the error is coming from the square SDK.

you could try changing line 108 from includes/modules/payment/square_webPay/square/square/src/ApiHelper.php as below, but it is a pure guess on my part.

//from
public static function serialize($value): string
//to
public static function serialize($value): ?string

and i'm unsure what else that might affect.

best.

carlwhat:

i have not seen this error.

and i'm unsure what else that might affect.

best.

Thank you very much for your fast reply. Some hours after I asked the customer what the error message was, he replied. It was an HTTP Error 500.
I tested the payment module and no problem. Other customers also had no problem. So I told him that it seems the error was on his side. After a while he responded that the error comes from some setting on his smartphone (I have no idea what setting could cause this error).

Sorry for the false alarm. Your module works excellent an better than the old one.

todoonada:

...Your module works excellent an better than the old one.

:thumbsup:

Upgraded my Square module to the WebPay module last week, was working great, taking charges with no issue.

Today I got a debug file with this at the end:
PHP Notice: missing token result: check if card button is disabled on dev console using: document.getElementById('card-button'); else look for javascript error in console. in /usr/www/users/xx/includes/modules/payment/square_webPay.php on line 261.

Customer abandoned their cart at checkout_payment.

I saw some other messages about this, but must have missed the solution. How can I fix this?
Using 1.56c, php 7.3, standard checkout flow, daily cron task for handler update.

many thanks,
Ed