NGateway Domain Transfer Wizard
Inbound transfer flow. CORE Payload 2.0 uses domain.transfer.request to start a transfer; the poll queue is read with poll.request and cleared with poll.acknowledge (there is no poll.queue command in the bundled spec).
Sequence: domain.check → optional domain.authinfo.request (code for domains on your member) or skip and paste code from the losing registrar → domain.inquire + auth → contacts → domain.transfer.request → poll.
Step 1 — domain.check
Retrieve availability / transfer-related pricing hints for the name at this registry.
Step 2 — domain.authinfo.request (optional)
If this domain is sponsored by your CORE member, the gateway can return the current transfer code (domain.authinfo in the response). If the name is still at another registrar, obtain the code from them and use Skip below, then paste it in step 3.
Step 3 — domain.inquire + domain.authinfo
Validates the auth code for many registries and returns contact.N.id / contact.N.type for mapping.
Authinfo is kept in memory for this session only (not saved with “Reset” persistence).
Step 4 — contact.inquire
Loads each distinct losing-registrar contact handle from step 3. Responses appear in the progress panel.
Step 5 — Gaining contacts (contact.create)
For each role from domain.inquire, enter the new gaining-registrar contact ID (3–16 chars), or create one below and paste the returned ID into the row.
| # | Type | Source ID | Gaining contact ID |
|---|
Create gaining contact (applies to selected row)
Step 6 — domain.transfer.request
Submits the inbound transfer using gaining contact IDs from step 5, the same authinfo, and optional NS / update / period fields.
Step 7 — Poll queue
Use poll.request to dequeue messages; acknowledge with poll.acknowledge using msg.id. Watch msg.type (e.g. transfer-related notices) and any domain fields in the response.
Response / Progress
{}