CTR-BANK-GATEWAY · version 1
Bank Connectivity Gateway — Payment instructions
Blocked pending a bank security review that has not been scheduled. Recorded here so the gap is visible rather than absent.
What the contract says
These are the terms the connector is generated against. A source that stops matching them is a drift finding, not a silent data change.
Review state
Neither review is performed by the team that wrote the contract.
Validation and drift
Drift is only detectable on a contract that has been read against a sample.
The field list
4 fields · 1 key · 1 personal. The validation rule on each row is what admits or rejects a record at the staging boundary.
| Field | Source | Target | Type | Flags | Drift | Validation |
|---|---|---|---|---|---|---|
| End-to-end id | EndToEndId | payment.ref | string(35) | keyinternal | Never checked | ISO 20022 field. Unique per instruction. |
| Amount | InstdAmt | payment.amount | decimal(18,2) | internal | Never checked | Positive. |
| Creditor account | CdtrAcct.Id.IBAN | payment.creditorHash | string(64) | personalrestricted | Never checked | Hashed at the boundary. The clear IBAN never enters the platform. |
| Status reason | StsRsnInf | payment.statusReason | string(80) | nullableinternal | Never checked | Populated on rejection only. |
What has passed the staging boundary against this contract
No batch has been presented against this contract in the recorded window.
Replay windows
No replay has been requested against this contract.
Write-back routes into this system
1 route designed against Bank Connectivity Gateway.
What goes stale when this feed does
3 asserted figures depend on Bank Connectivity Gateway. The rule on each row is what the surface does when the feed misses its commitment.
| Figure | Where it is shown | Role | On stale | Note |
|---|---|---|---|---|
| Supplier invoice value cleared | Reconciliation ledger REC-01 | contributing | Suppress the figure | Settlement confirmation comes from the bank channel, which is not connected. This dependency is the reason the ledger cannot close on payment rather than on posting. |
| Reconciliation breaks open | Reconciliation ledger | contributing | Suppress the figure | Two ledgers cannot be computed at all without the bank channel and are shown as not-computed rather than as zero breaks. |
| Group cash position | Finance cockpit | primary | Suppress the figure | Intraday balances come from the bank channel, which is not connected. This is why the position is labeled modeled and not measured. |
A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. What they are not is a connection. No connector on this estate is attached to a customer instance, so every batch, every replay and every write-back attempt recorded here ran against a modeled extract or a sandbox, and the registry keeps saying modeled.
This contract has never been validated against a sample. Every type, every cardinality statement and every validation rule on this page is a declaration taken from documentation, not an observation. Its drift state is unknown rather than clean.