By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,831 Members | 1,031 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,831 IT Pros & Developers. It's quick & easy.

PEAR payment gateway abstraction layer

P: n/a
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
Jul 17 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
ja******@hotmail.com (11abacus) wrote in message
news:<1a**************************@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
Jul 17 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.