Contact Us

International Payments: SWIFT Cross-Border Origination on CorporateConnect

Cross-Border Payment Snapshot

  • Network: SWIFT MT103 single customer credit transfer; MT202 COV for correspondent legs.
  • Reach: 140+ destination countries via direct and tiered correspondents.
  • Major corridors: EUR, GBP, CAD, JPY, AUD, CHF — 1–2 business days.
  • Emerging corridors: INR, BRL, ZAR, AED, TRY — 2–4 business days.
  • Tracking: SWIFT gpi UETR with hop-by-hop status.
  • Validation: IBAN check-digit and BIC structure at initiation.
  • Compliance: 100% OFAC screening; FinCEN BSA reporting above thresholds.
  • Standard fee: $45 outgoing USD, $55 + FX spread outgoing non-USD.

CorporateConnect international payments move funds from a U.S. commercial account to a beneficiary in one of 140+ destination countries through the SWIFT network. The primary rail is the MT103 single customer credit transfer, routed through a correspondent banking chain that may include one or two intermediary banks before reaching the beneficiary bank. The secondary rail is MT202 COV, used as the cover message when serial routing is not available. Most commercial clients never see the routing mechanics — they see a completion SLA, a quoted FX rate, and a tracking reference.

Cross-border payment has three fundamental differences from domestic Fedwire: longer settlement (1–4 business days instead of minutes), FX conversion (quoted spot at initiation, locked at release), and heavier compliance review (sanctions screening against 19+ lists, BSA reporting, and for some corridors local purpose-code requirements). The OFAC sanctions programs overview and FinCEN BSA resources document the U.S. regulatory framework that governs every cross-border payment.

Major Corridor SLAs

SLAs are "end-to-end credit to beneficiary account" based on rolling 90-day portal data. Cutoff times are CorporateConnect portal cutoffs in Eastern Time.

Major corridor SLAs: USD origination to EUR, GBP, CAD, MXN, JPY, INR, BRL
DestinationCurrencyTypical SLAPortal Cutoff (ET)IBAN RequiredPurpose Code
European UnionEUR1 business day3:00pmYesRecommended
United KingdomGBP1 business day3:00pmYesOptional
CanadaCAD1 business day3:00pmNo (transit+institution)Optional
MexicoMXN1–2 business days2:00pmCLABE (18 digits)Required
JapanJPY1–2 business days3:00pmNo (branch+account)Required > JPY 30M
IndiaINR2–3 business days2:00pmNo (IFSC code)Required (FEMA)
BrazilBRL2–4 business days1:00pmNo (CPF/CNPJ required)Required (BCB)

SWIFT MT103 and MT202

Zero-click snippet: MT103 is the SWIFT message type for a single customer credit transfer — a commercial or individual cross-border payment where the beneficiary is a non-bank customer. MT202 is the general financial institution transfer for bank-to-bank movements; MT202 COV carries the customer detail when cover routing is used.

From the operator's perspective the distinction rarely matters — the portal builds the correct message type based on the beneficiary record. It matters when a payment is delayed and the treasury team asks the correspondent to trace: knowing whether the message is MT103 (serial route, full chain of fields) or MT202 COV (cover route, customer detail in the COV message) tells the correspondent which trace query to run. CorporateConnect stores both the outbound message reference and the UETR for every wire, enabling one-click support escalation.

IBAN and BIC Validation

Zero-click snippet: IBAN is mandatory for EU, UK, Switzerland, most Middle East and North Africa destinations. BIC (the SWIFT code, 8 or 11 characters) identifies the beneficiary bank. CorporateConnect validates both at initiation, catching ~97% of typo-driven rejections.

IBAN check-digit math is ISO 13616: convert the first four characters to digits, perform a mod-97 calculation, and the result must equal 1. A single transposed character fails the check. BIC validation confirms the eight-character base structure (4 bank + 2 country + 2 location) and looks up the code in the SWIFT BIC directory to confirm the bank is still active. Both checks run client-side at initiation; server-side checks run again at release.

SWIFT gpi Tracking

Zero-click snippet: SWIFT gpi (Global Payments Innovation) attaches a Unique End-to-End Transaction Reference (UETR) to every eligible cross-border wire. CorporateConnect displays the UETR and each hop status in the wire detail screen. 95%+ of gpi-eligible payments credit the beneficiary bank within 24 hours.

