>
> I am embarrassed to say I have never worked on the payment modules of
> an e-commerce system. Somebody else always did it.
>
> But I have talked to one of those somebodies, and she says there are 4
> main pieces that an e-commerce vendor needs to accept credit card
> payments:
>
> 1. A credit card gateway, for example Authorize.net or Skipjack.
>
> 2. A processing layer between the gateway and the bank, for example
> http://advancedpaymentsolutions.net/
>
> 3. A merchant account at a bank.
>
> 4. An SSL certificate.
>
> That's a lot of setup. Each piece has subscription costs, and several
> of them also have transaction fees.
Or, you could just go through PayPal or Google's checkout system and
save all of those troubles if cost is such a significant issue for
this particular set of users.
S
>
> On May 19, 8:59 am, "sstein...@gmail.com" <sstein...@gmail.com> wrote:
>> Or, you could just go through PayPal or Google's checkout system and
>> save all of those troubles if cost is such a significant issue for
>> this particular set of users.
>
> It's not just the cost, it's all the setup. I'd prefer closer-to-
> instant gratification.
Then you have to figure out how to multiplex a single holding account
and disburse money to the correct customer. Huge overhead and more
cost and setup by far than setting up a simple PayPal account.
> I'm aware of those services. And maybe having the e-commerce software
> try to handle it all is a stupid idea?
Yup.
> If I understand correctly, both PayPal and Google Checkout require the
> merchant to have an account.
Or, see above; you have to disburse the money at some point making you
responsible for all the bookkeeping, accounting, taxes, etc. Bleh!
> Google Checkout appears to require the buyer to have or set up an
> account, too, while PayPal apparently does not.
Right. PayPal's the lowest impedance but some customers resist using
it if they see it, which they don't have to.
S