Authentication with PayPal failed: Could not create token.

Hello @outlet2013

thank you for reaching out to us, we are here to help.

This error usually occurs when there is an issue with the account details. This is why I advise you to disconnect and reconnect the account to the plugin. This shoudl renew all details of your account, renew the API key and correct any issue that might be there.

Please let me know if this resolves the issue.

Kind regards,
Joost

Already Rennoved! 10 Times always same error!

Hello @outlet2013

I just received a response from another merchant that was experiencing the same issue that his issue was resolved after he did conflict testing. It was caused by a plugin erroneously turning off WP transients. I am still pending to hear from him about what plugin was causing this.

You may want to perform a full conflict test to rule out eventual issues with the theme or a different plugin. We recommend temporarily activating the default theme Storefront and disabling all other plugins except for?WooCommerce and?PayPal Payments to see if the behaviour persists.

Here’s a guide that explains the steps in more detail: How to test for conflicts

Please let us know how this works out for you.
I will let you know what plugin was causing this for the other merchant when I hear from him.

Kind regards,
Joost

Just checked all…no conflicts!
But when i open a single product i have this 4 api calls! Thats not normal…i think they arent needed on product page! Infact i disabled all paypal button and advise!

POST	https://api.paypal.com/v1/oauth2/token
?grant_type=client_credentials	429 Too Many Requests	
WooCommerce\P\A\A\PayPalBearer->request()
Plugin: woocommerce-paypal-payments	0,1 kB	30	0,2079
POST	https://api.paypal.com/v1/oauth2/token
?grant_type=client_credentials	429 Too Many Requests	
WooCommerce\P\A\A\PayPalBearer->request()
Plugin: woocommerce-paypal-payments	0,1 kB	30	0,1996
POST	https://api.paypal.com/v1/oauth2/token
?grant_type=client_credentials	429 Too Many Requests	
WooCommerce\P\A\A\PayPalBearer->request()
Plugin: woocommerce-paypal-payments	0,1 kB	30	0,2045
POST	https://api.paypal.com/v1/oauth2/token
?grant_type=client_credentials	429 Too Many Requests	
WooCommerce\P\A\A\PayPalBearer->request()
Plugin: woocommerce-paypal-payments	0,1 kB	30	0,1991

Hello @outlet2013

sorry I didn’t advise this earlier, but if PayPal standard is working perfectly, please activate that until we have this resolved! We don’t want you to be financially effected by this situation.

Then when the live site working properly, it would be smart to create a staging site and test this with a sandbox account, to see if you get the same outcome. You can generate sandbox account here.

Please let me know if the issue also occurs when you are using a sandbox account.

Kind regards,
Joost

Problem identified! IS Pbject cache of w3tc!
Disabling cache of objects no api call!!!

Solution is to store transients in database when object cache is enabled! In this way worls well!

My site also displays this error:

Authentication with PayPal failed: Could not create token.

Please verify your API Credentials and try again to connect your PayPal business account. Visit the plugin documentation for more information about the setup.

@outlet2013 how to store transients in database? on setting oage or have some plugin?
thank you

Hello @weibin0227

this does not necessarily have to be the same issue (this is why we always advise opening a new thread for similar cases). There are 2 ways you can possibly resolve this:
– There could be an issue with the account details stored in the plugin. To make sure they are correct we advise you to disconnect and reconnect the account details via the connect wizard (blue button “Activate PayPal).
– Another cause for this issue could be that the connection to the PayPal server is somehow blocked and you need to check if any plugin is doing this. You can do this by deactivating all other plugins, except WooCommerce and PayPal Payments and trying again. Outlet2013 would have found the issue as well doing this since his Cache plugin was causing the issue. He adjusted the settings of this plugin to resolve the issue for himself.

I would advise to see if these actions help you resolve the issue or open a new thread if you need additional support. If you want to share system report or logs with us and you would rather not share them on this public forum, you can also engage us via these instructions.

For now, I will resolve this thread, since the issue was resolved in this particular case.

Kind regards,
Joost