PEAR payment gateway abstraction layer

[11abacus]

Hi,

Just wondering if any of you has thought about or is working on a
payment gateway abstraction layer (PEAR-style)?

I'm interested on developing that or at least start a discussion about
it.

The package would provide a framework for all types of online (and
offline?) payment transactions.

- Authorize.net, PayPal, ...,
- eChecks,
- Credit cards,
- Authorize only, charge, refund...
- Through specialized PHP extensions or simple use of CURL...

Basically a drop-in package to make integration of a payment gateway
into a site as easy as PEAR::DB is for databases.

If you know of an other discussion going on currently about the
subject, feel free to post a reference to it here.

-Philippe

[Nikolai Chuvakhin]

[email]jausions@hotmail.com[/email] (11abacus) wrote in message
news:<1a2a8cd7.0311120854.74bd8bb6@posting.google. com>...

>
> Just wondering if any of you has thought about or is working
> on a payment gateway abstraction layer (PEAR-style)?

Why even bother? Abstraction layers are humongous resource wasters.
In addition, each processing company has its own API, so there are
potentially dosens of APIs out there...

Also, think of security. Adding an abstraction layer increases
the number of potential security holes. Not a good thing for a
money-handling application...

> Basically a drop-in package to make integration of a payment
> gateway into a site as easy as PEAR::DB is for databases.

With performance drags as severe as PEAR::DB's (150-170% overhead)?
I don't think so...

Cheers,
NC