How Wire Transfer Works
A wire transfer follows a structured chain of instructions between financial institutions, not a literal movement of cash. Understanding each step helps merchants and developers anticipate timing, cost, and potential failure points.
Originator Initiates the Transfer
The sender — whether an individual, business, or automated system — submits payment instructions to their bank. These instructions include the beneficiary's account details, bank identifiers, amount, currency, and a payment reference. Most banks enforce a daily cutoff time after which instructions queue for the next business day.
Originating Bank Validates and Screens
The sending bank authenticates the request, verifies available funds, and screens the transaction against AML rules and sanctions lists (OFAC, UN, EU). Depending on the transfer value and destination, enhanced due diligence may be triggered. The bank then debits the sender's account.
Message Sent Over the Network
For domestic US transfers, instructions route over Fedwire (Federal Reserve) or CHIPS (Clearing House Interbank Payments System). International transfers use SWIFT messaging — a standardized, encrypted communication network connecting over 11,000 financial institutions in 200+ countries. SWIFT sends messages; settlement happens separately through correspondent account relationships.
Correspondent Banking Chain (International)
If the originating bank has no direct relationship with the beneficiary bank, funds pass through one or more correspondent banks. Each correspondent charges a fee and performs its own screening. This chain adds both cost and time to cross-border electronic funds transfers.
Beneficiary Bank Credits the Account
Once the receiving bank accepts the funds and reconciles the SWIFT or Fedwire message, it credits the beneficiary's account. The transfer is now complete and irrevocable. The beneficiary receives a credit advice notification, which merchants should match against expected payment references.
Why Wire Transfer Matters
Wire transfers remain the backbone of high-value B2B and cross-border commerce despite the rise of real-time payments. Their scale and reliability make them indispensable for treasury operations, large-ticket ecommerce, and international supplier payments.
The SWIFT network alone processes over 44 million messages daily across more than 200 countries and territories, underpinning trillions of dollars in global trade finance. In the United States, the Fedwire Funds Service settled approximately $1.1 quadrillion in 2023 — roughly $4.4 trillion per business day — demonstrating the sheer volume of value that flows through wire infrastructure.
For high-value ecommerce — luxury goods, real estate technology platforms, wholesale B2B marketplaces — wire transfers reduce payment processing costs versus card interchange. A 2.5% card fee on a $500,000 transaction costs $12,500; a wire costs under $50. The economics are unambiguous above certain ticket thresholds. Additionally, wire transfers carry no chargeback risk, making them the preferred settlement method when merchants require payment finality before fulfilling large or irreversible orders.
Regulatory Baseline
Under the Bank Secrecy Act and FinCEN's Travel Rule, US financial institutions must collect and transmit originator and beneficiary information for wire transfers of $3,000 or more. International equivalents (FATF Recommendation 16) apply in 200+ jurisdictions.
Wire Transfer vs. ACH
Wire transfers and ACH are both bank-to-bank payment methods, but they serve different use cases. The choice between them affects speed, cost, reversibility, and volume suitability.
| Attribute | Wire Transfer | ACH Transfer |
|---|---|---|
| Speed | Domestic: same-day; International: 1–5 days | Same-day ACH or next-day; standard is 1–2 days |
| Cost (sender) | $15–$50 per transaction | $0.20–$1.50 per transaction |
| Reversibility | Irrevocable once settled | Reversible up to 60 days (consumer) |
| Transaction limit | No statutory limit (bank policies vary) | $1M per transaction (Same-Day ACH) |
| Best for | High-value, time-sensitive, international | Payroll, subscriptions, low-value B2B |
| Network | Fedwire, CHIPS, SWIFT | NACHA network |
| Settlement finality | Final on same day | Delayed; subject to returns |
| Fraud risk for sender | High (irrevocable, BEC target) | Lower (reversibility protects senders) |
For merchants operating at scale, the right choice depends on transaction value, geography, and tolerance for return risk. ACH suits recurring billing; wire transfers suit one-time high-value orders.
Types of Wire Transfer
Wire transfers are not monolithic — several variants exist to serve domestic, international, and specialized use cases.
Domestic Wire Transfer routes entirely within one country's payment infrastructure. In the US, Fedwire handles real-time gross settlement (RTGS) between banks. CHIPS processes the bulk of high-value interbank dollar settlements each day using a multilateral netting mechanism.
International Wire Transfer (Telegraphic Transfer) crosses borders via SWIFT messaging. Payment instructions travel in ISO 20022 or MT message format, with settlement occurring through pre-established nostro/vostro correspondent accounts.
SWIFT gpi (Global Payments Innovation) is an enhanced international wire service offering end-to-end tracking, same-day settlement in many corridors, and fee transparency. Over 4,000 banks have adopted SWIFT gpi, which now covers the majority of SWIFT cross-border payment traffic.
Book Transfer moves funds between accounts held at the same institution — technically a wire in structure but settled instantly on the bank's internal ledger with no external network involved.
Real-Time Gross Settlement (RTGS) systems like Fedwire, TARGET2 (Europe), and CHAPS (UK) settle each wire individually and immediately in central bank money — providing the highest level of payment finality.
Best Practices
Strong operational controls around wire transfers protect both treasury teams and the platforms they build on. The irrevocability of wires makes prevention far more valuable than recovery.
For Merchants
Establish a formal wire verification process: never update beneficiary banking details based on email alone. Require a phone callback to a known contact number before executing any change. For B2B invoice payments, implement a dual-approval rule for transfers above a defined threshold — two authorized signatories must approve before the wire is submitted.
Maintain a whitelist of approved beneficiary accounts in your banking portal. Reconcile incoming wires daily against open orders using structured payment references. If operating internationally, negotiate OUR fee instructions with your bank so correspondent deductions do not create partial-payment disputes with suppliers.
For Developers
When integrating wire transfer initiation via a bank API or payment orchestration layer, always validate IBAN and BIC/SWIFT codes programmatically before submission — malformed identifiers cause returns that can take days to resolve. Use ISO 20022 structured address fields rather than free-text to maximize straight-through processing rates.
Build idempotency into your wire submission logic. A network timeout does not confirm whether the transfer was accepted; duplicate submissions create costly overpayments. Store a unique end-to-end transaction reference (UETR for SWIFT gpi) and poll status before retrying. Expose settlement status webhooks to downstream systems so fulfillment workflows are not triggered before funds are confirmed.
Common Mistakes
Sending to unverified account details. Business Email Compromise (BEC) fraud — where attackers intercept or spoof payment instructions — cost US businesses $2.9 billion in 2023 according to the FBI's IC3 report. Always verify account changes through an out-of-band channel.
Missing bank cutoff times. Wires submitted after a bank's same-day cutoff (commonly 5 PM ET for Fedwire) are queued to the next business day. For time-sensitive settlements, build buffer time into payment workflows and confirm your bank's exact cutoff schedule.
Incorrect SWIFT/BIC or routing number. A single transposed digit can route a wire to the wrong institution or trigger an automated rejection. Rejected international wires may take 3–7 business days to return and may incur investigation fees from correspondent banks.
No payment reference on incoming wires. Without a structured reference, reconciling customer wire payments against open invoices becomes a manual process. Always provide customers with a specific reference code and validate it against your accounts receivable system on receipt.
Ignoring intermediary fee deductions. On SHA (shared) fee wires, correspondent banks may deduct their charges from the principal amount. Merchants expecting exact payment amounts should request OUR fee transfers or account for potential deductions in their reconciliation logic.
Wire Transfer and Tagada
Tagada's payment orchestration layer helps platforms manage wire transfer workflows alongside cards, ACH, and alternative methods — without building direct bank integrations for each corridor.
With Tagada, you can route high-value transactions automatically to wire transfer rails based on ticket size thresholds, buyer geography, or currency — ensuring you always pay the lowest effective processing cost while maintaining settlement finality where it matters.
For B2B platforms and marketplaces handling cross-border supplier payments, Tagada's orchestration engine abstracts the complexity of correspondent banking chains, SWIFT message formatting, and multi-currency settlement reconciliation into a single unified API — so engineering teams ship faster without becoming wire transfer specialists.