Service Transfer

91 vues Markdown

Release a domain to another registrar or keep it from leaving, by driving the provider's own transfer lock and auth code from the service record instead of its panel.

Opening the Screen

Open a domain from Orders › Services, then pick the Transfer tab: {admin}/services/detail?id={service}&content=transfer

Two conditions have to hold for the tab to be rendered: the service type is a domain, and its status is Active. A domain that is still being registered, suspended or cancelled does not show the tab at all, because neither action on it can be carried out at the registrar in those states.

An Incoming Transfer Is Followed Elsewhere

While a domain is being transferred to you the service is not active yet, so this tab is absent. The progress line, the last check time and the Check Now button for that direction sit on the Details tab.

What Is on the Screen

The tab holds two cards side by side, and nothing else. Each owns a single registrar capability and falls back to a read-only state when the module bound to the service cannot provide it.

Card	What it does	When it can be used
Transfer Lock	Shows the recorded lock state and lets you open or close it at the registrar.	The module exposes any transfer-lock method, one that changes the lock or only one that reads it, and the service is active with a module bound to it.
Auth (EPP) Code	Asks the registrar for the authorization code the gaining registrar will require.	The module exposes an auth-code method and the service is active with a module bound to it.

Transfer Lock

The card opens with one explanatory line, When transfer lock is enabled, the domain cannot be transferred to another registrar., followed by a state block: a padlock icon, the state in words, and the switch that changes it.

A closed green padlock next to Transfer lock is enabled means the domain is held; an open amber padlock next to Transfer lock is disabled means it is free to leave. Under the state, a clock line reports how long ago the lock was last changed. It is printed only when a valid change time has been recorded, so a domain whose lock was never touched from here shows no time at all; after the first change made here it appears on the next reload and is rewritten in place from then on.

The state shown is the value recorded the last time the lock was changed, not a fresh question put to the registrar while the tab loads. If someone opened or closed the lock in the provider's own panel, this card keeps showing the older answer until something writes a new one.

Auth (EPP) Code

Under the same kind of explanatory line, The authorization code required to transfer this domain to another registrar., sits a row of three controls: a read-only field that starts masked, a clipboard button with the Copy to Clipboard tooltip, and the Get Auth (EPP) Code button. A hint line, Retrieve the current Auth (EPP) code from the registrar., closes the card.

The field holds nothing until you press the button and the value is never stored: reload the screen and it is masked again. A code fetched here is never written into the service record.

Two answers are normal, and which one you get is the registrar's decision rather than a setting. Some providers hand the code back and it lands in the field. Others refuse to expose it over the API and mail it to the domain's own contact address instead; no code appears then, and a message confirms it was sent to the owner.

When the Cards Are Read-Only

Each card decides on its own whether it can act. If the module bound to the service has no matching method at all, or the module itself failed to load while the page was built, the card drops its control and prints a plain notice instead: Transfer lock management is not available for this module. or Auth code management is not available for this module.

The lock card counts any lock method, whether it changes the lock or only reads it, so the notice appears only when the module offers neither. A registrar that can report the lock but not change it therefore keeps a working switch, and flipping it comes back with the module's own refusal instead of a new state. A lock that always refuses is a limit of the provider, not a fault of this screen; use the provider's own panel for that domain.

The two cards are independent, so a registrar can support the lock but not the auth code and the tab then shows one working card and one notice. The lock card still shows the recorded state in its read-only form, so the notice means the lock cannot be changed from here, not that the domain is unlocked.

Before You Use It

The service must be a domain with the status Active, or the tab is not rendered.
The service must be bound to a registrar module and that module must load. A domain kept as a record only reaches the tab with both cards read-only.
The registrar account behind the module needs the rights for these two calls, since the request is passed through with the credentials stored on the module.
Both actions need the service operation privilege; a read-only administrator sees the tab but cannot act on it.

Fields

Transfer Lock The switch on the right of the state block. Its starting position is the recorded lock state: on for a held domain, off for a released one. Every change is sent to the registrar first and written to the service only once the registrar accepts it.

Transfer lock is enabled The state in words, next to the padlock icon. It turns into the disabled wording, and the icon into an open amber padlock, as soon as a successful change comes back; the clock line is rewritten at the same moment.

Transfer lock management is not available for this module. Replaces the switch when the module offers no lock method at all, neither one that changes the lock nor one that reads it, or could not be loaded. A module that can only read the lock keeps the switch instead and refuses the change when it is flipped. The padlock and the state wording stay, because the recorded state is still worth reading.

Auth (EPP) Code Read-only and masked until a code is fetched. It cannot be typed into: the value only arrives from the registrar and is discarded when the page is left.

Get Auth (EPP) Code Asks the registrar for the code. Depending on the provider it either fills the field beside it or reports that the code was emailed to the owner.

Auth code management is not available for this module. Replaces the whole field and button row when the module has no auth-code method. The code then has to be obtained from the provider's own panel.

Tasks

Releasing the domain

Open the service from Orders › Services and pick the Transfer tab.
In the Transfer Lock card, switch off the toggle at the right of the state block.
The request goes to the registrar straight away, with no confirmation window in between.
On success the padlock opens, the line reads Transfer lock is disabled and the clock line resets to the current moment. If the registrar refuses, an error is shown and the switch snaps back, so the screen never claims a change the provider did not make.

Holding the domain again

On the same Transfer tab, switch the Transfer Lock toggle back on.
The registrar closes the lock and the new state is recorded with a fresh change time.
The padlock turns green, the line reads Transfer lock is enabled, and the domain drops out of the automatic re-lock queue described below, which only looks at domains whose lock is recorded as open.

Getting the auth code

On the Transfer tab, press Get Auth (EPP) Code in the Auth (EPP) Code card.
Wait for the answer; the button shows a loading state while the call is out.
If the code comes back it appears in the field to the left of the button; take it with the clipboard button carrying the Copy to Clipboard tooltip, since the field is read-only. If the provider mails it instead, the field stays masked and a message confirms it was sent to the domain owner.
Hand the code to the customer together with the open lock. Reloading the tab clears the field, so copy it before leaving the screen.

Things to Watch

An Open Lock Plus a Code Is a Complete Handover

Those two together are everything the gaining registrar needs. Once the transfer completes at the registry, nothing on this tab can pull the domain back. Release the lock only for a transfer you have already agreed to.

The Lock Closes Itself After Two Weeks

An automatic job checks released domains once a day and closes the lock again at the registrar 14 days after it was opened, counting from the change time shown under the state. A transfer still pending after that window fails at the gaining registrar, so a slow transfer needs the lock opened again.

The Customer Can Change the Lock Too

The same switch exists in the client area, and a change made there is written to the same record. If the state here surprises you, look for the earlier change before assuming a registrar problem. The two sides are not recorded the same way: a change made here goes only to the activity log, with the service name, while a change the customer made is written twice, to the activity log as a client action and to the service's own History tab. So the activity log holds both sides and is the place to start; the History tab tells you the change came from the customer.

Required Privileges

Opening the service detail and reading this tab is covered by SERVICES_LOOK. Both actions on the tab, changing the transfer lock and requesting the auth code, require SERVICES_OPERATION; without it the requests are refused, however they were triggered.

Cet article vous a-t-il été utile ?

Merci pour votre retour !

Besoin d'aide supplémentaire ?

Notre équipe d'assistance est disponible 24h/24 pour tout ce que vous ne trouvez pas ci-dessus.

Nous contacter Ouvrir un ticket