We have a website set up for payments thru Square. All of a sudden it is not accepting payments and says the following:
Square Payment Failed (Status code UNAUTHORIZED: The ‘Authorization’ http header of your request was incorrect or expired. The header value is expected to be of the format “Bearer TOKEN” (without quotation marks), where TEN is a valid access token (e.g. “Bearer
ABC123def456GHI789jk10”). For more information, see Square Connect API Documentation
I spoke to Go Daddy who built our website and is maintaining it. They had one of their engineers check it on their end and they cannot see anything wrong. So I’m back to you guys. Can you help me get this fixed (I am not a tech person) so I will need your help. We are not able to accept payments on our website so that isn’t good for business. I’ve sent a request for someone to help in a separate email but I’m adding this request in too.
Typically the only reason UNAUTHORIZED errors occur are due to invalid access tokens. As far as I know, GoDaddy uses OAuth, which means they generate the access tokens on your behalf, so they’re passing an invalid access token to Square. It’s possible the token has expired, in which case they should renew the token (which, again, can only be done by GoDaddy unfortunately), or if you remove and re-add the integration, it probably will auto-renew (they shouldn’t make you do this, though). Since they use OAuth, there’s nothing Square can do to resolve the issue, as the request comes directly from GoDaddy, and we do not have access to their code to change.
This also happened to us, we are using Wordpress and Woocommerce. I was hoping to find answer too. We are using AWS, This is the payment log:
Square Payment Failed (Status code UNAUTHORIZED: The Authorization http header of your request was incorrect or expired. The header value is expected to be of the format “Bearer TOKEN” (without quotation marks), where TOKEN is a valid access token (e.g. “Bearer A*****************”). For more information, see https://developer.squareup.com/docs/build-basics/using-rest-api#set-the-headers .)*
WooCommerce uses OAuth and they are the ones that pass the token in the request. Have you reached out to them with this issue yet? 