---
id: ADR-ACC-TRX-005
title: Committed Attempts Around External Payment Calls
product_area: accounting
module: transactions
revision: 1
status: proposed
design_intent: confirmed
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
decision: >-
  Electronic collection and return commit an attempt before the external call
  and conditionally record its outcome afterward, with scheduled lookup and
  human review for uncertain outcomes.
constrains:
  - DOM-ACC-TRX-003
  - STATE-ACC-TRX-005
  - STATE-ACC-TRX-010
  - STATE-ACC-TRX-007
  - WF-ACC-TRX-006
  - WF-ACC-TRX-007
  - WF-ACC-TRX-009
  - SVC-ACC-TRX-transactions
origin: >-
  Andrew’s D-01 (payment intents) and the kept decision on refunds and voids in
  three steps with a sweep:
  services-accounting:docs/architecture/accounting-2.0/02-decisions.md#1. The
  assessment's decisions, D-01 to D-07 (Andrew, 2026-10-17)
alternatives:
  - option: Hold the database transaction open during provider work.
    why_not: >-
      External collection could survive a local rollback, and network latency
      would prolong financial locks.
  - option: Conclude failure immediately from an empty recovery lookup.
    why_not: >-
      A delayed provider result could make that conclusion unsafe; the
      implementation nevertheless treats expired reference absence differently
      from key lookup.
consequences:
  - >-
    Committed attempt identity and provider deduplication support recovery
    without another collection request.
  - >-
    An uncertain operation can retain processing and financial reservations
    until recovery completes.
  - >-
    Exhausted scheduled key lookup raises attention for staff; charge-reference
    absence and day-old abandonment have separate implemented outcomes.
supersedes: []
evidence:
  - >-
    services-accounting at f47cb263:
    docs/architecture/accounting-2.0/02-decisions.md, 05-lifecycles.md,
    06-integrity-model.md.
---
# Committed Attempts Around External Payment Calls

## Context

An external payment result can be lost after the provider acted. The design records the local attempt first and identifies each actual recovery path rather than promising infallible outcome recovery.

## Decision

The structured decision records the governing boundary and its observed limits. Its origin distinguishes Andrew’s rulings from reversible implementation choices and proposed publication policy.

## Alternatives Considered

The listed alternatives explain the competing responsibility or recovery approaches and why the recorded direction differs. They are explanatory comparisons, without evidence of a separate approval discussion for each alternative.

## Consequences

The consequence rows identify implementation obligations, current departures and gaps requiring further verification. Artifact status remains proposed until Andrew approves it.