All Legacy API credential questions here please.
To request API Signature or Certificate credentials for your PayPal account:
3. Click My selling tools
4. In the API access section, click Update.
5. Under NVP/SOAP API integration, click Manage API credentials.
- If you have already generated an API Signature, then View API Signature appears. Click that option to view or remove your existing API Signature.
- If you have already generated an API Certificate, then View API Certificate appears. Click that option to view or remove your existing API Certificate.
- Select one of the following options, then click Agree and Submit.
- Request API Signature – Select for API Signature authentication.
- Request API Certificate – Select for API Certificate authentication.
- PayPal generates your API credentials as follows:
- API Signature credentials include an API Username, API Password, and Signature, which does not expire. These values are hidden by default for added security. Click Show/Hide to toggle them on and off. When finished, click Done.
- API Certificate credentials include an API Username, API Password, and Certificate, which expires automatically after three years. Click Download Certificate to save the API Certificate to your desktop.
@DevRel_Monti Thanks in advance for any help you can provide. I have opened a paypal-support ticket for this urgent issue a couple days ago, but am still awaiting the first response.
We've successfully been running a WordPress plugin using PayPal's Classic API integration and a custom listener URL for years. (It is a retired plugin that is no longer supported, but still functions to automate management of 100+ existing PayPal subscriptions.)
After recently migrating the site to a new server, all IPNs related to the plugin started failing. No configuration changes have been made to the plugin or Paypal account. Our server manager insists WHM/Apache config is identical. I have also ruled out any issue with mod_sec rules causing the problem. It appears the only difference is the server IP address.
Would I need to create and assign new Paypal NVP/SOAP (Classic) API credentials after moving the website to a new server if the domain and plugin configuration remains the same?
Can I simply/safely "Remove" our existing Classic API integration and create new credentials?
Any other suggestions are greatly appreciated.
Thanks! @DevRel_Monti :
IPN Failure After Server Migration [ Case # 11506430]
I have received a response answering my question about whether or not new credentials are required. (They are not.)
I have not, however, yet received any resolution as to why our IPNs would suddenly start failing after migrating the website to a new server when no changes were made to the website/plugin configuration now the PayPal account. The IPN simulator only reports "review your information" with no details about why the message fails. (They did not fail prior to our server move, and our data center insists the problem is with PayPal.)
Listener URL Now Fails:
Here's a question... I managed to find where to set up LIVE NVP/SOAP credentials. ( whihc work perfectly with our site in Sandbox))
But set to Live, now I get the error This transaction cannot be processed. The merchant's account is not able to process transactions.
Hmmm.. what am I missing?
Haven't Found your Answer?
It happens. Hit the "Login to Ask the community" button to create a question for the PayPal community.
- Unable to retrieve any (API Credentials > REST API apps > Secret) app secrets in REST APIs
- Cannot open/edit Apps & Credentials in Sandbox Environment
- API Credentials page is empty in NVP/SOAP APIs
- Platform Partner Fees - Sandbox in Sandbox Environment
- Authentication failed due to invalid authentication credentials or a missing Authorization header in PayPal Payments Standard