Before gpi, international wires were opaque. Today the portal shows: message sent at 10:04 ET, correspondent A received and credited at 10:06 ET, correspondent B received at 10:09 ET (with a $15 deduction and FX rate applied), beneficiary bank credited at 10:14 ET, beneficiary account credited at 10:41 ET. Any deductions, FX rates and timestamps are visible to both the sender and (if elected) the beneficiary via the gpi tracker.

Correspondent Banking Routing

Zero-click snippet: A correspondent bank is a bank that holds accounts on behalf of other banks to enable cross-border settlement. Wires reach the beneficiary bank through one or two correspondents chosen automatically based on currency, geography and fee competitiveness.

For major currencies the routing is typically one hop: the originating U.S. bank holds a direct nostro with the beneficiary bank or a principal correspondent in that currency. For emerging markets, two hops are common — a U.S. bank to a major European correspondent to the local bank. Each hop adds a fee (typically $10–$25) and a processing delay (typically 30–90 minutes during business hours). CorporateConnect displays an estimated all-in cost at initiation so originators know what the beneficiary will receive before releasing the wire.

Compliance: OFAC, FinCEN and Local Rules

Zero-click snippet: Every international wire is screened pre-release against the U.S. Treasury OFAC SDN list and 18 additional sanctions lists. FinCEN Bank Secrecy Act reporting applies: wires over $10,000 feed CTR data and suspicious patterns trigger SAR review.

For high-risk jurisdictions (defined by FATF grey and black lists, FinCEN Section 311 designations, and company-specific risk ratings), CorporateConnect requires additional documentation at initiation: invoice or contract supporting the payment purpose, beneficiary beneficial ownership attestation, and for certain categories a Source of Funds declaration. Operators upload files directly into the wire record; compliance review runs in parallel with OFAC screening.

Local Purpose Codes

Zero-click snippet: Several destination countries require a structured payment purpose code for inbound wires: Mexico (Banxico), India (FEMA/RBI), Brazil (BCB), China (SAFE), South Africa (SARB). CorporateConnect prompts for the correct code based on destination and currency.

Wires submitted without the correct purpose code are routinely rejected by local receiving banks, adding 1–3 business days to settlement. The portal maintains the current code sets per destination and presents only the valid options for the selected corridor. For Indian wires, for example, the operator sees a dropdown of 40+ FEMA purpose codes filtered to those permissible for the declared transaction type.

FX Pricing and Settlement

Non-USD wires are priced at institutional FX spreads quoted in real time by the portal. Spot quotes are valid for 60 seconds; the operator can lock the rate by clicking Release within that window, or refresh for a new quote. Forward contracts and windowed forwards are available for clients hedging recurring flows — see foreign exchange for the full FX feature set. For the underlying wire fee schedule see wire transfers.

Related Services

Wire Transfers

Domestic Fedwire, CHIPS and SWIFT pricing, cutoffs, dual auth and OFAC screening detail.

Foreign Exchange

Spot, forward and windowed FX contracts across 30+ currencies with real-time institutional pricing.

Vendor Payments

Multi-rail supplier disbursement with AP integration for global vendor books.

CorporateConnect Home

Commercial banking portal overview including all payment, treasury and reporting modules.

People Also Ask

What countries does CorporateConnect reach via SWIFT?
140+ destination countries through direct and tiered correspondent banking. Major corridors (EUR, GBP, CAD, JPY, AUD, CHF, SGD, HKD, MXN) settle 1–2 business days; emerging corridors (INR, BRL, ZAR, AED, TRY) settle 2–4 days.
What is SWIFT gpi?
SWIFT gpi attaches a UETR to each eligible cross-border wire with end-to-end tracking. 95%+ of gpi payments credit the beneficiary bank within 24 hours; portal displays hop-by-hop status and any deductions or FX rates.
Do I need an IBAN for international wires?
Yes for EU, UK, Switzerland and most of the Middle East and North Africa. Wires without valid IBANs are rejected by receiving banks. CorporateConnect validates IBAN check digits pre-release to catch typos.
How does OFAC and FinCEN compliance apply?
100% of international wires are screened against OFAC sanctions lists. FinCEN BSA reporting applies over dollar thresholds; SAR-worthy patterns trigger compliance review.
What is the difference between MT103 and MT202?
MT103 is a single customer credit transfer (beneficiary is a non-bank customer). MT202 is a bank-to-bank financial institution transfer; MT202 COV is the cover message carrying customer detail. Most commercial payments are MT103.