• Resolved nils2woo4you

    (@nils2woo4you)


    Dear Community,
    dear developers,

    There are already 2-3 posts on this topic here, but unfortunately none of them provide any useful advice.

    WooCommerce / WordPress is up to date, all configurations have been made according to the instructions and have been checked several times. We use the Uncode theme. In sandbox mode I can pay with Amazon, if I deactivate the sandbox mode the Amazon popup opens with the error “InvalidButtonAccessRequest”.

    The error occurred for the first time after updating to plugin version 2.0.2 / Amazon V2. Therefore, I downgraded to version 1.13.1 and tried to enable payments with Amazon Pay again. Unfortunately, the error now also occurs with Plugin Version 1.13.1.

    What could be the reason for this? What other settings can I check?
    Another observation is that I cannot save the JavaScript origins field on Amazon. Amazon is currently checking this issue.

    Many greetings and many thanks in advance

    Nils

Viewing 15 replies - 1 through 15 (of 18 total)
  • Tobo

    (@infonetzlichtcom)

    I have exactly the same problem. Im using Litespeed but it doesn’t matter if I switch Object cache or optimization off. Cart/ Checkout excluded from cache…

    Tobo

    (@infonetzlichtcom)

    I set up a staging site. Downgraded to v1.x reconnected the staging site but the error is still the same.

    Sandbox Mode is showing login fields but production keeps showing this error.

    We have the same Problem. Connecting was successfull but when you click on the Amazon button the Error “Error Code: InvalidButtonAccessRequest” appeared.

    WooCommerce Logs are Empty and WordPress has no Error in the log file.
    Do you guys have any advice to fix this Problem?

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

    (@infonetzlichtcom)

    Nothing new at the moment.

    Same Problem.

    SessionID is empty
    Error ist InvalidButtonAccessRequest

    I connected with amazon pay with the integrated connector.

    I contacted the Amazon Pay Support.
    They say i should contact you here.

    I made the conflict test but no Issues there.

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

    Same Problem here, already prevails for about a month. Seems to be all German related sites experience these issue, correct?

    BR

    Tobo

    (@infonetzlichtcom)

    Yes. hope it will be fixed soon.

    its here the same prob now:

    When contacting Amazon Pay customer service, provide the following information:
    Session ID:
    Error Code: InvalidButtonAccessRequest

    But I’ve found these line in debug.log:

    [10-Jun-2021 12:09:41 UTC] xxx – WC_Amazon_Payments_Advanced_Merchant_Onboarding_Handler::check_onboarding_request – Received Onboarding Key Exchage request.
    [10-Jun-2021 12:12:51 UTC] yyy – WC_Amazon_Payments_Advanced_IPN_Handler::schedule_hook – Scheduling check for CHARGE xyxyxyxyxyxyx

    Plugin Support Christian

    (@christian1983)

    Hey @infonetzlichtcom @traudel @comzilla @devlabor @nils2woo4you

    Hope you are doing well!

    Can you check the following links:

    Setup your seller account: https://www.notion.so/saucal/Seller-account-verification-edb544c226fd48b6afbdae460604c5cd

    And just to be sure: https://www.notion.so/saucal/Setting-up-Amazon-Pay-plugin-V2-433010b19b6b48dba43947caa4113d18 (V2 keys)

    Let me know.

    Best,
    Christian

    Tobo

    (@infonetzlichtcom)

    It isn’t possible to set javascript origins in seller central. You fill in and click save. Nothing in that section after.

    I set it up several times excatly like it is described. It isn’t working.

    Plugin Support Christian

    (@christian1983)

    Hey there ,

    try to check the following link conflict test on a Staging site, could be some plugin or even the Theme you are using. We need to isolate the problem first.

    If you can’t find the issue, 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

    ok, I don’t know why, but in Sellercentral the JS URL were deleted. After add them again it works now.
    A really strange behaviour

    Tobo

    (@infonetzlichtcom)

    If I add a JS URL. The URL won’t show up…

    Tobo

    (@infonetzlichtcom)

    All is working again here :)! Think it was Amazons fault…

    Thread Starter nils2woo4you

    (@nils2woo4you)

    Hey all,

    thanks for your messages and support, especially to Tobias.
    I can confirm that it works again. The JS Origin field could only be saved on my second attempt. But now everything is working again.

    I was very persistent with Amazon Support and I’m supposed to get some feedback. If there’s anything else to report, I’ll share it with you!

    Many greetings and many thanks!

    Nils

Viewing 15 replies - 1 through 15 (of 18 total)
  • The topic ‘Pay with Amazon => InvalidButtonAccessRequest’ is closed to new replies.