The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.
| # | Surface | Action | Capability | Expected | Provenance |
|---|---|---|---|---|---|
| 1 | /console/{tenantId}/configuration/platform/integrations/bindings | Choose Main account for workspace payments and a second account for one business unit. | CAP-PFM-INT-007 | Both new bindings are active at their initial revision. | test services-platform:modules/integrations/tests/e2e/integration-bindings.e2e.spec.js#answers the business unit binding the id its scope and revision give |
| 2 | /console/{tenantId}/configuration/platform/integrations/bindings | Explain payment routing for that business unit. | CAP-PFM-INT-008 | The explanation selects the business unit account and lists the eligibility checks. | test |
| 3 | /console/{tenantId}/configuration/platform/integrations/{integrationKey}/connections/{connectionId} | Use the account’s test panel to authorize a sample amount. | CAP-PFM-INT-012 | The panel displays the gateway response and its call reference. | test |
| 4 | /console/{tenantId}/configuration/platform/integrations/activity/{executionId} | Find the test in Activity and inspect its details. | CAP-PFM-INT-011 | The record identifies the account, attempts, outcome and administrator who initiated the test. | observed |
| Path | From step | Condition | Path taken | Outcome | Provenance |
|---|---|---|---|---|---|
| alternate | 3 | The response disappears after the test request leaves Rhythm | Enter settlement and query the provider | A conclusive provider response settles the call | test |
| failure | 2 | The most specific account is ineligible for payments | Explain the failed eligibility check and reject routing | Do not substitute the broader workspace account | test services-platform:modules/integrations/tests/unit/services/binding-resolution.spec.ts#stops at the first ineligible binding with binding_ineligible, never reaching the broader scope |
| Id | Statement | Provenance |
|---|---|---|
01 | The most specific binding determines routing, and Explain exposes that choice. | test |
02 | Direct tests record the account and initiating person under the test application, without a binding. | test services-platform:modules/integrations/tests/e2e/connection-try.e2e.spec.js#records an execution of that connection by the calling application library_try on behalf of the person, with no binding |
End-to-end policy: required: The required browser walk joins routing configuration, explanation, direct testing and call inspection across their separate pages.