---
id: TST-COM-ORD-136
title: The void refund legs
kind: unit
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
repository: services-commerce
files:
  - modules/orders/tests/unit/orders/void-refund.spec.js
implements:
  - ATS-COM-ORD-008-06
environment: mock
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 1
isolation: 'The suite owns its in-memory inputs, scripted responses and rendered component state.'
evidence:
  - provenance: test
    source: 'services-commerce:modules/orders/tests/unit/orders/void-refund.spec.js'
    test_cases:
      - >-
        returns a store-credit settlement by the memo and a card leg by a refund of its payment, in tender
        order
      - 'counts no declined, uncertain, pending or terms leg as captured'
      - >-
        splits a settlement whose card took the rest by the payment’s total: the credit part by the memo, the
        card part refunded
      - 'leaves the mixed settlement unresolved when the payment’s total is not known, planning nothing of it'
      - 'credits every billed line at what it carries, its tax included, and skips a line not billed'
      - plans nothing for an order with no captured leg
      - 'plans a refund of each payment leg first, then the memo of the sale invoice, under the void’s keys'
      - keys a void’s steps as the order’s and every other document’s as its own
      - plans nothing for an order nothing was paid on
      - refunds the paid part of a part-paid order before the memo of its line is cut
      - refunds a fully paid order in full before the memo
      - 'plans a store-credit part by the memo alone, and the card part refunded before it'
      - plans the refund of a settlement’s card part before the memo that returns its credit part
scenario_coverage:
  - scenario: ATS-COM-ORD-008-06
    test_cases:
      - refunds the paid part of a part-paid order before the memo of its line is cut
      - 'plans a store-credit part by the memo alone, and the card part refunded before it'
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
dependency_evidence:
  provenance: test
  source: 'services-commerce:modules/orders/tests/unit/orders/void-refund.spec.js'
  declared_by_test: 'the leg computation, the plan input, the planner. Doubled: nothing.'
---

# The void refund legs

## Verification Boundary

The unit suite checks the named contract or helper with controlled inputs.

## What This Suite Proves

The registered cases check the void refund legs with their fixture records and assertions. Scenario bindings name only the examples those cases exercise.

## What It Does Not Prove

A registered file supplies no run result or verified conformance by itself. Local fixtures do not establish deployed cross-service behavior or complete browser journeys.

## Real Dependencies and Test Doubles

Inputs and external responses are controlled in process; this suite establishes no deployed service behavior.

## Must Not Be Doubled

The named contract validation or component behavior under assertion must use its actual implementation.