MWS Key error

Hey @wp_shibly

Hope you are doing well!

Which version of plugin are you using?

try to check: https://www.notion.so/saucal/Setting-up-Amazon-Pay-plugin-V2-433010b19b6b48dba43947caa4113d18

Let us know.
Best,
Christian

Thank you for your response. I already folowed that link and setup accordingly. But it gives me MWS keys error everytime. I’m using 1.12.2 this version.

When I hit save change button it always gives me the following error.

https://paste.pics/18edd2c3368dc8ef566bb826b77c849f

Thanks.

Hey @wp_shibly,

Then try to check this link for V1: https://www.notion.so/saucal/Setting-up-Amazon-Pay-plugin-V1-bc489eaeeadd425c9d4453c764d83cbe

The message is because your keys are corrupted or wrong.

After solving that issue, I recommend you to update the plugin to V2.

Best,
Christian

Thank you very much. Let me try that later tomorrow and I will come back to you.
Best,

I followed the link https://www.notion.so/saucal/Setting-up-Amazon-Pay-plugin-V1-bc489eaeeadd425c9d4453c764d83cbe to integrate v1 pay. But the plugin still shows the same error. It says “Error: MWS keys you provided are not valid. Please double-check that you entered them correctly and try again.”

Is there a way to debug why this is happening?

A lot of people are having issues with v2 pay which I can see in the recent support ticket. Please help me figure v1 pay for now.

Thanks

Hey @wp_shibly,

please contact us at WooCommerce.com > My Account > Support. You may need to create an account before you can access that page.
Please include a link to this forum thread, so that we can keep track of what’s already been done.
We will be able to help you further there.

Best,
Christian

Thank you for your response, Christian. Will do it and continue from there. Please keep this thread open until it resolves.

Thanks.

Hi @wp_shibly

Thank you for your response, Christian. Will do it and continue from there. Please keep this thread open until it resolves.

I see that you already opened a ticket with us, and we have responded to your ticket there.

So I’m going to mark this as resolved – as the discussion will continue from the ticket