I am trying for the first time to setup Paypal PDT and want to test it against the sandbox.
When I try to go to http://sandbox.paypal.com, I am getting forwarded to https://www.sandbox.paypal.com/hk/webapps/mpp/home , then I get an error generated by Tomcat (404).
Is that normal? Is this site to be used only though APIs and am I doing something wrong when opening it directly in a browser?
Under the FAQ, I can read that
I'm a non-U.S. developer. How does the site redesign affect me?
The current new REST APIs and PayPal Mobile SDKs are currently
targeted for the US market only. We will be rolling out in all
geographies over the rest of the year.
Is this a reason for that? Is the sandbox a part of the REST API?
I apologize for the inconvenience. We are working to fix this as soon as possible. In the meantime please try using https://www.sandbox.paypal.com/webapps/mpp/home as a workaround to log in.
Just wanted to follow up and to let you know that the 404 issue has been resolved.
Nope, it's broken for me to in the UK. I tried using a US proxy, and it seems that it's broken for everyone, no matter where you are.
Best to just sit it out and wait, although in the meantime I'm going to be using something else. Way to go, PayPal.
Related
OK so im just gonna ask this question, as I am at the end of the rope, with hopes someone out there will have some advice.
I have installed the Woocommerce Follow Up Emails plugin on my site, and for the life of me I cannot get it send the email.
The settings I have are:
Trigger: 3 days after the order total is above $1.00
Setting: Customer recieves the email once
There is nothing in the "scheduled emails" of the plugin showing up, however and this is the part that throws me off, in the Tools>Scheduled Actions of the wordpress dashboard i get multiple entries of the below:
which tells me that it the emails are being scheduled but are not being sent out (even though it says, action complete). I have checked the WPMail log nothing, i have checked Cpanel Email Tracking and theres nothing. I have a WP Cron plugin installed that tells me it is functioning correctly.
Does anybody have any ideas/suggestions that i could do or check that I havent done already? Is there something I'm missing?
Any help will greatly be appreciated.
P.S, I purchased the plugin from a third party site and cant ask Woocommerce for support without paying for subscription (which i will do as my absolute last resort)
The plugin works fine on my side, although it is very basic in its functionalities and you reach super quickly its limitations.
I'd suggest you buy the plugin from WC. They tend to have special offers of 30-50% off few times a year. Their support is typically very good and has a live chat so you get answers often directly.
Hope you got it figured out by now.
I applied twice in the google forms for a developer key for soundcloud to use a widget on my website. It has been more than 3 weeks and I have still not got any reply from them. What do I do?
I'm afraid you just have to wait until they respond. I have applied 3 times now and keep getting rejected and the response is a generic answer not explaining why you were denied. For me I think it is the APP URL, yet they don't explain, it is so frustrating.
Did you try email api#soundcloud.com on my first rejection they were very friendly and replied with advice, however second time they did not.
You can also try calling help on +4930467247600 however they have not worked for me.
Lastly I read online that one person heard nothing from them for weeks and checked his SoundCloud developer page under 'YOUR APPS' and his app was there set up and with the client id and secret etc. He was just never informed that he got it. So hopefully that is the story in your case.
For me it took four weeks. I contacted them via Twitter and Email. They responded but all they said was:
"As mentioned previously, we’re currently working through applications
as quickly as possible, although there has recently been more requests
than usual lately causing delays.
You should receive confirmation soon though."
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
Trying to login to paypal sandbox but its giving me 'try again later' message.
do you know if its downtime or something like that?
Exact message : We're unable to complete your request. Please try again shortly.
Thanks
Janki
I think so as I tried logging in here
https://www.sandbox.paypal.com and it took like 2 min to load; didn't timeout though. Besides the cache/cookie obvious; try clearing out the java cache data in the java of the control panel and try a different browser to see.
you can try resetting the password of the login you're trying # developer.paypal.com; see if that works.
Worse case you can wait, or submit a ticket at paypal.com/mts / contact support.
Well, I got reply on twitter by Paypal that it was down for half a day and now up.
This is sorted now, it was issue on Paypal Sandbox.
Thanks
Janki
After paypal updated their interface (sandbox.paypal.com for example is not working, now you have to go to developer.paypal.com) many of the things are not working: 2 of them are particularly frustrating and I was hoping someone here knew how to get around them:
Am I the only one whose sandbox customer test accounts are not able to make purchases? The transaction page says they are not available.
IPN validation is not letting me send a https request. When I do it says there is something wrong with the server name. Yesterday however before the update I could get verified status. If I dont put https, now my handler gives me an invalid responde status, code: 400. What does it mean?
To fix the HTTP 400 error, follow the instructions in https://www.x.com/content/bulletin-ipn-and-pdt-scripts-and-http-1-1 and update your code to pass "Host" information. Ideally, things should work with just the recommended changes from the above link. Apparently, thats not the case. Here is a fix from one of the PayPal MTS person - PalPAL sandbox IPN processor rejecting all messages?
Remove the "cmd=notify-validate" option from the validation URL. I tried this and it worked. Though it doesn't return the right string, atleast it doesnt break with the 400 error.
While we wait for a fix from Paypal, I wonder how a company like PayPal can cause such a huge blunder and not post anything on their status page - https://www.x.com/developers/paypal/documentation-tools/site-status/pp-cri. It just makes you think that even smaller companies can do a better job than companies like PayPal.
For the code:400 issue, you have to update the post to version 1.1. That information is located here.
https://www.x.com/content/bulletin-ipn-and-pdt-scripts-and-http-1-1 in this bulletin.
However, as I posted before the asp.net example uses a call, that does not exist, so I was only able to get mine partly working. After fixing this, the servers appear to be rejecting calls to https, or the cert they have installed is invalid.
Action Required before February 1, 2013
Merchants need to update their IPN and/or PDT scripts to use HTTP 1.1, and include the “Host” header in the IPN postback script. In addition to this bulletin, these merchants will be notified via a direct email.
Alright, seems to be fixed!
If you are having trouble logging in, like suggested above, clear cache and cookies and try again.
Regarding the error 400, seems to have been solved by paypal!