Actually, we used to do it that way, we would first do a "Pre-Auth", after they filled in the data, before it loaded the verify_order page. Then after the order WAS successful, we'd use a "FORCE" to for the charge from the pre-auth. We have since then changed processors, so we can't do that, that is why we made the system we did.
I look forward to being able to do so again, even though they charge us for 2 transactions per order. It was a better way to do it. Anyways, just a thought. Richard. ----- Original Message ----- From: "Charles Daminato" <[EMAIL PROTECTED]> To: "Jesse Williams-Proudman" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Monday, September 02, 2002 9:31 PM Subject: Re: Registration Billing Method Question > If you can authorize and charge as two seperate steps, I'd do > this: > > 1) authorize (which "holds" funds for some processors temporarily) > 2) attempt to register the domain name > 3) if successful, charge the card (if not, "de-authorize", or > equivalent) > > :) > > Charles Daminato > TUCOWS Product Manager > [EMAIL PROTECTED] > > On Mon, 2 Sep 2002, Jesse Williams-Proudman wrote: > > > I have a question for how you all do billing for your registrations. Here > > was my plan: > > > > Gather Registration and Billing Data > > Authorize and Charge The Card > > Attempt To Register The Domain > > > > Now my problem is if the domain registration fails, I've still billed the > > card? Should I now issue a void or what? > > > > What do you all do? > > > > -- > > > > Jesse Williams-Proudman || CEO > > NineWire Digital Solutions || +1.888.873.6199 > > [EMAIL PROTECTED] || http://ninewire.com > > Mac Web Hosting & Colocation || Mac Nationwide Dialup > > > > $75 Xserve Colocation Special from Your Mac ISP! > > > > > > >
