Domain transfers: from paid to completed
Push or registrar transfer, the buyer's details and defaults, the seller's authorisation code or push, the code's safety, evidence and the timeline, registry checks that complete the order, reminders and deadlines, and the admin Transfers page and registrar help.
Since 1.5.0 the hand-over of the domain is tracked on the marketplace. The domain itself still moves at the registrars (AIODomain is not a registrar), but both sides know what to do next, the authorisation code travels safely, deadlines are watched, evidence is kept, and the registry is checked so the order completes as soon as the domain really changed hands.
1. The two ways a domain moves
| Method | How it works | How long |
|---|---|---|
| Push (account change at the same registrar) | The seller moves the domain into the buyer's account at the seller's registrar. The buyer needs an account there and gives its name or e-mail. | Minutes. Not every registrar offers it (Cloudflare, Hostinger and Squarespace do not). |
| Registrar transfer (authorisation code) | The seller unlocks the domain and hands over the authorisation code (EPP / transfer key). The buyer starts a transfer-in at their own registrar with the code and pays that registrar's transfer fee (usually one year of renewal). | 5 to 7 days at most registries; faster when the losing registrar approves. A domain registered or transferred in the last 60 days cannot be transferred. |
| Another way | For special cases (an escrow agent, a broker, a registrar not in the list); the buyer explains in the note. | Varies. |
The marketplace keeps the buyer's money until the buyer confirms the domain is in their account (or the registry shows the change, or the confirmation period ends).
2. Buyer: tell the seller where to send it
After the payment the order page shows the Transfer box with a short intro (the marketplace's text) and the form: the method, the registrar (pick from the list or type another), your account name or e-mail at that registrar (needed for a push), a note, and Save as my default for future purchases so the next order skips this step. You have a deadline for it (24 hours by default); a reminder arrives when it passes, and the seller cannot start before you answer.
The box then shows the step-by-step help of your registrar for accepting a push or starting a transfer-in.
3. Seller: push or hand over the code
The sale page shows the buyer's choice and the help for your registrar:
- Push: move the domain to the buyer's account exactly as given, then click I pushed the domain with a note. The buyer is told to accept it.
- Registrar transfer: switch the transfer lock off at your registrar, make sure WHOIS privacy does not block the transfer e-mails, get the authorisation code, paste it into the form and tick The domain is unlocked. The code is stored encrypted; the buyer sees it on the order page only, never in an e-mail. You can replace the code if the registrar issues a new one. When the buyer starts the transfer, approve it at your registrar if it asks, so it does not wait the full five days.
When the hand-over is done, Mark as transferred with your note (the marketplace refuses it before the buyer's details and, for a registrar transfer, the code exist). The buyer is asked to confirm; without an answer the order completes after the confirmation period, and a verified registrar change completes it at once.
4. The authorisation code
Only the buyer can reveal the code, with a click on the order page; each view is counted (25 at most by default) and logged in the timeline. Staff can reveal it from the admin panel; that is audited. The code never appears in notifications, e-mails, links or logs.
5. Evidence and the timeline
Both sides can attach evidence to the transfer: a note, a link (for example to a registrar status page) or a file (a screenshot of the registrar panel, the registrar's e-mail as PDF). The other side is told. The timeline lists every step with who did it and when: details given, code provided, push done, transfer started, code viewed, registry checks, reminders, deadline extensions, staff actions. In a dispute the marketplace team reads the same timeline and evidence.
6. Registry checks
For a registrar transfer the marketplace looks the domain up every 12 hours (RDAP, WHOIS as a fallback). When the registrar of record changed from the seller's registrar to another one, the transfer is verified: both sides are told and the order completes, which releases the seller's money (the hold period still applies). While the registrar is unchanged the box says so, and when the transfer lock is still on, that too. A push cannot be seen from outside (the registrar stays the same), so a push completes with the buyer's confirmation. Staff can run the check at any time from the admin panel.
7. Reminders and deadlines
| Situation | Who is reminded |
|---|---|
| The buyer gave no details by the deadline | The buyer, daily (six at most); the seller once |
| The seller has not acted two days before the transfer deadline | The seller |
| A transfer has been in progress for five days without the buyer's confirmation | The buyer |
The transfer deadline is the order's delivery deadline (7 days after payment by default). Staff can extend the seller's or the buyer's deadline with a note from the admin panel.
8. Transfers in the admin panel
Finance -> Domain Transfers lists every transfer with tiles (open, waiting for the buyer, waiting for the seller, in progress, delivered, verified, stalled, average days) and tabs. Open one: the parties, the method, the registrar accounts, both notes, the deadlines with Extend, the registry block with Check the registry now, the audited Reveal the code, the evidence with uploads, the timeline, and the actions: act for the buyer (set the details), act for the seller (store a code, mark pushed), Mark delivered, Complete the order, Mark failed (with a reason; then refund the order from the order page) and Reopen at a chosen step. A Transfers stalled tile sits on the dashboard; the order record links to its transfer.
Domains -> Registrars holds the help texts per registrar (push steps, auth-code steps, accept steps, the transfer page, typical days, "push supported"); twelve big registrars come filled in, everything else gets the generic text.
Settings -> Payments & Fees -> Transfers: the allowed methods, the hours the buyer has for the details, automatic registry checks on/off and their interval, completing the order on a verified change, the code view limit, the intro text.