---
id: TST-ACC-TRX-097
title: Payments queries suite
kind: integration
product_area: accounting
module: transactions
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - >-
    modules/transactions/tests/integration/services/persistence/payments.queries.integration.spec.js
implements: []
implements_parts: []
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  Suite-marked records in the prepared local test database; fixture teardown
  removes owned records.
provenance: test
source: >-
  services-accounting:modules/transactions/tests/integration/services/persistence/payments.queries.integration.spec.js
evidence:
  - provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/persistence/payments.queries.integration.spec.js
    assertion_titles:
      - payment queries (integration)
      - loadPayment
      - >-
        answers the voided check’s header and its two allocation rows (the
        original and its reversal), every column as stored
      - answers the card’s processor columns
      - 'answers nothing for an absent id, and for another tenant’s payment'
      - listPayments
      - >-
        answers the tenant’s payments newest first, a page of two with the
        keyset of the next
      - >-
        filters by status, by payment method, by behaviour, by customer and by
        date
      - answers nothing of another tenant
      - listUnappliedPaymentsOf
      - >-
        answers Ada’s payments with money still unapplied, oldest first: the
        January check (1000) and today’s card (1500), not the voided one
      - listAllocationsOfInvoice
      - >-
        answers the invoice’s allocation rows across its payments, in payment
        then position order
      - the intents
      - 'answers an intent by id and by key, and nothing for another tenant’s'
      - >-
        lists the intents left processing and claimed before an instant, oldest
        first
    imports:
      - 'const { stage } = require(''@rhythmsoftware/macroservice-testing/stage'');'
      - >-
        const { TEST_NOW } =
        require('@rhythmsoftware/macroservice-testing/execution-context');
      - >-
        const { toUtcTimestamp } =
        require('@rhythmsoftware/macroservice-time/zoned-time');
      - >-
        const { voidPayment } =
        require('../../../../services/payments/payment-allocate');
      - >-
        const { receivePayment } =
        require('../../../../services/payments/payment-receive');
      - '} = require(''../../../../services/persistence/payment-intents'');'
      - '} = require(''../../../../services/persistence/payments'');'
      - '} = require(''../../payments-fixtures'');'
      - "\t\t\tconst { invoice, voided } = world.require();"
      - "\t\t\tconst { card } = world.require();"
      - "\t\t\tconst { foreign } = world.require();"
      - "\t\t\tconst { card, check, voided } = world.require();"
      - "\t\t\tconst { card, check, voided } = world.require();"
      - "\t\t\tconst { foreign } = world.require();"
      - "\t\t\tconst { card, check } = world.require();"
      - "\t\t\tconst { invoice, voided, check } = world.require();"
      - "\t\t\tconst { card, lost } = world.require();"
      - "\t\t\tconst { lost } = world.require();"
    test_double_declarations: []
---

# Payments queries suite

## Verification Boundary

The suite exercises transaction commands and database protections in the local prepared test environment. Registration records the existing executable file; it does not report a run or establish product approval.

## What This Suite Proves

The executable assertions exercise this module, but no capability or feature scenario binding is established for this file. Its individual assertion titles remain in the evidence register for subsequent mapping.

## What It Does Not Prove

Local commands and route invocations do not establish deployed routing, live processor guarantees or the complete staff browser experience. An unbound feature chain remains proposed, and this registration carries no execution result.

## Real Dependencies and Test Doubles

The suite uses the imported commands, route handlers or persistence code against the local test database. Fixture helpers supply accounting context; any stepped clock, dummy processor or substituted external client is retained in the evidence declarations.

## Must Not Be Doubled

The command or persistence behavior under assertion and its relevant database protections must remain real. Substituting the final financial result removes evidence of transactional effects.