CTR-BANK-GATEWAY · version 1

Bank Connectivity Gateway — Payment instructions

Blocked pending a bank security review that has not been scheduled. more

DraftNever checked

What the contract says

These are the terms the connector is generated against. more

Entity

Payment instruction · bidirectional

Primary key

endToEndId

Declared volume

0 records a day

Freshness commitment

1 h

Owner

L. Duarte · Treasury Operations

Vendor

SWIFT and host-to-host channels · critical criticality · not-connected

Cardinality

One instruction to exactly one payment. Batching happens at the gateway and the platform never sees the batch.

Write-back rule

Explicitly none, and the contract says the exclusion is permanent under this version. Payment initiation by an agent is not a capability this platform is asking for.

Review state

Neither review is performed by the team that wrote the contract.

Security reviewNot started

No reviewer has been assigned.

Privacy reviewNot started

No reviewer has been assigned.

Validation and drift

Drift is only detectable on a contract that has been read against a sample.

Last validatedNever

No sample has been read against this contract.

The only contract on the estate for a system that is not connected at all. more

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.

Staging boundary

Replay windows

No replay has been requested against this contract.

Replay register

Write-back routes into this system

1 route designed against Bank Connectivity Gateway.

Write-back register

release-payment-file · Payment instructionBlocked

WB-BANK-01 · human-confirmed · authority FI6-AUTH-H1 · policy FI6-POL-200

1 attempted · 0 written to a production system

What goes stale when this feed does

3 asserted figures depend on Bank Connectivity Gateway. more

Freshness

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. more
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. more

What this contract is, and what it is not

A contract, a validation rule, a freshness commitment and a replay path are real mechanisms and they are what this wave builds. more

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.