API Credentials not transferring?

I can’t get this to work either. I’ve been using AP for ages without problems.

Amazon says it has transferred the credentials, the Woo settings just sits there waiting forever for the results.

By clicking Transfer API Keys, your API Keys will be securely sent to the following URL:
https://www.xxx.com/wc-api/wc_gateway_amazon_payments_advanced_merchant_onboarding/
Your keys have been transferred.
We successfully shared your Amazon Pay keys with .
Close the window to return to your admin panel.

Note that the Merchant ID and Store ID are there, but no public key…and of course it continues to say “Reconnect to Amazon Pay”.

Extremely frustrating. Trying to make sense of the manual instructions doesn’t help (and I have 30 years in IT) there is no place to download the keys on Amazon Seller Central nor Amazon Pay.

• This reply was modified 2 years, 11 months ago by rabh.
• This reply was modified 2 years, 11 months ago by rabh.

Thanks, I did already disable most all of the plugins. I will try changing the theme and then get back to you.

So I disabled all the plugins except for Woocommerce itself and Jetpack. Activated 2021 theme.

Still no joy.

I go through the process and tell it to transfer the credentials, it says it successfully transferred the credentials but Woocommerce Amazon Pay plugin just sits there waiting for the credentials to arrive and the ssl access log just continues to repeat:

“GET /wp-admin/admin-ajax.php?action=amazon_check_credentials&nonce=ef65cf720b HTTP/1.1” 200 26
“GET /wp-admin/admin-ajax.php?action=amazon_check_credentials&nonce=ef65cf720b HTTP/1.1” 200 26
“GET /wp-admin/admin-ajax.php?action=amazon_check_credentials&nonce=ef65cf720b HTTP/1.1” 200 26
“POST /wc-api/wc_gateway_amazon_payments_advanced_merchant_onboarding/ HTTP/1.1” 200 20
“GET /wp-admin/admin-ajax.php?action=amazon_check_credentials&nonce=ef65cf720b HTTP/1.1” 200 26

Hi.

I was having problems emailing you because your server was rejecting my replies.

I think it’s working now (the email).

In any event, I tried to do the manual process to get keys and it did not provide me with a file of keys. I can’t create a new store so all it was doing was changing my current keys (or appeared to be doing that).

I will try some other permissions things on my end to see if I can get it to work.

OK, I got it to work, to transfer the credentials.

Now, when I try to make a purchase (using a different browser and my personal Amazon account) after the latest Amazon Pay update), it logs me into Amazon, retrieves my payment information and address and displays the information in the two little boxes.

So I click on PLACE ORDER and just above the two boxes I get a red excalamation mark and “please enter an address” and there is no way to continue.

So I tried logging into my store account, then tried to pay with Amazon Pay and still get the enter an address error.

So then I went into my store account and entered an address (doesn’t transfer from Amazon Pay ?).

Then I hit PLACE ORDER again and got this error:
Error: The request signature we calculated does not match the signature you provided. Check your AWS Secret Access Key and signing method. Consult the service documentation for details.

So the system created the order with no addresses and set amazon_payment_advanced_version to 1.13.1 despite having retrieved the version 2 credentials from Amazon.

So checking again, at the top it says “Amazon Pay: Additional Setup Required – To ensure full compatibility with this version of WooCommerce, please enable the “Use Login with Amazon App” feature from the settings page. After enabling Login with Amazon click the “CONFIGURE/REGISTER NOW” button to re-run configuration and setup your credentials. Alternatively, perform the setup manually using these” but of course “Login with Amazon app” is a V1 parameter which cannot be changed on the settings page.

Enable Amazon Pay & Login with Amazon is enabled, but the plugin keeps saying reconnect with Amazon Pay, gets a new set of credentials and then still doesn’t work.

Very frustrating.

• This reply was modified 2 years, 11 months ago by rabh.
• This reply was modified 2 years, 11 months ago by rabh.
• This reply was modified 2 years, 11 months ago by rabh.