Usertransfer manual - Revision history

WikiAdmin at 23:36, 1 April 2019

2019-04-01T23:36:56Z

WikiAdmin at 13:00, 14 December 2016

2016-12-14T13:00:31Z

WikiAdmin at 10:52, 14 December 2016

2016-12-14T10:52:38Z

WikiAdmin at 10:50, 14 December 2016

2016-12-14T10:50:23Z

WikiAdmin at 10:38, 14 December 2016

2016-12-14T10:38:31Z

WikiAdmin at 10:18, 14 December 2016

2016-12-14T10:18:28Z

WikiAdmin at 10:17, 14 December 2016

2016-12-14T10:17:50Z

WikiAdmin at 11:08, 17 July 2015

2015-07-17T11:08:18Z

WikiAdmin at 13:43, 11 February 2013

2013-02-11T13:43:19Z

WikiAdmin: Created page with "{{Sidebar}} NOTOC

Internal (user) domain transfers

Usertransfers can be used for transfering domain objects internally between HEXONET resellers. Usertransfers..."

2012-08-28T14:44:34Z

Created page with "{{Sidebar}} __NOTOC__ <h1>Internal (user) domain transfers</h1> Usertransfers can be used for transfering domain objects internally between HEXONET resellers. Usertransfers..."

New page

{{Sidebar}}
__NOTOC__

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

Usertransfers can be used for transfering domain objects internally between HEXONET resellers.

Usertransfers for gTLDs COM, NET, ORG, BIZ, INFO, NAME, MOBI, TEL & ASIA 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 transfers succeeds, this will trigger an explicit renewal (when applicable) for the domain at the respective registry.

Usertransfers for all other TLDs are free of charge.

<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>

optional

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>

In case that user A does not react to this EVENT within 5 days, the transfer will neither be

1.''' Auto approved''' - in case that the transfer has been requested with a valid authorization code. After the approval, the domain is with user B.

or

2. ''' Auto denied''' - in case that the transfer has been requested without stating an authorization code. The domain will stay with user A.

← Older revision		Revision as of 13:00, 14 December 2016
Line 58:		Line 58:
	[[File:User_transfer.png]]		[[File:User_transfer.png]]

−	~~<span class="label label-important">@INFO:~~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.~~</span>~~	+	''' 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.
		+	}}

← Older revision		Revision as of 10:52, 14 December 2016
Line 58:		Line 58:
	[[File:User_transfer.png]]		[[File:User_transfer.png]]

−	<span class="label label-important">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.</span>	+	<span class="label label-important">@INFO: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.</span>

@@ Line 58: / Line 58: @@
 [[File:User_transfer.png]]
+<span class="label label-important">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.</span>
-−
-<span class="label label-important">INFORMATION</span>
-<pre>
-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.
-</pre>

← Older revision		Revision as of 10:38, 14 December 2016
Line 59:		Line 59:


		+
		+	<span class="label label-important">INFORMATION</span>
		+	<pre>
	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.		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.
		+	</pre>

← Older revision		Revision as of 10:18, 14 December 2016
Line 55:		Line 55:
	'''4. FLOWCHART'''		'''4. FLOWCHART'''

−	~~The flowchart of the usertransfers.~~

	[[File:User_transfer.png]]		[[File:User_transfer.png]]

@@ Line 4: / Line 4: @@
 <h1>Internal (user) domain transfers</h1>
-Usertransfers can be used for transfering domain objects internally between HEXONET resellers.
+User transfers can be used for transferring domain objects internally between HEXONET resellers.
-Usertransfers 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 transfers succeeds, this will trigger an explicit renewal (when applicable) for the domain at the respective registry.
+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.
-−
-Usertransfers for all other TLDs are free of charge.
 <h2>Requirements</h2>

@@ Line 51: / Line 51: @@
 action = approve
 domain = <DOMAIN></pre>
 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.

@@ Line 6: / Line 6: @@
 Usertransfers can be used for transfering domain objects internally between HEXONET resellers.
-Usertransfers for gTLDs COM, NET, ORG, BIZ, INFO, NAME, MOBI, TEL & ASIA 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 transfers succeeds, this will trigger an explicit renewal (when applicable) for the domain at the respective registry.
+Usertransfers 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 transfers succeeds, this will trigger an explicit renewal (when applicable) for the domain at the respective registry.
 Usertransfers for all other TLDs are free of charge.
@@ Line 30: / Line 30: @@
 action = usertransfer
 domain = <DOMAIN>
 auth = <AUTH>
 </pre>
@@ Line 56: / Line 53: @@
-In case that user A does not react to this EVENT within 5 days, the transfer will either be
+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.
-−
-−
-.''' Auto approved''' - in case that the transfer has been requested with a valid authorization code. After the approval, the domain is with user B.
-−
-or
-−
-. ''' Auto denied''' - in case that the transfer has been requested without stating an authorization code. The domain will stay with user A.

← Older revision		Revision as of 13:43, 11 February 2013
Line 56:		Line 56:


−	In case that user A does not react to this EVENT within 5 days, the transfer will ~~neither~~ be	+	In case that user A does not react to this EVENT within 5 days, the transfer will either be