Hi there!
Updated to 2.0.1 and my customers complained they couldnt enter card details into the payment fields.
Rolled back to 1.0.38 (which did work perfectly) and now customers are presented with ‘error processing payment’ message
When rolling back, it is best to disconnect/reconnect with Square to refresh the token, as the token changed from ver. 1 to ver. 2, then back to ver. 1.
To do this, go to WooCommerce > Settings > Square and Disconnect from Square then Connect using the steps found here.
After reconnecting, run a test payment and see if that works. If it still does not please submit a ticket to us directly at https://woocommerce.com/my-account/create-a-ticket/
Tried this, but the ‘square’ tab no longer exists? see snips
Hi there,
Square settings are under the Integration tab.
Hope this helps!
Hi all,
I have the same problem – since reverting to 1.0.38 (including disconnecting and reconnecting to Square, twice!) we can’t process payments. They all fail (see below). I’ve checked the settings under the ‘integration’ tab for 1.0.38 and they seem good. The latest transaction shown in our Square dashboard is from last Friday before all this kicked off, there is no mention of any (all failed) over the weekend. All orders that tried to use Square have a status of ‘failed’ in WooCommerce. I have disabled Square payments (and am now directing people to Paypal) to get around this. I now also have to manually sort and tidy up a whole pile of failed orders 🙁
Help required!
Example error in ‘order note’ in a failed order:
Array
(
[0] => stdClass Object
(
[category] => AUTHENTICATION_ERROR
[code] => UNAUTHORIZED
[detail] => This request could not be authorized.
)
)
Order status changed from Pending payment to Failed.
-end-
Hey @rsnsbartlett,
Sorry to hear about the error, did you disconnect and reconnect Square after downgrading? The Oauth access token is stored in different WordPress options between the two versions so disconnecting and reconnecting should get your access restored.
Hi @rsnsbartlett,
We have not heard from you in a bit so we are closing this thread. If the issue is still persisting please open a new thread and let us know.
Have a great day!
Hi there, yes – this was all resolved for us on another ticket. Thanks.
SB