---
id: TST-PFM-OPS-106
title: Accept webhook delivery
kind: integration
product_area: platform
module: operations
revision: 1
status: draft
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
repository: services-platform
files:
  - modules/licensing/tests/integration/services/sync/accept-webhook-delivery.integration.spec.js
implements:
  - ATS-PFM-OPS-012-18
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
estimate_basis: Scheduling estimate only; no duration is measured during this documentation pass.
isolation: >-
  The prepared local test database and suite-owned identifiers; existing hooks control rollback or
  cleanup.
evidence:
  - >-
    services-platform:modules/licensing/tests/integration/services/sync/accept-webhook-delivery.integration.spec.js
    at ad3f6a6582843008ed0f5a17b131878d15829af1: existing suite body, setup, assertions and cleanup.
binding_note: This existing engineering suite is registered without claiming a complete specification scenario.
assertion_sources:
  - >-
    services-platform:modules/licensing/tests/integration/services/sync/accept-webhook-delivery.integration.spec.js#enqueues
    a sync of the company that contract belongs to
  - >-
    services-platform:modules/licensing/tests/integration/services/sync/accept-webhook-delivery.integration.spec.js#says
    the delivery was what asked for the sync, which is what an operator reads in a log
  - >-
    services-platform:modules/licensing/tests/integration/services/sync/accept-webhook-delivery.integration.spec.js#enqueues
    the company once for a batch about two of its contracts, because one read answers both
  - >-
    services-platform:modules/licensing/tests/integration/services/sync/accept-webhook-delivery.integration.spec.js#enqueues
    the company once for the same contract delivered twice, which HubSpot does on a retry
  - >-
    services-platform:modules/licensing/tests/integration/services/sync/accept-webhook-delivery.integration.spec.js#enqueues
    the company for a contract that was created, not only one that changed
  - >-
    services-platform:modules/licensing/tests/integration/services/sync/accept-webhook-delivery.integration.spec.js#enqueues
    the company for a contract that was deleted, because a deleted contract licenses nothing
  - >-
    services-platform:modules/licensing/tests/integration/services/sync/accept-webhook-delivery.integration.spec.js#enqueues
    the company for a delivery that names the generic object type, which a portal may send instead
  - >-
    services-platform:modules/licensing/tests/integration/services/sync/accept-webhook-delivery.integration.spec.js#ignores
    an event of a kind nothing subscribes to
---

# Accept webhook delivery

## Verification Boundary

This suite exercises application licensing through production operations against the local database. Its implementation is present at the pinned source revision, and this register records no execution result.

## What This Suite Proves

The checks resolve companies from the stored commercial copy, deduplicate their queued reads and report companies whose messages cannot be published. The scenario bindings name the attributed outcomes.

## What It Does Not Prove

Local execution does not establish deployed infrastructure, live commercial-provider configuration or authorization-cache completion. Registration and an implemented suite do not establish a passing result.

## Real Dependencies and Test Doubles

The prepared PostgreSQL database and production operations under test are real. Commercial-provider responses use the suite’s scripted inputs where declared. Queue publication uses a recording publisher.

## Must Not Be Doubled

The persistence operations, database constraints and reads under assertion remain real.