Editing Usertransfer manual

{{Sidebar}}
__NOTOC__

<h1>Internal (user) domain transfers</h1>

User transfers can be used for transferring domain objects internally between HEXONET resellers.

User transfers for gTLDs and nTLDs are billed exactly the same way as regular transfers. As a result, when an internal transfer is initiated by a reseller (with authorization code), the reseller will be immediately charged the renewal fee for the respective domain, if applicable. As always, if a transfer fails, like regular transfers, all fees are automatically refunded. Conversely, if the transfer succeeds, this will trigger an explicit renewal (when applicable) for the domain at the respective registry.

User transfers for ccTLDs are not renewed or charged a fee.

<h2>Requirements</h2>

<ul>

<li> The domain must already exist within the HEXONET System
<li> No former transfer request should be active when submitting the request
<li> It is not allowed that the domain changes the Registrar-Account (REPOSITORY)

</ul>

<h2>How does a user transfer work ? </h2>


'''1.''' User B requests the transfer

<pre>
command = TransferDomain
action = usertransfer
domain = <DOMAIN>
auth = <AUTH>
</pre>

'''2.'''  User A receives an EVENT message of the HEXONET system. From now on he has got the possibility to:


'''3. DECLINE'''

<pre>command = TransferDomain
action = deny
domain = <DOMAIN>
</pre>

or


'''3.1 APPROVE'''

<pre>command = TransferDomain
action = approve
domain = <DOMAIN></pre>


'''4. FLOWCHART'''


[[File:User_transfer.png]]

''' INFORMATION'''

{{warnbox|
In case that user A does not react to this EVENT within 5 days, the transfer will be ''' AUTO APPROVED''' since it has been requested with a valid authorization code. After the approval, the domain is with user B.
}}