Re: Re: Payment_paypalipn submission
| From: | Jeremy Johnstone | Date: | Mon, 15 Dec 2003 04:04:21 +0000 |
| Subject: | Re: Re: Payment_paypalipn submission | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-24433@lists.php.net to get a copy of this message | ||
I have pre-existing code I have written for AuthorizeNET, 2checkout.com,
PayPal IPN, and Ibill so this may be the way to go. I will have a look
at your existing code, and will see what it will take to port everything
over to your API. Please feel free to contact me offlist at anytime and
I will be happy to discuss this further with you whenever is convenient
for you.
Jeremy
On Sun, 2003-12-14 at 20:04, Ian Eure wrote:
> On Sunday 14 December 2003 11:02 am, Mike wrote:
> > You should speak to Ian Eure, he is currently writing a Payment_Process
> > module which uses different modules and a common base class to provide a
> > constant API for different payment providers.
> >
> > His work is here
> > http://www.websprockets.com/~ieure/PEAR/Payment/
> >
> Indeed, welcome to the bleeding edge. Please feel free to contact me with any
> questions you have about Payment_Process.
>
> It looks like this would be a good fit for Payment_Process and PEAR in
> general. However, I recommend that you look at replacing the curl_*() calls
> with either the Net_Curl or HTTP_Request packages, both of which are in PEAR
> and provide a much cleaner interface than using PHP's cURL extension
> directly.