FYI,
This is how Network Solutions does it. They charge the credit card first.
If they are unable to register the domain, then send a message to the
registrant that the domain registration failed and that they will be
refunded the fees back to the credit card.
With that said, many merchant accounts let you do an authorization only,
provide the product, then make the final deposit. This could be an ideal
solution if you don't want to have to provide refunds. I would suggest
checking with your merchant account provider to see if they offer this.
>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?
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:35:15 EDT