Integration Receipts

An inbound provider message has a provider, external event ID, receipt time, payload hash and processing status. Integration Operator uses those details to trace whether the external side accepted the requested work. A Failed or Rejected receipt remains visible for reconciliation.

An external event ID helps distinguish a repeated delivery from a new response. The receipt stores provider, receipt time, payload hash and processing status. It has no direct link to a DNS entry, so the operator must establish which publication request the message concerns before changing that entry.

• Ownership. Integration Operator investigates each provider response.
• Evidence. Check provider, event ID, receipt time, hash and processing status.
• Follow-through. Match the message to the relevant outside work before changing a DNS entry.

Agree the provider identity and how an external event ID is matched to the request. Keep a single message trace for repeated deliveries and review unexpected payloads before changing the DNS record or service change state.

Rehearse an ordinary record and an exception with the people who will use this area. Check the linked owner or service before changing a status. If the outside information changes, compare it with the original request before the next handoff.

Use an approved DNS entry with a publication request. Find the corresponding provider receipt, compare its event identity and outcome, and only then review the DNS entry for Published. Investigate a Failed receipt without declaring publication.

Have the receiving operator repeat the check using the linked records. Review a mismatched owner, value or date with the decision owner before applying the same handling to more work.

For an exception, use two receipts with the same external event ID. The Integration Operator should compare provider, receipt time, payload hash and status before deciding whether the second message repeats an earlier response. A Received receipt means the message arrived; it is not proof that the DNS provider published the requested value. A Failed or Rejected receipt needs investigation before anyone changes the DNS entry. Keep the approved domain, host and value available during reconciliation because the receipt has no direct record link. If the message cannot be matched, leave the DNS entry at its prior status.

• Provider receipt exceptions — Failed and rejected inbound messages needing investigation.
• Recent provider receipts — Received or applied messages with their provider and event ID.

Follow the provider acknowledgment handoff and review the data model before migrating records.