When you submit an inbound transfer, save its local order reference, operation identifier and any returned domain identifier. An accepted response can remain pending while the registry or losing registrar processes the transfer.

1. Read GET /v2/operations/{operationId} for the original transfer operation.
2. When the domain resource is available, resolve its identifier from your account's inventory.
3. Send GET /v2/domains/DOMAIN_ID/transfer with domains:read.
4. Inspect the actual transfer status and any available provider or verification information.

If the provider should have completed the transfer but the stored state is old, use POST /v2/domains/DOMAIN_ID/sync with domains:sync and an idempotency key. Wait for that operation before rereading transfer and domain details.

Routine connectors should continue their normal domain synchronization. Avoid many simultaneous polling loops for the same domain; follow returned polling guidance and your rate limits.

A pending transfer may need time or an external verification step. If the current contract offers verification resend and the provider supports it, use that specific action after checking the recipient and previous request.

A failed state needs the actual reason, such as an authorisation-code issue, lock or registry refusal. Do not start another transfer merely because your local screen is old. Reconcile the original operation and financial state before a new business request.

Mark the customer's transfer complete only after the provider-confirmed state supports it. Read the final domain status and expiry, then check that the desired nameserver and DNSSEC arrangement remains valid.

Your invoice status, the transfer operation and public website availability are separate evidence. A website can work throughout a pending transfer, and a completed registrar transfer can coexist with an unrelated DNS error.

For support, include the domain, original operation, last synchronization time and redacted transfer state. Keep the EPP code out of routine diagnostics.

• Submit an inbound domain transfer with the Domain Nexus v2 API
• Synchronize a domain's current provider state through the v2 API
• Read Domain Nexus API errors and trace an uncertain request
• Retry Domain Nexus requests without creating duplicate domain operations