The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | invokeIntegrationCapability | Send a payment authorization from Accounting whose response disappears after dispatch. | CAP-PFM-INT-009 | Accounting receives an unknown outcome and the original payment is not dispatched again. | test services-platform:modules/integrations/tests/e2e-adapters/gateway-dummy.adapters.spec.js#answers the invoke client unknown, never a retry |
| 2 | /console/{tenantId}/configuration/platform/integrations/activity/{executionId} | Inspect the payment call. | CAP-PFM-INT-010 | The detail shows settlement in progress and the next planned lookup. | test react-console:lib/integrations/settling.test.ts#says when Rhythm checks again, as a time |
| 3 | platform.integrations.executions.reconcile | Query the provider for the original payment. | CAP-PFM-INT-010 | A conclusive result settles the call and produces one completion for Accounting. | test services-platform:modules/integrations/tests/integration/services/executions/reconciler.integration.spec.js#settles a found operation succeeded, with the provider’s answer as the stored response |
| 4 | /console/{tenantId}/configuration/platform/integrations/needs-attention | If lookup remains inconclusive, resolve the payment with an operator note. | CAP-PFM-INT-011 | The final record identifies the operator and creates one completion for Accounting. | test services-platform:modules/integrations/tests/integration/services/executions/execution-settlement.integration.spec.js#resolve of a sync execution the caller was never answered for writes exactly one completion |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 3 | Five provider lookups remain inconclusive | Escalate the payment and send administrators one notice | An operator determines the outcome through the manual branch | test services-platform:modules/integrations/tests/integration/services/executions/reconciler.integration.spec.js#sends the execution to needs_attention after the fifth lookup that cannot tell, with one notice to the administrators |
| failure | 3 | The provider reports no matching payment | Continue lookup and escalate after the last attempt | Do not infer a failed payment solely from absence | test services-platform:modules/integrations/tests/integration/services/executions/reconciler.integration.spec.js#sends a payment to needs_attention at the last lookup, with one notice, never failing it |
| Id | Statement | Provenance |
|---|---|---|
01 | Unknown payment outcomes use lookup rather than a second payment dispatch. | test |
02 | Manual settlement writes one completion for the calling application. | test services-platform:modules/integrations/tests/integration/services/executions/execution-settlement.integration.spec.js#resolve of a sync execution the caller was never answered for writes exactly one completion |
End-to-end policy: optional: Browser evidence covers settlement displays; service tests with a controlled clock establish the delayed lookup sequence.