v5.0 update - The API response status code (401) does not indicate success

[MrCaterpillarz]

Hi,

I tried updating checkout.com to v5.0, but I get the following error at the checkout after entering my card details and clicking 'place order':

The API response status code (401) does not indicate success.

I checked the settings and found that there is a new API field called 'Channel ID'.

I entered this with the 'pc_' prefix as instructed, based on the Channel ID given to me by checkout.com.

I even tried creating a new set of keys, but it still didnt work (those new keys subsequently worked fine when rolling back to 4.3, so the keys were fine).

I get no errors in the console and the log just seems to log the attempted quotes/values with no error messages.

Anyone else experience this issue, and is there a new easy API setting that I am overlooking?

For example, is the API callback URL the same in the new version? The setup guide seems to suggest so.

Any help greatly appreciated, thank you.

[JamesFX2]

Did you get anything done with this?

[MrCaterpillarz]

Hi James, I believe your guys fixed the issue on our dev site (staging2.plumplay.co.uk), but we don't know what exactly was changed. We have since updated the plugin from v5.0 to v5.2 on the dev site, yet our live site is still on v4.8. We would like to get some clarification on what was done to fix the issue with the 401 'API response code does not indicate success' error. The last we heard about this was from Igor, who said: "I have sent a support ticket request to the Magento 2 plugin developers to get more insights. My guess is that the authorisation header with your secret key is becoming malformed on production requests, so it doesn't recognise your account credentials (and gives a 401). I don't know exactly what value that is if it is adding an extra string character, adding an additional "Bearer" in front of it or anything like that. Hopefully, the devs will be able to share more context on it. I will keep you posted as soon as I hear back". This was the error we were getting: ***@***.*** Please let me know if you can find out what was done to fix it, as we might need to replicate the changes in conjunction with the upgrade to v5.2 Many thanks, David David Potts +44 (0)7701 03173301522 737 116 ***@***.*** The Cliff, Middle St., Ingham, Lincolnshire, LN1 2YQ, UK plumplay.com Plum Products Ltd is registered in England no. 2285392. Registered address: Plum Products Ltd, The Cliff, Middle Street, Ingham, Lincolnshire, LN1 2YQ. This message is private and confidential. If you have received this in error, please notify us and remove it from your system. Plum may monitor email traffic data and content of email for the purposes of security and staff training. We will use any data you have provided to answer your enquiry and contact you if necessary. Information about how we process your personal data and your rights regarding your personal data can be found in our Privacy Policy From: James Flacks ***@***.***> Sent: Wednesday, July 26, 2023 3:29 PM To: checkout/checkout-magento2-plugin ***@***.***> Cc: David Potts ***@***.***>; Author ***@***.***> Subject: Re: [checkout/checkout-magento2-plugin] v5.0 update - The API response status code (401) does not indicate success (Issue #520) Caution This email is from outside Plum. Be careful of attachments and links. Report suspicious emails to ***@***.******@***.***> Did you get anything done with this? - Reply to this email directly, view it on GitHub<#520 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7YKVSCQ4RKTK5KR6Y5XECDXSESSZANCNFSM6AAAAAAX536DV4>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>

[athulya-wac]

Any updates in this? faced this issue when production testing with magento 2.4.7