I was working with paypal sandbox account. It was working fine. But, now it shows the following error.
The cookies are enabled. I tried using different browser and a different computer. Still I'm getting the same error. I tried clearing the cookies and cache. But it didn't work. Any solution?
Please turn on cookies to check out
This is a Paypal's issue which affects Express Checkout on the PayPal Sandbox. Paypal announced that there is no alternative workaround at the moment.
Reference: https://www.paypal-notify.com/eventnotification/event_details?eventId=6109
This works for me: Paypal Sandbox Frustration
To simplify:
Login first your developer's account here: http://developer.paypal.com
Open another tab and login your developer's merchant account here: https://paypalmanager.sandbox.paypal.com/apiAccess.do?subaction=api
Open another tab again and do your express checkout process.
To add an experience : In the beginning I had serious SSL issues when connecting to sandbox for a SetExpressCheckout:
The type of error was javax.net.ssl.SSLHandshakeException Error
To bypass this error (never happened before), i added the api-3t.sandbox.paypal.com certificate to my java truststore.
After that, the setCheckout responded correctly with a valid token, but I run into the 'cookie are turned off' problem, for almost 8 hours now. None of my websites is working with the sandbox environment.
I think nothing can be done until PayPal make things clearer with some announcement.
Related
I am getting the following error in the transactions section of the dashboard (since days, I am not able to test anything):
We’re sorry, something went wrong while fetching sandbox transactions. Please try again.
Does anyone know how to fix this?
I talked to the PayPal support and it seems to be a global issue at the moment which should be fixed until tomorrow. There is another solution to create a sandbox account right now (see Unable to use sandbox accounts), but then I am not able to verify those accounts because the notification email with the confirmation link is completely broken. So unfortunately it seems we all just have to wait for it to work again.
I am seeing the same issue this morning. I am getting UNKNOWN_ERROR when trying to process via the Sandbox from .NET using SDK as well. Even the .NET Sample SDK is returning a UNKNOWN_ERROR. I sure hope they get this fixed soon.
I have the same issue on the transactions dashboard. Additionally Mass Payout's are not processed, but regular Payment's are working.
Sandbox mode, using Node.js REST API
I dont have access anymore to the sandbox.paypal.com
In Developer Account I tried:
Want to link existing Sandbox Account with your developer account? *Click here* and provide credentials of your sandbox account.
After few redirections it refuses to sign me in:
Error
Relying Party Validation error: client_ID or redirect_uri provided in the request does not match any of the registered clients. Please check the request.
I've tried with two differents accounts, one of them do not have a live account, and it give me each time the same error without further explanation.
#paypaldev filed a ticket on the issue but I'm not sure what to expect.
Do am I the only one ?
An update here for everyone else as I followed up with François via Twitter. The internal teams were able to track down the issue that was causing the relaying party validation error, and it should now be fixed without needing a workaround. If anyone is still seeing an error, please let me know and I'll circle back with the teams working on the fix.
In the new PayPal Sandbox, we want to test the IPN, with a payment_status of denied.
The old PayPal sandbox used to allow us to view the transaction history and Accept/Deny a transaction.
Seems the new Sandbox account hierarchy seems to be confused. When clicking History it redirects back to the REAL paypal.com site, not sandbox.paypal.com, and hence shows the wrong history.
Steps to reproduce:
log via developer.paypal.com
go to "Enter sandbox site" under Applications, now logged into https://paypalmanager.sandbox.paypal.com with the correct account showing, great
Click history, redirected to https://history.paypal.com/us/cgi-bin/webscr?cmd=_history, which shows the REAL history. Grrr.
Any ideas? Happy for a hack, just want to fire a deny request for a sandbox transaction so we can test.
It's a known issue - sorry. Trying to change the URL to the Sandbox one still redirects you to the Live site and, occasionally for whatever reason, a security certificate page. A fix is coming soon.
If you want to be updated on the issue as it goes on you create a ticket at PayPal.com/mts, let me know what the ticket number is, and I can grab it.
Edit:
This should be resolved now. I cleared my cache and cookies, closed the browser, and tried it out. I was able to view the transaction history in the Sandbox.
we're having the same issue on our end. What works for us is firing up an incognito window in Google Chrome and login via there. It's a hack, but it works.
I have old Sandbox business & personal accounts that stopped working. I have to go back and test a site I developed two years ago. I saw a reference to importing these accounts on the new site but every link seems to go in circles. I certainly can't afford time to rewrite all my client's api's even if they would pay me just to go into testing mode.
Can someone suggest how I might revive these accounts.
There are currently some issues that are being addressed to resolve this issue. As a workaround try using FireFox or Chrome if you were using IE. Clear your cookies and chache prior to opening up that browhwer. Then go to developer.paypal.com and log in with your live PayPal account email address. Then try importing your accounts. There have been more issues with IE than the other browsers.
This question already has answers here:
Please login to use the PayPal sandbox feature
(5 answers)
Closed 9 years ago.
DISCLAIMER: This question is specifically for the Paypal forum.
I have two Sandbox test accounts. parijat_kalia#hotmail.com (PERSONAL) and parijat_kalia-facilitator#hotmail.com (BUSINESS). The second one has the API credentials and I am using the NVP API to test our e-commerce subscription plan
. The response I get is :
10501: Invalid Configuration This transaction cannot be processed due to an invalid merchant configuration. Occurs when the billing agreement is disabled or inactive.
Hence, to activate it, I presume I need to log in with this sandbox account into the sandbox website so as to activate the billing agreement. The steps I follow are pretty basic.
Login to developers.paypal.com
Click on Applications tab in the horizontal menu
Click on Sandbox accounts in the vertical menu
Click on the specific accounts 'parijat_kalia-facilitator#hotmail.com' dropdown arrow button.
Click on Sandbox site
When i click on sandbox site, it loads in the PERSONAL account in the email i.e 'parijat_kalia#hotmail.com'. I obviously change this and try to login with the business account credentials. However it does not log me in whatsoever. I have changed the password, literally copy pasted it, but it does not work. Nor does deleting the cookies/clearing the cache and terminating the history help. Also, I am using Chrome, not IE.
Also, I presume this error is with Paypal's sandbox website, since the API call is technically logging me in with the credentials (I infer this since I am getting error 10501).
Can you please tell me what is going wrong?
I had an issue similar to that the other day. I was trying to switch from one developer account to another, but it kept logging me in as the first one. So, I couldn't use any of the sandbox accounts for the 2nd account.
I circumvented this issue by switching to private browsing mode in chrome (ctrl+shift+N) and logging in that way.
I can't guarantee this will fix your issue because it's not the same as mine, but it might help.
Misplacedme's answer worked for me, but I don't have enough rep yet, so I'll reply and add some info.
Chrome: Use an Incognito Window (ctrl+shift+N)
Opera: Use a New Private Window (ctrl+shift+N)
IE: No need for special window. It works as it used to.
Firefox: No need for special window. It works as it used to.
Safari: No need for special window. It works as it used to.
Note: These are all on a Windows 8 PC (sorry, I know most people in their right mind aren't using win8 much less developers)