---
id: TST-ACC-TRX-129
title: Stripe webhooks 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/stripe/stripe-webhooks.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/stripe/stripe-webhooks.integration.spec.js
evidence:
  - provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/stripe/stripe-webhooks.integration.spec.js
    assertion_titles:
      - the Stripe webhook (integration)
      - what is ignored or not found
      - 'ignores a body with no event id, without asking Stripe'
      - answers not_found for an event Stripe does not hold
      - >-
        ignores an event whose object carries no Rhythm tenant, and one naming a
        tenant not known here
      - charge.refunded
      - >-
        finishes the processing refund from the charge’s refund that carries its
        id, and a second delivery applies nothing
      - the clearing of electronic checks
      - settles the one payment_intent.succeeded names
      - >-
        returns the one payment_intent.payment_failed names, with the bank’s
        reason
      - disputes
      - >-
        opens a chargeback from charge.dispute.created, reading the tenant
        through the PaymentIntent, once
      - 'closes it lost from charge.dispute.closed: the payment charged back'
    imports:
      - 'const { stage } = require(''@rhythmsoftware/macroservice-testing/stage'');'
      - >-
        const { receivePayment } =
        require('../../../../services/payments/payment-receive');
      - >-
        const { executeRefund, requestRefund } =
        require('../../../../services/refunds/refund-commands');
      - >-
        const { useStripeClientForTests } =
        require('../../../../services/stripe/stripe-client');
      - >-
        const { receiveStripeWebhook } =
        require('../../../../services/stripe/stripe-webhooks');
      - '} = require(''../../payments-fixtures'');'
      - "\t\t\tworld.require();"
      - "\t\t\tworld.require();"
      - "\t\t\tworld.require();"
      - "\t\t\tconst { payment, requested, refusal } = lost.require();"
      - "\t\t\tconst { clears } = pending.require();"
      - "\t\t\tconst { returns } = pending.require();"
      - "\t\t\tconst { payment } = disputed.require();"
      - "\t\t\tconst { payment } = disputed.require();"
    test_double_declarations: []
---

# Stripe webhooks 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.