---
id: TST-COM-ORD-017
title: Order 360's payment actions
kind: unit
product_area: commerce
module: orders
revision: 1
status: draft
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
repository: react-console
files:
  - components/console/order/__tests__/order-360-live-cards.test.tsx
implements:
  - ATS-COM-ORD-007-13
  - ATS-COM-ORD-008-11
  - ATS-COM-ORD-010-07
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: 'react-console:components/console/order/__tests__/order-360-live-cards.test.tsx'
    test_cases:
      - shows Take Payment and Void Order on an unpaid pay-now order inside its window
      - 'shows neither once the tender window has passed, except Void Order'
      - >-
        shows Receive Payment as a link to Accounting's Settle Invoices with the invoice selected, and no Take
        Payment
      - shows none of them on a paid order
      - shows none of them to someone without the permissions
      - shows none of them on a sample order
      - 'shows the totals with the promotion''s name, the money, and the invoice as a link to Accounting'
      - says Accounting has not reported when the order has no money mirror yet
      - renders nothing for a sample order
      - 'shows a line''s discount reason, tax and the reason its delivery failed'
      - 'lists each tender with its status, the declined one struck through and a payment linked to Accounting'
      - shows a payment the processor has not confirmed as pending at the processor
scenario_coverage:
  - scenario: ATS-COM-ORD-007-13
    test_cases:
      - shows Take Payment and Void Order on an unpaid pay-now order inside its window
      - >-
        shows Receive Payment as a link to Accounting's Settle Invoices with the invoice selected, and no Take
        Payment
      - shows none of them on a paid order
      - shows none of them to someone without the permissions
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
  - scenario: ATS-COM-ORD-008-11
    test_cases:
      - 'shows neither once the tender window has passed, except Void Order'
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
  - scenario: ATS-COM-ORD-010-07
    test_cases:
      - 'shows the totals with the promotion''s name, the money, and the invoice as a link to Accounting'
      - says Accounting has not reported when the order has no money mirror yet
      - 'shows a line''s discount reason, tax and the reason its delivery failed'
      - 'lists each tender with its status, the declined one struck through and a payment linked to Accounting'
      - shows a payment the processor has not confirmed as pending at the processor
    scope: >-
      The cited cases exercise the scenario’s listed fixture outcomes; this register makes no verified
      conformance claim.
---

# Order 360's payment actions

## Verification Boundary

The component suite renders the named screen with controlled adapter results.

## What This Suite Proves

The registered cases check order 360's payment actions 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.