---
id: TST-COM-FUL-039
title: Obligation holds
kind: integration
product_area: commerce
module: fulfillment
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: services-commerce
files:
  - modules/fulfillment/tests/integration/services/persistence/obligation-holds.integration.spec.js
implements:
  - ATS-COM-FUL-005-02
  - ATS-COM-FUL-005-05
  - ATS-COM-FUL-005-06
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  Run-created workspace identifiers and fixture records in the prepared test database; concurrency
  cases own their extra connections.
evidence:
  - repository: services-commerce
    path: >-
      modules/fulfillment/tests/integration/services/persistence/obligation-holds.integration.spec.js
    test_titles:
      - >-
        blocks a pending obligation with the hold, keeps a blocked one blocked with the hold over
        its reason, and refuses an authorized one
      - >-
        releases the hold (the reason and the evaluation time cleared, the state still blocked) and
        refuses a release of what is not held
      - >-
        holds the unpaid obligation with the log row, the history line and the audit event, then
        releases it and evaluates: unpaid, it stays blocked
      - >-
        releases the hold on the paid obligation and evaluates it at once: the gate opens, the
        authorization is queued and the dispatcher nudged
      - >-
        completes the in-flight obligation by hand with the evidence, closing its authorization, and
        refuses a pending one
    scenario_anchors:
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/persistence/obligation-holds.integration.spec.js#holds
        the unpaid obligation with the log row, the history line and the audit event, then releases
        it and evaluates: unpaid, it stays blocked
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/persistence/obligation-holds.integration.spec.js#blocks
        a pending obligation with the hold, keeps a blocked one blocked with the hold over its
        reason, and refuses an authorized one
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/persistence/obligation-holds.integration.spec.js#releases
        the hold (the reason and the evaluation time cleared, the state still blocked) and refuses a
        release of what is not held
      - >-
        services-commerce:modules/fulfillment/tests/integration/services/persistence/obligation-holds.integration.spec.js#completes
        the in-flight obligation by hand with the evidence, closing its authorization, and refuses a
        pending one
---

# Obligation holds

## Verification Boundary

This suite checks obligation holds against the prepared PostgreSQL database. Its entry points are the persistence and service functions used by the tests.

## What This Suite Proves

The bound scenarios identify the assertions this suite contributes. Source anchors retain the exact test cases; where a capability scenario has several contributing suites, a single binding does not imply that every branch runs here.

## What It Does Not Prove

Direct service and persistence calls do not establish the full HTTP permission contract, deployed scheduling or browser behavior. No execution result is claimed by this register.

## Real Dependencies and Test Doubles

The database and imported Commerce persistence services are real. Fixtures create the records owned by this run. Financial facts are supplied by a local fixture provider. Accounting command responses use the suite’s fixture port. Time-sensitive cases use a controlled clock where the source fixture supplies one.

## Must Not Be Doubled

Keep the database constraints, row visibility and persistence writes real when claiming this integration coverage. A canned repository response cannot replace the boundary being checked.