{"id":145,"date":"2013-08-08T01:09:48","date_gmt":"2013-08-08T01:09:48","guid":{"rendered":"https:\/\/www.joetannorella.com\/?p=145"},"modified":"2013-08-08T01:09:48","modified_gmt":"2013-08-08T01:09:48","slug":"paypal-ipn-sandbox-returning-invalid","status":"publish","type":"post","link":"https:\/\/www.joetannorella.com\/paypal-ipn-sandbox-returning-invalid\/","title":{"rendered":"Paypal IPN sandbox returning INVALID"},"content":{"rendered":"

This is an issue that is very easily overlooked. Paypal have to have some credit here in that they basically give you all the code required to get the IPN up and running properly – and, apart from the issue I’m going to tell you about next, it really does work straight out of the box.<\/p>\n

Using the Paypal Sandbox to generate test IPN<\/a> visits, I kept getting an INVALID response. To find out what my response was, I simply added a different integer to my order_status column; 1 for VERIFIED, or 2 for INVALID.<\/p>\n

What you need to do is make sure that when you POST back the IPN data to Paypal, you alter the URL to “https:\/\/www.sandbox<\/strong>.paypal.com\/cgi-bin\/webscr” instead of “https:\/\/www.paypal.com\/cgi-bin\/webscr”. Seems pretty obvious, but also easy to overlook.<\/p>\n

If this doesn’t solve your problem, maybe these links will help:<\/p>\n