IPN Verify endpoint updates and SSL adjustments.
PayPal apparently has a new subdomain for IPNs and they are also going to eliminate HTTP verifications. It will need to be HTTPS.
Need to change to the new domain (ipnpb.paypal.com and ipnpb.sandbox.paypal.com).
The change doesn't get enforced until 9/30/2016. We should add a notice in the plugin about this with a link to the URL above.
Comments (22)
-
-
add exit function, ref
#70→ <<cset 6e7514708eac>>
-
remove js code, ref
#70→ <<cset a6088a54118f>>
-
- changed status to resolved
Resolve issue
-
reporter I noticed you set the end points so they won't switch until the date the documentation says the change will happen. I think that's simply the date by which you need to get this done, though. I'm pretty sure the new endpoints should already work, so we don't necessarily need to do that. Were you able to test the new endpoints now?
The link in the original issue notes does say that the new URLs should be working already and we should use those going forward, so I think we just need to go ahead and make the switch now.
-
reporter - changed status to open
Re-opening because I had a question for @kcppdevelopers
-
remove date, ref
#70→ <<cset 967880996860>>
-
IPN Verify endpoint updates and SSL adjustments, ref
#70→ <<cset aaf9ee536dc1>>
-
I have checked new endpoint but it seems it not validate IPN data.
-
I have checked below endpoint:
For sandbox: https://www.ipnpb.sandbox.paypal.com and https://www.ipnpb.sandbox.paypal.com/cgi-bin/webscr but it not validate IPN response data.
https://www.sandbox.paypal.com/cgi-bin/webscr endpoint is working fine for me.
-
reporter @kcppdevelopers When you say it doesn't validate, are you getting a good response, but it's simply invalid every time? Or are you getting an empty response? a 404, or what exactly?
-
I am getting error like Couldn't resolve host 'www.ipnpb.sandbox.paypal.com'.
-
reporter Are we using https:// when sending the POST back to that URL? Per the documentation about this issue, that endpoint only accepts https:// POST back.
-
reporter Ah, yes, I reviewed the code and it does look like we're using https://
-
IPN Verify endpoint updates and SSL adjustments, ref
#70→ <<cset c812e87b0526>>
-
I have push latest code in issue-70-A branch and add date condition for new endpoint.
-
reporter The PayPal MTS rep says it should be working fine right now.
From the information I have, this endpoint should be available and only accept https.
I am able to do a DNS lookup and see it resolve to IP 173.0.82.66 which matches what I see https://www.paypal-knowledge.com/infocenter/index?page=content&widgetview=true&locale=en&id=FAQ1157&actp=search&viewlocale=en_US&searchid=1456247528389 and select ipnpb.sandbox.paypal.com from the Additional IPs box.
So it seems like there is an issue with a setting, config, dns table, that is having an issue.
-
IPN Verify endpoint updates and SSL adjustments, ref
#70→ <<cset 3a20ce9a49df>>
-
Now it's working fine.
-
- changed status to resolved
Resolve
-
reporter - changed version to 1.1.0
-
reporter - changed status to closed
- Log in to comment
IPN Verify endpoint updates and SSL adjustments, ref
#70→ <<cset 8e080eaa1c46>>