danmcb has asked for the wisdom of the Perl Monks concerning the following question:

It's here

The point is that you have to know something about the incoming IPN POST request from PayPal before you can go back to the PayPal server and ask "Is this valid?"

So the synopsis example, where you just instantiate with no args, seems incorrect to me.

What am I missing? Is this one of those things where I don't get it because it's too simple?

  • Comment on Business::PayPal::IPN synopsis doesn't make sense to me

Replies are listed 'Best First'.
Re: Business::PayPal::IPN synopsis doesn't make sense to me
by Anonymous Monk on Jul 24, 2008 at 08:56 UTC
    If you don't already know what PayPal IPN is this library may not be for you. Consult with respective manuals provided by PayPal.com
[reply]

      I think that I do know what it is. I've been reading the manuals for a while, and have implemented it before. Hence I don't see how the example given in the synopsis can possibly work, unless it somehow incorporates a web server to receive the incoming IPN POST req from PP (in which case where is the config for that?)

      I would have expected something like:

      my $hash = $cgi->params(); # the incoming POST params
my $ipn = Business::PayPal::IPN->new( $hash );
if ( $ipn->isOK ) {
 # further checks here ...
} else {
 # invalid, log it
}

      Basically, it needs to know something about your config and the post to work, where is that info?

      Or maybe PayPal really does work like magic ...

[reply]
        As soon as you receive payment to your PayPal account, PayPal posts the transaction details to your specified URL, which you either configure in your PayPal preferences, or in your HTML forms' "notify_url" hidden field........ Business::PayPal::IPN is the library which encapsulates all the above complexity into this compact form:

        So it looks like it is too simple

[reply]
        It creates its own CGI internally.
[reply]

Back to Seekers of Perl Wisdom