01must proveProposed | Processor tenders require an active merchant account in the payment’s unit and currency; hosted processor fields collect the instrument, and Accounting does not retain its token. | validation | api, service | test |
02must proveProposed | Financial eligibility and planned allocations are checked before the charge call, preventing rejected input from reaching the processor. | validation | service | test |
03must proveConfirmed | An intent is committed before charging, and its identity limits the attempt to one charge and one recorded payment. | invariant | service, database | test |
04must proveProposed | A definite decline or unreachable charge fails the intent and releases the request key for another attempt without recording collected money. | lifecycle | service | test |
05must proveProposed | Captured money is always recorded, allocations shrink to the lines’ current balances, and excess remains unapplied. | policy | service | test |
06must proveProposed | An uncertain processor response leaves the intent processing, and retrying the request performs a lookup instead of another charge. | lifecycle | service | test |
07must proveProposed | Scheduled lookups follow the environment cadence and require a definite answer; exhausted unresolved lookups raise an attention item for human review. | lifecycle | service | test |
08must proveProposed | Human resolution requires an unresolved attempt already in review and either records failure or creates the payment once using the confirmed processor reference. | permission | api, service | test |
09must proveProposed | An intent whose processor cannot be queried is abandoned after twenty-four hours and logged as an error. | lifecycle | service | test |
10must proveProposed | Electronic checks remain pending until clearing is confirmed, then succeed; a returned debit creates an ACH-return reversal. | lifecycle | service | test |
11must proveProposed | Only Rhythm staff can use the system route to mark an electronic check settled; customer administrators are refused. | permission | api | test |
12must proveProposed | The processor’s electronic-check capability controls whether bank-account entry appears beside card entry, and electronic checks are eligible wherever cards are. | policy | service | test |
13must proveProposed | Card captures create reconciliation items immediately, while bank-debit captures become eligible when clearing completes. | invariant | service | test |
14Proposed | Production processor work uses the Integration Platform gateway; the superseded Stripe options and webhook remain exposed and report missing configuration where keys are absent. | policy | service | documented |