Support » Plugin: Payment Gateway for Adyen and WooCommerce » adyen-php-api-library.ERROR: 000: HTTP Status Response – Unauthorized

  • Resolved kindrat

    (@kindrat)


    Hello!
    I installed your plugin, activated it.
    Added by:
    1. Test Mode ticked
    2. API Key Test
    3. Test Merchant account name
    4. Test Origin Key
    5. HMAC Key
    6. Capturing check mark is checked

    When I open the checkout page, or click on confirm order button, I get an error:
    “We can’t process payment at the moment. Please try again later.”

    In PHP logs:
    [Mon Apr 27 21:29:57 2020] [error] [client 93.76.94.111] [2020-04-27 18:29:57] adyen-php-api-library.ERROR: 000: HTTP Status Response – Unauthorized [] [], referer: https://mysite.com/checkout/

    I think, this is the 401 error code:
    Unauthorized – Authentication required – You need to input valid authentication credentials (username/password) to access the resource.

    I can’t understand why it doesn’t work.
    Help please.

    WooCommerce: 4.0.1
    WordPress: 5.4
    PHP: 7.3.12
    Payment Gateway for Adyen and WooCommerce: 1.0.1

    • This topic was modified 5 months, 3 weeks ago by kindrat.

    The page I need help with: [log in to see the link]

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author WPRuby

    (@wprubyplugins)

    Hello @kindrat

    Can you please test your API key and the Merchant account name against making a test payment? You can use step3 curl command: https://docs.adyen.com/checkout/get-started#step-3-make-a-test-payment.

    If you get an Unauthorized response, there might be a settings issue in the Adyen account. We are currently following up with another user regarding this issue, I’ll keep you updated.

    Yes, I tested my API key and the Merchant account name using cURL command and I have transaction in my Customer Area, under Transactions > Payments.

    Plugin Contributor Waseem Senjer

    (@waseem_senjer)

    Hi @kindrat
    Not sure exactly what is happening. But when you generated the Origin Code, did you add the correct URL of your website?

    If the issue still happens, is it possible to send me admin access to the WordPress dashboard? please open a support ticket at https://wpruby.com/submit-ticket/ if you would like to send me the login details.

    • This reply was modified 5 months, 3 weeks ago by Waseem Senjer.

    The Origin Code is generated with correct URL of my website.

    I opened a ticket at https://wpruby.com/submit-ticket

    Hello @wprubyplugins and @waseem_senjer

    I’m having this same issue described here after installing the plugin and trying to test.

    I tested the api key and merchant account code with the curl command and that worked properly.

    I was wondering if there has been any resolution to this yet?

    Thank you!

    Plugin Contributor Waseem Senjer

    (@waseem_senjer)

    Hi @gevenm

    What worked for @kindrat is the following:
    1. Make sure that the ECOM merchant account is selected when you generate the keys. (at the top-right corner)
    2. Try to generate the keys from a different browser. (this worked for him)

    Please, let me know if that did not solve the issue.

    That did the trick!
    Thank you for the quick support.

    Plugin Contributor Waseem Senjer

    (@waseem_senjer)

    Hello @gevenm

    I’m glad that it worked for you.

    Did you also try from another browser? Or you just needed to switch to the ECOM account?

    Plugin Contributor Waseem Senjer

    (@waseem_senjer)

    Hello @gevenm
    Any updates for me? I would really appreciate it.

    Hey Waseem,

    I generated new keys through a different browser (edge). I believe I originally generated them from our ECOM test account, but I can’t say for sure. The new keys I did pay extra attention to select the ECOM account.

    Plugin Contributor Waseem Senjer

    (@waseem_senjer)

    Hello @gevenm
    Thank you very much for your insights, I really appreciate it.

    Plugin Contributor Waseem Senjer

    (@waseem_senjer)

    For anyone who stumbled upon this issue. It’s finally fixed in the 1.0.2 release. Please, update your plugin if you use an older version.

Viewing 12 replies - 1 through 12 (of 12 total)
  • You must be logged in to reply to this topic.