> The solution is to check that the domain doesn't exist, authorize the
> payment, get the domain, and then charge the card. Yes, if the credit
> limit somehow gets reached between 2 and 4 you're screwed, but you're
> screwed if they chargeback, which is more likely anyway.
Actually, the auth step puts a hold on the funds in the consumer's credit
card account. If you do the final deposit within a short amount of time
(depends on the merchant account provider), then you are pretty safe.
> On Wed, 26 Jan 2000, Lars Hindsley wrote:
>
> > We have a case here of what comes first...
> >
> > We have a form now incorporating all info including credit card info.
> >
> > We need to take into account that one of two things can fail.
> > If you charge the card first and a domain fails, you have charged for a
> >
> > domain they didn't get if you register the domain and the charge fails,
> >
> > you are stuck paying for a domain you don't need.
> >
> > Anybody know the solution? The fact is we already pace a user
> through the whois.
> >
> > It drops the domain into the form if it is available. Have we
> already solved our problem?
> >
> >
> > Best Regards,
> > Lars Hindsley | Project Leader
> > SpyProductions
> >
> >
> >
> >
>
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:15 EDT