Capture a high-value wire

Simulated wire

Capture the full instruction — debit account, beneficiary name and address, beneficiary account and routing identifiers, correspondent and intermediary bank fields, purpose of payment, charges handling and remittance information. Required fields differ by instruction type and are named individually below. Capturing posts nothing: the wire waits for a second, different staff user with release authority.

Disclosure

SIMULATED high-value settlement — this module's own settlement engine, not a real wire network

High-value wire instructions in this module settle through an INTERNAL SIMULATION, not through a real wire network. There is no SWIFT, Fedwire, CHAPS or TARGET2 connection, no correspondent or intermediary bank is contacted, no MT103 or pacs.008 message is produced or transmitted, and nothing recorded here has any effect outside this database. The correspondent, intermediary and routing fields captured on a wire are held as instruction data and screened against the seeded sample sanctions watchlist; they are never used to address anybody. On approval the wire posts as a balanced pair — debiting the ordering customer and crediting an internal scheme-settlement suspense account — and is marked pending settlement until the configured settlement lag elapses, at which point the same deterministic settlement job moves the suspense balance to the internal scheme-clearing position and the payment becomes settled. Every wire record stores the adapter identifier and a simulated flag so a stored record can never be mistaken for real wire traffic.

What dual control enforces here

The MAKER captures the wire with its full detail set — debit account, beneficiary name and address, beneficiary account and routing identifiers, correspondent/intermediary bank fields, purpose of payment, charges handling and free-text remittance information. Required fields are enforced per instruction type.
The captured wire is put through exactly the same pre-release validation gate as every other payment (positive whole-cent amount, account state, available funds, per-customer limits, payee state) and screened against the seeded sample sanctions watchlist. Nothing posts at capture: the wire is recorded as awaiting approval.
A SECOND, DIFFERENT staff user with release authority reviews the full instruction, the validation result and the screening result, and either approves or rejects it. Both decisions need a mandatory note and are recorded with the acting user and the moment.
The capturing user can never approve their own wire. An attempt is refused with a clear message and the refused attempt is itself recorded on the wire's decision trail.
On approval the wire posts a balanced debit/credit pair and moves to pending settlement; the scheduled settlement job settles it after the configured lag, through the same SIMULATED adapter and disclosed the same way. A rejected wire is terminal and posts nothing, ever.

adapter: internal-simulated-wire.v1 · simulated: true · no wire-network connection exists

Instruction

Wire reference (idempotency key) *

One reference is one wire, forever. Re-submitting the same reference returns the original instruction and captures nothing again.

Instruction type *

Settled in the same currency and jurisdiction. A national routing code identifies the beneficiary bank; no correspondent leg is required.

Account to debit *

Amount (USD) *

Enter the amount to send.

Capturing staff user (the maker) *

This user cannot approve the wire they capture, whatever their role. Release authority rests with Daniel Silva, Sola Adeyemi.

Beneficiary

Beneficiary name *

Beneficiary account / IBAN *

Beneficiary address *

A high-value instruction with no beneficiary address cannot be screened or evidenced.

Beneficiary routing code *

Required on a domestic wire: without it the instruction names no route.

Beneficiary bank name

Beneficiary bank BIC

8 or 11 characters. Required on a cross-border wire.

Beneficiary country (ISO-2)

Screened against the jurisdiction records on the seeded sample watchlist.

Correspondent / intermediary bank

Held as instruction data and screened. Nothing is transmitted to any of these institutions — no correspondent bank is contacted at any point.

Correspondent bank name

Correspondent bank BIC

Correspondent account

Correspondent country (ISO-2)

Intermediary bank name

Intermediary bank BIC

Purpose, charges and remittance

Purpose-of-payment code *

For example SALA (salary), SUPP (supplier), INTC (intra-company), TRAD (trade).

Charges handling *

Purpose of payment (in words) *

The approver reads this, not the code.

Remittance information *

Free text that would reach the beneficiary, and which the approver reviews.

Capturing posts nothing. The wire is recorded as awaiting approval and needs a second, different staff user with release authority to approve or reject it with a written note.

Sample book disclosure: the customer accounts, staff users and sanctions watchlist in this environment are seeded demonstration data created by this module — there is no connection to a real core banking system, payment scheme or sanctions feed. Batch (ACH-style) clearing and high-value wire settlement both run through this module's own SIMULATED settlement engine, never a real scheme or wire network.