Card authorization-backed budgets

The card rail funds a budget with one manual-capture authorization: the buyer's card is authorized once, for the cap, and that authorization IS the funded ceiling. Dynamo never holds card balances and never stores value; the hold is the budget. When a hold must be renewed, the rail re-authorizes the same payment method for at most the remaining ceiling, never more.

The platform model

Dynamo runs the PSP platform pattern (Stripe in this repository, TEST mode only):

for the cap on the buyer's payment method. Payment method tokens only - no card numbers ever touch the system.

authorization - never more than signed vouchers bill, never beyond the ceiling.

transfers split captured funds per voucher totals. Every Dynamo application fee is its own explicit, ledger-auditable row tied to the settlement that produced it.

released back to the buyer's card - the mirror of escrow release.

refunded units reversed and netted against the payee (holdback & refunds).

Status: Live in Stripe TEST mode; live card money is Release-gated and off in this release. The switch and its safeguards are described in TEST mode and the live-ready switch.

Fail closed, in card terms

the last funded voucher. The budget is marked ceiling-dead with the decline code, and every stream that depends on it is revoked with the emergency-stop semantics: settled first, and never held for a task claim still in its acceptance window. The single closing capture is made only once every root is revoked; a stream that cannot be revoked or settled yet is named in an alert and the capture waits, retried by the scheduler inside the hold's last 24 hours. Nothing accrues beyond the funded ceiling. make demo-card-decline runs the full sequence.

never a silent over-capture, never a retry against a bigger hold the buyer didn't approve.

Why "authorization-backed", precisely

The phrase is chosen for accuracy. Card networks have a specific meaning for escrow, and this is not that: the buyer's bank holds the authorization, the network's rules govern it, and Dynamo's engine decides only how much of it signed vouchers justify capturing. What the protocol adds is the enforcement graph - caps, envelopes, revocation, voucher-gated captures - on top of a hold the cardholder already understands.

Reconciliation

Card sessions end with the engine==PSP table: every intent, capture, transfer, refund, and release the engine believes happened, matched against the PSP's own records, to the cent. make demo-card prints it; make demo-evidence exports it as an offline-verifiable evidence bundle with the PSP references embedded.