If you can reimburse their credit card, then a better solution (for you)
is to:
- Do a lookup on all the domains they wish to register
1
- Charge them that amount
2
- Attempt to register them
3
- If any fail, reimburse
If you have an outage at point 1, then who cares?
At point 2, then there's a possibility you may have to reimburse more, or
everything.
At point 3, then that doesn't matter because you probably have a couple
days before you have to reimburse before anyone would notice. Plus you
could have a program that looks-up pending reimbursements in your
database, and emails them them explaining the outage and the
reimbursement.
Since your credit card fees will always be less than your domain cost,
this solution is better. Of course, if my credit card link supported
locking amounts, and then capturing later (a few seconds later) that would
be ideal.
Mark Collette
hyperbyte inc.
On Tue, 1 Aug 2000, Vladimir Jebelev wrote:
>
>
> On Thu, 27 Jul 2000, Bill Gerrard wrote:
>
> > > - acquire funds
> > > - if fails (which is very unlikely, since authorization was successful)
> > > then send a notification to customer support folks, so they can
> > > try to re-submit credit card later, and it fails again,
> > > ***unregister domains***
> >
> > Unfortunately TUCOWS.com/OpenSRS does not share the ability to "unregister
> > domains" with their RSP's but it sounds like they allow their internal
> > retail registration group do it (i.e. Domain Direct), is this correct?
> >
> >
>
> No, Domain Direct people use the same APIs. I didn't specifically mean
> 'use unregister capabilities of OpenSRS API', but rather, - make sure
> those domains can not be used by the guy whose credit card failed on
> capture funds, it may simply mean resetting contact and nameserver info to
> your RSP.
>
> In practice, you never have to resort to such measures: we are not talking
> about stolen credit cards numbers or exceeding credit limits - those cards
> will fail on authorization. The likelyhood of a successful authorization
> and then failure on capturing funds 1-2 seconds later is virtually zero:
> even if your network connectivity goes down during that window, you should
> be able to capture that transaction later.
>
> Vlad
>
