New PayPal Sandbox Returns 400 Bad Request for IPN Verification

1
votes

Call it bad timing, but I had literally just gotten this working last night, right before PayPal rolled out its new developer interface. I'm using PHP / cURL, and literally copied this code from x.com:
https://www.x.com/developers/PayPal/documentation-tools/code-sample/216623

At 10pm last night, it started returning 400 codes with an empty response body. Here are the response headers:

HTTP/1.1 400 Bad Request
Date: Fri, 08 Mar 2013 16:43:16 GMT
Server: Apache
X-Frame-Options: SAMEORIGIN
Set-Cookie: c9MWDuvPtT9GIMyPc3jwol1VSlO=%7cC8szeIKENkwUqfOEYTjk-zp16RPNDC2MvLBQq9QALLYk8LcDM9kDEELRUPR_lxii1ujHBm%7cAo_aiVmV13ssvg_VFFqLkSkrVuIkUVx3O9nb09-nmQbg21hzsBAPIAIUIW8XFO_wn3c6T0%7c; domain=.paypal.com; path=/; Secure; HttpOnly
Set-Cookie: cookie_check=yes; expires=Mon, 06-Mar-2023 16:43:16 GMT; domain=.paypal.com; path=/; Secure; HttpOnly
Set-Cookie: Apache=10.72.109.11.1362760996493186; path=/; expires=Sun, 01-Mar-43 16:43:16 GMT
Connection: close
Transfer-Encoding: chunked
Content-Type: text/plain; charset=ISO-8859-1

I'm using the IPN Simulator to test. Never get a "VERIFIED" or an "INVALID" response. Only a blank response body. Is anyone else having this problem?

1
phppaypal-ipnpaypal-sandbox

1 Answers

0
votes

Currently everyone is experiencing this error in the sandbox environment when we upgraded the developer accounts. We're currently working to resolve this issue however I'll be sure to update through this post you once it's resolved.

This is a completely new environment so please let me know if you are experiencing any other issues so we can correct them as soon as possible.