paypal ipn

[pkocsis]

ughhh.....

I've read all I could...searched the lists, this forum...to no avail.

I'm trying to write my ipn listener program in livecode. When I test in the sandbox, if I construct my reply (either GET or POST; constructed properly, both work) I can get it to work if I post to paypal via http. I cannot get it to work posting to https. It looks like as soon as the socket gets opened, paypal closes it.

At first I thought the sandbox was hosed (which in many ways, it is)....but when testing, if I take my reply string and use a browser to post back (to https) I get 'VERIFIED'. So this tells me that the sandbox indeed should work by posting to https.

Is it a headers thing? or something my browser is doing ssl-wise that the live code 'post' command (or get url) is not doing/providing?

Can anyone shed light on this? I'd use curl, but am on a windows machine (I know there is curl for windows, but, sheesh...I'm trying to avoid that route)

There's got to be a way of using 'post' or replying with a GET method using url.....no?

HELP!

[Mark]

pkocsis

Try to put this line at the beginning of your script:

libUrlSetSSLVerification false

It must be in the handler(s) that use(s) the post URL command.

If this doesn't work, then perhaps you could write the system as a PHP script and make your Revolution stack connect to it. I made several PayPal systems in which Revolution connects to a PHP-based system on the server.

Btw, I recently used the PayPal sandbox and it still works as expected (clumsy but functional).

Kind regards,

Mark

[pkocsis]

Hi Mark,

Thank you so much for replying!

I have tried:

libUrlSetSSLVerification false

...to no avail. Same results. I have since punted and am using a call to curl. Got it all working fine using curl. I agree that sandbox is 'functional', but I found that some fields were missing or obsolete as compared to current live paypal.....oh well....it was certainly functional to get my mechanism working

Thanks again Mark!