Square WebPay support thread.

[dbltoe]

Just did a test order on the site with the fatal error. Got the same error BUT, the order processed.

[todoonada]

Have a look at post 131
It isn't strictly the correct way to do it as it doesn't fix the root cause but does solve the problem (if you don't need to keep track of which module was used to take the payment).

Thank you. Works fine.
Quick 'n dirty.

[carlwhat]

Installed the new 1.0.2 on 1.5.7d with OPC.

Getting

[30-Oct-2022 13:30:25 America/New_York] PHP Fatal error: Uncaught TypeError: Argument 1 passed to square_webPay::saveAccessToken() must be an instance of Square\Models\ObtainTokenResponse, instance of Square\Http\ApiResponse given, called in /includes/modules/payment/square_webPay.php on line 779 and defined in /includes/modules/payment/square_webPay.php:678
Stack trace:
#0 /includes/modules/payment/square_webPay.php(779): square_webPay->saveAccessToken(Object(Square\Http\ApiResponse))
#1 /includes/modules/payment/square_webPay.php(622): square_webPay->renewOAuthToken()
#2 /squareWebPay_handler.php(45): square_webPay->token_refresh_check(false)
#3 {main}
thrown in /includes/modules/payment/square_webPay.php on line 678

[30-Oct-2022 13:30:25 America/New_York] Request URI: /squareWebPay_handler.php, IP address: 68.##.##.122
--> PHP Fatal error: Uncaught TypeError: Argument 1 passed to square_webPay::saveAccessToken() must be an instance of Square\Models\ObtainTokenResponse, instance of Square\Http\ApiResponse given, called in /includes/modules/payment/square_webPay.php on line 779 and defined in /includes/modules/payment/square_webPay.php:678
Stack trace:
#0 /includes/modules/payment/square_webPay.php(779): square_webPay->saveAccessToken(Object(Square\Http\ApiResponse))
#1 /includes/modules/payment/square_webPay.php(622): square_webPay->renewOAuthToken()
#2 /squareWebPay_handler.php(45): square_webPay->token_refresh_check(false)
#3 {main}
thrown in /includes/modules/payment/square_webPay.php on line 678.

line 779 of /includes/modules/payment/square_webPay.php needs to be changed.

//from
$this->saveAccessToken($apiResponse);
//to
$this->saveAccessToken($response['results']); 

[carlwhat]

Another site with 1.0.2 and OPC gets a token warning when the customer has an autofill in Chrome for the CC and does not press enter on the CC Zip before clicking on the confirm order button.

Looks like we may have to work out a way for OPC to ensure the CC is fully active before the confirm order is clicked. You agree?

this is one of those comments that i have no idea what you are talking about and looks to be pure conjecture on your part.

so simply i will disagree.

[carlwhat]

i have just submitted version 1.0.3 for review.

i'm of the opinion that the small bug previously documented warranted a new release.

best.

[swguy]

Approved.

[dbltoe]

Here's the scenario:

1. Site uses One Page Checkout and Square WebPay
2. Customer selects product, adds to cart, and selects Guest Checkout
3. If the customer's browser offers them a remembered card for use, they select that card
4. Most systems ask the customer for their CVV to verify and add the card to the form.
5. Often the Zip Code is left to be filled in by the customer.
6. If the customer does not click on enter or tab to the next box but, instead, scrolls down and clicks on Confirm Order, they will get the invalid token notice.
7. What has happened is that the customer has asked the cart to submit the order BEFORE the CC form is completed correctly. Essentially transmitting the transaction without a Zip Code.
8. So, anytime a customer is using Square and clicks on the Confirm Order button without the CC form properly filled out will get the Token error.

Thus the error received is

[30-Oct-2022 12:54:58 America/Los_Angeles] 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 /includes/modules/payment/square_webPay.php on line 261

By not finishing the entry process on the CC form before clicking on the Confirm Order button, the customer is forcing OPC to submit an invalid CC form.

The answer may be totally in OPC's court but at least I can see why the token errors have been so random.

[Brent]

I don't use OPC and got the same warning so you may be able to rule that out.

[27-Oct-2022 14:38:53 Europe/London] 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 /includes/modules/payment/square_webPay.php on line 239

At the time I was not running V1.0.2 though but a test version carlwhat gave me that fixed the issues when the store is hosted in a subfolder. The only modified file was /includes/modules/pages/checkout_payment/jscript_square_webPay.php

[dbltoe]

I don't use OPC and got the same warning so you may be able to rule that out.

I don't think there is an error with OPC. I think the problem is with the customer who enters the last bit off CC info without hitting enter or tabbing out of the CC form and clicking on the confirm order button.

My thought for a fix would work for either one. Make the confirm button disabled until the payment form is fully completed.

Just my WAG

I'll leave it up to Paul, Cindy and Scott et al to work it out. I stand ready to test any possible solutions.

[schoolboy]

In the past (and also these days), I have added written instructions to the payment selection area on the checkout page.
Generally, these are coloured RED and in BOLD text - so the idiots who do online shopping (that's me too), are instructed what to do before hit "Confirm Order".
EG: Above the option for CARD PAYMENTS I have;

Make sure to enter your card details manually! All fields are needed - CARD NUMBER, EXPIRY DATE, CVV