I have had an app developed in it processed orders in 'sandbox' mode. No I've tried a live payment it just keeps spinning on the app.
I went to the rest api on the PayPal Developer site, but when I click from 'sandbox to live' and click save it reverts back to sandbox.
The developer of the app is not being very helpful and PayPal is difficult to get help from.... so I have found this place ;-)
Hopefully somebody can help.
Thanks
Please try again in different web browsers by clearing cookies and cache. If you are still persisting the same issue, kindly file an MTS ticket for PayPal at: https://www.paypal-techsupport.com/ , with screenshots and steps for reproducing ths issue. Then you will get help from the PayPal MTS team.
Related
My customer had bought an Opencart website and an eCommerce Flutter app (from inspireUI/Fluxstore).
And my job is to implement the payment part into the app, (the app now loads the payment page from the website into a WebView and sync all the data the user had entered).
The user has to complete the web form, adding his credit card and complete the payment process.
Anyone have some documentations or any previous experience to help?
I've searched and contacted inspireUI support team and did not find helpful information.
There is not any documentation like this. You need to track all code and catch what happens.
By the way, you have to be careful while using WebView. There are some annoying issues related to payment like fraud detection and related to AppStore processes. You can read more.
I have issue with paypal when request api access.
I have click on selling tools -> API access -> update. Then it redirect to the page https://www.paypal.com/businessmanage/credentials/apiAccess.
After the page fully loaded. It don't display the text below the Learn more link. So I can't process more.
I have changed to different computers, phones, internet connections, browsers but it not solved the problem. I have created another account but it still meet that issue and I don't know why some my friends have used Paypal but don't have this issue. And they still can't solve my situation.
So please help me!
Paypal access API page not display fully
See above screenshot there was issues with facebook payment.
I'm currently having the same issue with sandbox payment on multiple environment, live payments are working.
I've tested the server webhook via the web payment dashboard and it works.
The current calls are on API 2.4 and also tested with 2.7 still get the same error.
The error started appearing on different account not all at the same time.
I'm continuing my search but hope these information can help to find and solve the issue.
I'm trying to integrate Paypal's ExpressCheckout API into my website.
I'm incurring into very frustrating problems with the system and with the support assistance, too.
Every time we have a problem the support assistance invites us to change the implementation technology, from SOAP, to SDK, to NVP, etc..
After 3 days of working (from coding with SOAP (PHP) up to the attempt to start the SDK's examples) no solution has yet been found.
I'd like to know if someone has ever had similar problems.
Thank you in advance.
I completely understand and share your frustrations.
The current issue I am having is after a call to SetExpressCheckout() using the .NET SDK I redirect to the PayPal sandbox URL with the appropriate command and token specified on the querystring and when the browser gets to the PayPal site it says "Please log in to use the PayPal sandbox features" which is linked to the developer.paypal.com site.
If I log in first on another tab and then redirect to PayPal it still doesn't work, aarrggh!
Stefano - What type of issue are you currently having?
Peter - What particular browser are you using? There have been a few issues in the past with IE. If you are using IE, you might try using Chrome or Firefox to see if you get different results. I just tested all 3 and they were working for me. You also might try clearing all cookies and cache prior to opening up a browser and navigating to developer.paypal.com. Once you have cleared cookies and cache, open up the browser and go to developer.paypal.com and log in. Then once logged in, on a second tab pull up your website and try testing.
Clearing the cache and cookies prior going to developer.paypal.com has worked for some merchants in the past that were having these same issues.
With the recent revamp of the PayPal developer site, I have encountered many problems trying to test my site with PayPal integration.
Issue 1:
I am not able to check out from out site which it should bring me to sandbox.paypal.com, it return me the common error of "Please login to use the PayPal sandbox feature". I have confirmed that I am logged in to the developer site at developer.paypal.com.
Issue 2:
Under Applications > Sandbox accounts, in one of the account, I am redirected to the live site at www.paypal.com by clicking on "Sandbox site". It should bring me to sandbox.paypal.com so I can login to the sandbox account. Currently this is not possible.
Issue 3:
I realised that I am logged out from developer.paypal.com when I go to www.paypal.com. Some kind of cookie issue?
Above all issues, I have tried troubleshooting by using a different browser, clearing cookies and cache.
Some of these issues are currently being worked on. Some have been able to have been resolved by clearing the cache and cookies on your browser. This must be done prior to opening up the developer.paypal.com site and most developers have better luck with this when using Firefox or Chrome. There appear to be more issues with IE, than the other browsers.
If doing this does not resolve your issue, you will want to open up a ticket with PayPal Merchant Technical Services. This way your issues can be tracked, and it will allow PayPal to gauge the number of merchants being effected by the different issues. Also, this will allow you to be notified once the issue is resolved.
As a workaround, you could also try using the API credentials that are within the sample code/SDK's for testing purposes. This will allow you to test the API calls, though you just will not be able to log into the Merchant account and make changes to it. This may or may not work for you depending on your needs.
Trying different browsers worked for me. I experienced the same problem for several hours today when using Firefox, Chrome, and Safari on Mac OSX 10.8. I tested using Firefox 19.0 on a PC and things worked fine with the PayPal sandbox site.
I had the same issues as the original poster. I was using IE9 with ExpressCheckout API.
I was calling the SetExpressCheckout and redirecting to PayPal sandbox. On the Sandbox login page, after typing login details of my test personal account I received a message that the email account was not valid and a link (which didn't work) to return to Sandbox site.
I switched to Firefox (which was also probably clean of cookies for the PayPal Sandbox as I don't recall ever testing PayPal using Firefox) and everything worked fine.
I called the SetExpressCheckout, redirected to PayPal sandbox and I could login with my test personal account and checkout and return correctly to my payment landing page to call DoExpressCheckoutPayment.
FYI in case anyone else is dealing with this problem. I am using the PayPal IPN feature, which in the Sandbox environment stopped working when I was doing some recent testing after migrating to the 'new' sandbox environment. I imported my old sandbox test accounts after logging into the developer site with my real paypal info, but still nothing worked. After messing around forever, I discovered that basically you have to setup again as if it was a new account even though you imported your old settings. I had to specify my IPN url again and also re-verify the old imported sandbox accounts via an email link that you receive under you paypal developer sandbox notifications. Then while logged in the developer site, you can log into the sandbox environment with your test accounts and everything works.
For testing purposes the most simple solution:
Click your browsers back button and perform the step again.
Sounds stupid, but it works.