I had started a row on the list a couple of months ago about a similar situation.
We had a customer do a chargeback on her credit card and that reversal included a domain name fee. In this instance, she had paid for it before we registered it so that really wasn't an issue. I logged in and changed her password to lock her out. If we paid for it and she didn't, it should belong to us, right? Wrong. I was made to give her the password so she could move it. We registered it for her on her behalf. Since we are not the registrant we were not authorized to alter the registrant's information. We, basically, guaranteed payment for the registrant at the time of registration to ICANN and anything that happens after that is our problem, not ICANN's. Or that at least was the final gist of the conversation. Good Luck, John T. Jarrett [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of D. Clarke Sent: Tuesday, July 15, 2003 8:03 AM To: [EMAIL PROTECTED] Subject: protection from non paying clientel Hi; I have a small situation here with a client who owes us a fair amount of money and is trying to transfer his domain away (run and hide, basically) I had locked his domain to prevent him from moving out completely but now that seems to be going against me. He claims a payment made the other day has "paid" for his domain, although standard FIFO accounting procedures places his invoiced domain somewhere near the end of the list and thus has not paid. OpenSRS compliancy is after me (courtesy of him complaining) and I'm stuck; If we cannot protect our company from rogue clients such as this by using the only asset available what is to stop others from doing the same thing? If there is nothing to seize or do in a situation like this, we're stuck hoping he pays or send him to collections and lose a lot of what he owes (if he even pays them) Anybody have any ideas of situations similar to this? Please reply to the list (unless this is considered off topic...) ~ Darryl
