All Legacy API credential questions here please.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@not_here 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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks! @not_here :
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:
https://tripawds.com/wp-admin/admin-ajax.php?action=psts_pypl_ipn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello RuffCue,
I had the same issue when switching to production by changing the endpoint to the production endpoint and also the express checkout link.
But it is not working anymore. I do not know if I have to create another NVP/SOAP credential for live.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a set of NVP API credentials on the live site that were created 2012, apparently.
I've tried to use these using Postman in a SetExpressCheckout call, but get the error message "Merchant not enabled for reference transactions". Why am I getting this error?
I understood by having these credentials (do they expire?) reference transactions should be enabled.
- « Previous page
-
- 1
- 2
- Next page »
Haven't Found your Answer?
It happens. Hit the "Login to Ask the community" button to create a question for the PayPal community.
- Things don’t appear to be working at the moment in PayPal Payments Standard
- Cannot create developer account from invitation link in Braintree Client-side Integration (JS, iOS, Android SDKs)
- QR Code Issue in Braintree Client-side Integration (JS, iOS, Android SDKs)
- How to enable on-demand / recurring payments to existing PayPal checkout? in SDKs
- How can I revoke SamCart's access my recurring payments? in NVP/SOAP APIs