http://e-junkie.com operates as a payment abstraction layer for a few services (Paypal, Google Checkout, 2CheckOut, etc). That is my primary use for them these days, although they do other things, too.
From the perspective of my website, I don't care whether someone pays with Paypal or Google Checkout. Both transactions are wrapped by e-junkie in a consistent API, then POSTed to a URL I gave them. Some Rails magic handles it from there.
Comments
http://e-junkie.com operates as a payment abstraction layer for a few services (Paypal, Google Checkout, 2CheckOut, etc). That is my primary use for them these days, although they do other things, too.
From the perspective of my website, I don't care whether someone pays with Paypal or Google Checkout. Both transactions are wrapped by e-junkie in a consistent API, then POSTed to a URL I gave them. Some Rails magic handles it from there.
They are more like what I would call a shopping cart provider, but the effect is the same for many businesses.