Observe or enforce one ERP vendor payment against the tenant's payment checks

Deprecated alias of POST /v1/connections/{connectionId}/executions: the same handler, which answers this payment contract unchanged for the installed Business Central extension 1.0.2.3. The Payment Release Guard. A native ERP shell states one vendor payment it is releasing and the facts it holds; Commerce Gate asks Decionis to evaluate it as a commerce-preflight-v2 PAYMENT_RELEASE with the caller's own organization key and answers the tenant's policy for P12 payment release authority, P13 duplicate invoice, P14 beneficiary change window and P15 liquidity floor. In OBSERVE mode the shell asks after posting, Decionis records a Shadow decision and enforced is false: nothing is blocked. In ENFORCE mode the shell asks before posting, Decionis records an enforced decision, enforced is true, and the shell stops the posting on HOLD or BLOCK; an enforced request states no posted entry (400 PAYMENT_ENFORCE_AFTER_POSTING). Commerce Gate only answers: nothing here initiates, holds, routes or settles a payment. Account numbers never cross this boundary; the beneficiary facts carry only when the vendor's bank account last changed and whether that change was verified. Business Central requires the full native_context captured from the context endpoint. Core rechecks the current workspace key, connection and native read grant; every organization, workspace environment, tenant, company, environment name and revision assertion must match. Registration metadata does not independently verify the native shell's payment facts or authorize posting. The resolved metadata and its evidence boundary remain in the saved evidence and response. Exact OBSERVE retries return the saved receipt; ENFORCE retries recheck the original upstream decision without replacing it. A separate after-post OBSERVE result does not change an earlier ENFORCE decision. F&SCM retains its existing credential/tenant binding and does not accept native_context. A 502 means Decionis did not return a bound evaluation in the requested mode, and a 503 PAYMENT_ENFORCEMENT_DISABLED means enforcement is switched off centrally; an observing shell retries and an enforcing shell applies its own fallback mode. This is an unreleased source candidate that needs the matching backend and a tenant policy whose allowed sources include the ERP's source name.