---
id: TST-ACC-TRX-127
title: Payment client side info 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/payment-client-side-info.integration.spec.js
implements:
  - ATS-ACC-TRX-007-11
implements_parts:
  - scenario: ATS-ACC-TRX-007-11
    assertion: >-
      it offers the bank account beside the card for mode both when the
      installation takes electronic checks
    provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/stripe/payment-client-side-info.integration.spec.js#it
      offers the bank account beside the card for mode both when the
      installation takes electronic checks
  - scenario: ATS-ACC-TRX-007-11
    assertion: >-
      it offers the card alone for mode both when the installation has
      electronic checks off: asked again once, no failure
    provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/stripe/payment-client-side-info.integration.spec.js#it
      offers the card alone for mode both when the installation has electronic
      checks off: asked again once, no failure
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/payment-client-side-info.integration.spec.js
evidence:
  - provenance: test
    source: >-
      services-accounting:modules/transactions/tests/integration/services/stripe/payment-client-side-info.integration.spec.js
    assertion_titles:
      - the payment client-side info for a merchant account (integration)
      - reads the merchant account back with its processor
      - >-
        mints a session on the account’s connection and answers Payrix’s mount
        information
      - >-
        offers the bank account beside the card for mode both when the
        installation takes electronic checks
      - >-
        offers the card alone for mode both when the installation has electronic
        checks off: asked again once, no failure
      - mints another session on each call
      - refuses a merchant account the tenant does not have (404)
    imports:
      - >-
        const { localIntegrationTransport, stubInvokeResult } =
        require('@rhythmsoftware/integration-client/local');
      - >-
        const { useIntegrationInvokeOptionsForTests } =
        require('../../../../services/payments/integrations-processor');
      - >-
        const { getPaymentElementInfo } =
        require('../../../../services/stripe/stripe-payment-element');
      - >-
        const { getMerchantAccount } =
        require('../../../../../books/services/persistence/merchant-accounts');
      - 'const { sql } = require(''drizzle-orm'');'
      - >-
        const { createPaymentWorld, expect, ownerQuery, fixedIn, ready,
        removeTenantPayments, testId } = require('../../payments-fixtures');
    test_double_declarations: []
---

# Payment client side info 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

Its cited assertions contribute evidence for bank entry follows processor capability. The structured assertion bindings identify which parts of combined scenarios it executes.

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