Blacksec

Administrator
Staff member
ROOT
VIP
The wire is banking's express lane — SWIFT messaging, correspondent hops, same-day or next-day finality, and a scrutiny level that treats every transfer like it might be the last one you ever send. Fee structures, MYBA vs SHA charges, cut-off times, monitoring, and where wires sit in the cashout chain — full mechanics below.

RAIL WIRE (START TO FINISH)

A wire is an authenticated bank-to-bank order: originator bank sends a SWIFT MT103 message (international) or Fedwire/CHAPS-style instruction (domestic), funds move through correspondent accounts, beneficiary bank credits the receiver. Unlike ACH (batch, cheap, reversible-ish windows), wires are individual, expensive ($15–$45 consumer, more for international), fast (same-day domestic, 1–3 days international), and once executed — mostly final. The speed and finality are exactly why they're the loud rail.

INTERNATIONAL WIRE ANATOMY

  • MT103: the payment message — originator, beneficiary, amount, currency, remittance info, plus every correspondent that touches it.
  • Charge codes: OUR (originator pays all fees — beneficiary gets full amount), SHA (split — each side eats own fees), BEN (beneficiary eats everything — their bank deducts en route). Cross-border BEN pulls mean recipient gets less than sent.
  • Correspondent chain: each correspondent bank does its own sanctions screening — a name hit ANYWHERE in the chain freezes the payment mid-hop.
  • Cut-offs: every corridor has daily cut-off times; wires after cut-off roll to next business day. Friday-afternoon wires land Monday/Tuesday.
  • Domestic fast rails: Fedwire (US), CHAPS (UK), TARGET2 (EU large-value) — near-real-time finality, business-hours oriented, higher monitoring stakes.

FEE & FX MATH

LegTypical costNotes
Sending bank fee (domestic)$0-15often free for account tiers
Sending bank fee (intl)$25-45+ possible OUR-code uplift
Correspondent fees (SHA/BEN)$10-40deducted en route, recipient sees reduced credit
Receiving bank fee (intl)$0-20some banks charge incoming wire handling
FX margin (non-USD/EUR)1-3% hidden in ratebank's spread, not visible as "fee"
Priority/urgent add-ons$10-30speeds correspondent queue position

Real-world cost of a $5,000 international wire with SHA: sender fee + correspondent deduction + recipient bank fee + FX spread = easily $60–120 total friction depending on corridor. Percentages matter more than headline fees at scale.

MONITORING (WHERE THE EYES ARE)

  • Real-time sanctions screening at originator, correspondent, and beneficiary — OFAC/EU/UN lists hit on name, address, even payment-info strings (the "bill payment" text field is screenable).
  • AML questionnaires on unusual wires: source of funds, purpose of payment — international personal wires above certain thresholds commonly trigger document requests.
  • Structuring awareness: wires just below internal review thresholds ($9,500-style patterns) aggregate into flags — threshold-aware splitting is itself a pattern.
  • Both ends KYC'd: originator info on the MT103 is verifiable by beneficiary's bank — mismatches (originator ≠ payer relationship story) invite rejection.
  • Business vs personal categorization: wire purpose codes must cohere — "family support" from a business account or vice versa flags instantly.

WHERE WIRES SIT IN THE CHAIN

Bash:
position: mid-to-late chain — AFTER value consolidated in a clean account
  -> never first hop from flagged source (wire from a fresh drop = maximum attention)
  -> story: purpose + relationship + documentation ready pre-send
  -> corridor: same-currency, same-story corridors processed cleaner than odd routes
  -> timing: business hours, no cut-off rushes, no Friday afternoon finals
  -> receiving: aged account, matched name, prior wire history helps

DEATH CONDITIONS

  • Fresh account → large incoming wire → immediate onward wire: layering with zero concealment, dual-bank flags within hours.
  • Payment-info strings that mismatch purpose code (casual text on "business payment") — compliance reads the MT103 literally.
  • Corridor oddities: route through unrelated jurisdictions — every hop adds screening, every hop asks why.
  • Corrections (recall) requests: wires CAN be recalled by bank request/rare fraud clawback — "final" doesn't mean invincible; mis-sent or fraud-claimed wires have recovery paths.
  • Round-number personal wires at business scale ($250,000 "gift") — story failure at obvious thresholds.

WORKING SEQUENCE

Bash:
source account: aged, purpose-consistent, docs ready (invoices/statements)
  -> send: business hours, SHA or OUR by need, corridor straightforward
  -> payment info: coherent with purpose code, real names, no cute strings
  -> receiving: aged, matched name, let credit sit before onward movement
  -> fees: budget total friction (send + corr + recv + FX) before quoting amounts
  -> never: same-day onward wire from receiving end without breathing room

Story documented, corridor straight, credit aged before next hop — wires clear when nothing about them needs explaining. Express lane for accounts that can afford to be seen using it.

— RELATED GUIDES —

Purpose coded, corridor straight, credit aged — the express lane rewards accounts that look like they belong on it. Fees budgeted, docs ready, story readable from MT103 line one. Wire sent in daylight, received in daylight, moved never in a hurry.
 
Last edited: