You do not have permissions to make this API call

[m11rf]

The website has been working fine and then i got this problem when you click to pay with paypal.

I recently update the paypal certificate

(https://github.com/gburton/CE-Phoenix/blob/master/ext/modules/payment/paypal/paypal.com.crt)

but after that the website has been working fine for weeks.

In the admin panel on the website itself i have nothing in the API Username API Password and API Signature fields, but i never have had anything in there.

I tried adding the username and password from the API settings in paypal but it's still the same error. 

Any help very much appreciated

[m11rf]

Does Oscommerce have a third party permission username that i can add and allow in paypal? If so, what is it?

 

 

[mhsuffolk]

Have you tried clicking this?  As you can see I have five fields populated.

[m11rf]

Thanks for your help. Thanks for showing me an example of yours, that really helped 

It's now sorted. I'm not sure why all of a sudden i needed to enter the API details when the shop has been up and running for 6 years without it.

But i put in all the information and it's working fine now.

If anyone else is searching for this, you are given a choice on paypal when you request API details

1. Click Request API Credentials.
2. Click Request API signature.   

You need to choose 2. I chose number 1 and was going round in circles for a while trying to input the wrong information. So i deleted number 1 and requested number 2 and got the right info.

 

Edited September 26, 2020 by m11rf

[blacksmoke55]

Mine is not a PayPal business account but I am getting this same error. I'v never had anything in the API fields.

I have tried resetting everything and nothing seems to work. Any help would be greatly appreciated!

Cheers,

Aaron

[m11rf]

I think the only way forward is to upgrade to a business account... I was reluctant. But needs must.

[blacksmoke55]

Just to close out my comments here, I did finally upgrade to a PayPal Business Account 

and the API & Security Header Errors are now gone.

Thanks for the help here, you folks are awesome!

Aaron