1. Identify the supported provider adapter and the transaction reference already associated with the domain operation.
2. Receive and verify the provider's event through your authorised upstream integration. Preserve its original event identity and environment.
3. POST the expected provider, environment and provider-format payload using an identity with the required sync scope.
4. Store the returned event and projection result. If the event needs a later reconciliation, POST the provider name and provider_reference to the reconcile resource.
5. Read the related domain and operation to confirm the resulting state, and retain the request references for support.

No. It projects recorded provider evidence into the existing lifecycle. Do not substitute a new registration or renewal when the real task is to reconcile the original transaction's outcome.

No. The payload must match the supported provider adapter's contract. The wrapper fields alone do not make arbitrary JSON valid evidence. If the provider or event shape is unsupported, use the existing domain sync and authorised support workflow rather than fabricating a success event.

The tenant checks still apply. A reference belonging to another reseller must not be imported into your account simply because it appears in an upstream log. Production and test environments also need to remain distinct.

Retain provider event identity and HTTP idempotency consistently in your receiver, and inspect the stored event result. Repeated delivery should not become repeated paid work. For conflicting events, preserve both the provider evidence and current operation state so the supported reconciliation logic or an administrator can review the discrepancy.

• Follow a domain operation through pending, failed and manual-review states
• Receive and verify Domain Nexus webhook deliveries
• Synchronize a domain's current provider state through the v2 API
• Retry Domain Nexus requests without creating duplicate domain operations