I used to use the old PayPal sandbox to simulate a payment using IPN (posting a payment, and then confirming the IPN). This used to work fine with the classic sandbox.
With the introduction of the new Sandbox - I try to submit the request as I used to (redirecting the user to https://www.sandbox.paypal.com/cgi-bin/webscr?) which should take the user to the payment page - but this link now takes the user to the logon page for the sandbox.
Is this no longer supported?
I see there is still an IPN simulator, but I want to test the end-to-end round trip process from the user-perspective. This does not seem possible anymore.
Try clearing your cache and cookies prior to opening up the developer.paypal.com site and logging in. Also try using Firefox or Chrome if you are using Internet Explorer.
Related
we have a web app written in Node where we have a payment page that uses the PayPal REST API.
We have been testing the payment page using sandbox for a few weeks now without any errors and we went through the whole approval process to enable direct credit card payments on our account, but when we change the credentials and URL on our app to the ones from live, we get a Client Authentication error.
We have gone over this issue with integration experts over the phone (for hours) and opened a ticket with PayPal support and no one has been able to help us.
This is our debug ID:
Debug ID for sandbox: 7b06479ae1ef3 (successful payment)
Debug ID for live: 8843fb4d4cbcf (failed payment)
Exact same code, only thing that changes are our credentials and URL.
The few people we have talked to in PayPal point to it as a credentials issue, but we have created a new app in our dashboard and gotten new credentials only to get the same error.
What could be going on?
Is switching from sandbox to live not as simple as just switching the URL and Client/Secret?
PayPal:
Cant access paypal sandbox - if trying to appraoch directly, you are being redirected to the paypal main site.
If trying to reach the sandbox via the paypal developer site,
browsed to Dashboard>Sandbox>accounts,
(find the facilitator and buyer accounts - which apperently do require decent passwords to work) than press "Click Me" just to fail again by being redirected to a page indicating:
"We're sorry.
Relying party validation error: client_id or redirect_url provided in the request does not match any of the registered clients. Please check the request and try again."
OK, found a way aroudn this.
Problem: For some reason if you are a PayPal user and also wish to use the sandbox (in my case I have a seperate private account and a business account, and the sandbox is used by the busienss account), any attempt to approach the sandbox results in being redirected to paypal main site (at least in my region).
Solution: Use a seperate cognito or private window for the sandbox - never login to you your own account while working with the sandbox, and if you do, restart the browser and get a new private window.
I was successfully checking out orders before on Paypal's Sandbox. Today, the login form and the button to complete the payment suddenly fail to display. Anybody encountered this?
Looks like one of the many random browser cookie issues that PayPal's servers tend to have. I'd suggest logging out of any sandbox or live PayPal accounts you might be in, then completely close your browser out, open it up and try again.
Our iPad app has been processing payments successfully in sandbox mode using v1.0.5 of the iOS SDK. However, we found one defect while testing our application. Please find steps below.
Login into PayPal.
Use email or phone and type in your credentials.
click on send payment. You will see the payment complete screen. Click on done button.
Now open your sandbox account and change the password/pin (Profile->Update password).
Then go to the application and try to make payment again. PayPal sdk navigate you directly to the confirmation page.
Click on send Payment.
PayPal SDK allow user to pay with old credentials(password/pin).
Is this a known issue or I am missing anything?
Also is there any way to log out user after every payment. (Force user to login every time he tries to make the payment without manually clicking logout button).
moka, I think that the scenario you describe is okay as is.
Within your app, the user logs in to her PayPal account, pays you, and chooses to not log out from PayPal.
Later, within your app she remains logged in to her PayPal account, even though elsewhere she has changed her password. And therefore she can still pay you from this account.
That all seems fine to me.
Regarding your second question:
When you call [PayPalPaymentViewController initWithClientId:receiverEmail:payerId:payment:delegate:], the SDK uses the payerId to determine whether this is a new user or a returning user.
So if you change the payerId each time you call the SDK, then each time this will be interpreted as a new user, who will therefore require a fresh PayPal login. (For example, you could set payerId to something like [NSString stringWithFormat:#"%d",rand()].)
-- Dave Goldman (eBay/PayPal/card.io)
Set rememberUser property to NO for PayPalConfiguration instance like this
payPalConfiguration=[[PayPalConfiguration alloc] init];
payPalConfiguration.rememberUser=NO;
It will then ask each time to login.
I can log into the developer.paypal.com site with my PayPal credentials. When I then enter the sandbox as my seller account, all of the links in the menu system takes me to the live PayPal site, instead of the sandbox. I have been able to hack the url and prepend "sandbox." and in some cases that gets me into the IPN history and Recurring Payment Profiles. I can live with that work around if I need to.
My main issue right now is that I can't access any transaction history for my seller account. It goes to the transaction history on the live PayPal site, and shows me the transaction history for the PayPal account that I initially used to log into the developer site.
This is really holding up my project.
Any one have any insights?
I've tried things like deleting cookies, but nothing has worked so far.
It is (unfortunately) common for the sandbox to be broken in the ways you describe. However, this should not be holding up your project -- the sandbox is mainly useful for checkout/API testing, and there is very little need to review transaction history in the web interface.
I too have the same very annoying problem. I need to list the transactions because sometimes I want to delete them (they are recurring payments) so I am in control of which IPNs actually go to my test website.
After playing around with the sandbox, I have found that at first, the "history" link will send you directly to the live paypal site but if you first select "Withdraw", then the nav menu will display the correct "history" link (i.e. https://www.sandbox.paypal.com/fr/cgi-bin/webscr?cmd=%5fhistory&nav=0%2e3)
The screen will give you access to the 20 latest transactions; I haven't found yet how one moves to the next page without being sent to the live Paypal site.
If I delete the seller test account, will it cancel all the existing future recurring payments?
Cheers.