E-Commerce Merchants (part 2)

[Ray Paseur]

One consideration in designing a web interface to a payment system is the
ability to switch e-commerce providers seamlessly. Has anyone looked into
"isolating" the ecommerce part of a web site so that you could change banks
or merchant accounts without disrupting your users? What comes to mind for
me is a period of overlap, so fulfillment and chargeback is given time to
expire on the old merchant. Also, the need to "skin" the store so site
users see a consistent look and feel through as much of the process as
possible. Any other thoughts? Know of any good tutorials?

Thanks to all for sharing your ideas,
~Ray

[Michael Vilain]

In article <2I1Od.55993$jn.44580@lakeread06>,
"Ray Paseur" <ra*@earplugsnon-aol.com> wrote:

One consideration in designing a web interface to a payment system is the
ability to switch e-commerce providers seamlessly. Has anyone looked into
"isolating" the ecommerce part of a web site so that you could change banks
or merchant accounts without disrupting your users? What comes to mind for
me is a period of overlap, so fulfillment and chargeback is given time to
expire on the old merchant. Also, the need to "skin" the store so site
users see a consistent look and feel through as much of the process as
possible. Any other thoughts? Know of any good tutorials?

Thanks to all for sharing your ideas,
~Ray

I wrote a custom interface to an existing web site that charges via
Authorize.net. I didn't select the provider. The bank said "We work
with this provider. Use them.", so that's what we did. So far, they've
been very helpful and provide a full set of specs for me to code my
pages.

If you're using Quickbooks and want to charge through the program, you
might look into their service. Find out if they have a web-interface
you can hook into. That way you'll have a manual program you can use
and a web-interface for on-line transactions.

--
DeeDee, don't press that button! DeeDee! NO! Dee...