.jpg)
Banks charge an average of 14.99% to move $200 across a border, according to the World Bank's Remittance Prices Worldwide report covering Q3 2025, published in April 2026.
That is the most expensive channel in the entire dataset, and it is the same correspondent banking infrastructure most companies still use to pay international contractors.
Gigapay exists to take that problem off treasury's desk: one vendor, one invoice in your funding currency, and payouts delivered to creators and contractors on local rails in 65+ countries.
When a payment run covers 200 contractors at $400 to $500 each, the gap between wire economics and local rail economics stops being a rounding error and becomes a line item worth thousands per batch.
This article breaks down every cost layer in an international wire transfer, what local rails cost instead, what the numbers look like at batch scale, and what a merchant of record changes for the treasury team that owns the total.
Key Takeaways
- A $500 international wire can lose $55 to $170 to fees, deductions, and FX spread.
- Banks average 14.99% to move $200 cross-border, per World Bank Q3 2025 data.
- Local rails cost roughly $0.50 to $5 per payout with FX spreads under 1%.
- A merchant of record turns 200 cross-border payouts into one invoice in your currency.
- Wires suit large supplier payments. Batch contractor payouts belong on local rails.
Why Cross-Border Payments Cost More Than the Quoted Fee
The fee your bank publishes for an international wire transfer is the smallest part of what the payment actually costs. Routefusion's March 2026 fee analysis puts the visible SWIFT transfer fee at $25 to $50 per transaction, and then layers on what sits underneath: a 1% to 3% FX markup baked into the exchange rate and $15 to $40 deducted by each intermediary bank the payment passes through.
The structural reason is that SWIFT does not move money. It moves messages between banks. The money itself travels through a chain of correspondent banks, and every bank in that chain can take a cut.
The Bank for International Settlements has documented that active correspondent banking relationships fell 22% between 2011 and 2019, which means fewer direct routes and more intermediary hops per payment. Each hop is a deduction point.
Treasury teams that pay a handful of large international suppliers rarely feel this. A $70 total cost on a $50,000 invoice is 0.14%. The same $70 on a $500 contractor payout is 14%. The cost structure of the correspondent banking system was built for the first case and quietly punishes the second.
Batch Contractor Payouts Are a Different Cost Problem Than Supplier Payments
Here is the version of this problem that finance teams actually experience. Treasury sees SWIFT fees, intermediary deductions, and FX spreads spread across bank statements. Accounts payable sees an email from a contractor saying they received $473 of an agreed $500. Nobody quoted a higher price.
Under the SHA fee arrangement that most international wires default to, intermediary banks deduct their charges from the payment amount after the sender has already paid, so the credit simply arrives short.
One short payment is an annoyance. Two hundred short payments per campaign is an operational category of its own. Someone has to answer every "where is the rest of my money" message, decide whether to top up the difference, book the adjustment, and explain the variance at month end.
The influencer and creator economy runs on exactly this payment profile: high payee counts, sub-$1,000 average amounts, and payees spread across dozens of countries. Gigapay's own research with Billion Dollar Boy and Meltwater found payment terms in influencer marketing stretching as far as 120 days, and rail friction is one of the reasons the cycle drags.
So the question worth asking is precise. It is not "how do we send money abroad." It is "what does each rail cost us per payee, at our batch size, in our corridors, including the costs that never appear on a fee schedule."
What an International Wire Transfer Actually Costs
Stack every layer and the true cost of a single cross-border wire looks like this.
Your Bank's Outgoing Wire Fee
The visible line. Corpay's 2026 review of published bank pricing puts outgoing international wires at $35 to $50 at most US banks, with European banks typically charging €15 to €50 per SWIFT payment. Sending 200 wires means paying this fee 200 times, so the floor for a single batch is $7,000 to $10,000 before anything else happens.
Correspondent Bank Deductions Along the SWIFT Chain
Each intermediary bank between your bank and the recipient's bank can deduct a lifting fee, typically $15 to $50 per hop according to Airwallex's 2026 cross-border cost analysis. A payment that routes through two or three correspondents loses $30 to $150 before it lands. These fees are often undisclosed upfront, they vary by corridor, and under SHA arrangements they come out of the payee's money.
The Recipient Bank's Incoming Fee
Many receiving banks charge their own fee to credit an incoming international wire, commonly $10 to $15 or a local equivalent. The contractor pays it, which means from their perspective you underpaid them, which means the dispute lands back with your AP team anyway.
The FX Spread Hidden in the Exchange Rate
The exchange rate is where banks earn most of their cross-border revenue. The typical bank markup runs 1% to 3% above the mid-market rate. On a $100,000 batch, that is $1,000 to $3,000 that never appears as a fee anywhere, because it is priced into the rate itself. You would need to compare your executed rate against the interbank rate at the moment of conversion to see it at all.
Trace Fees When a Payment Sits in a Nostro Account
When a wire stalls at an intermediary, sits in a nostro account, or gets held for a compliance check, the only remedy is a trace. Banks commonly charge $25 to $75 per trace request, and the investigation can take days. On a 200-payee batch, even a 2% exception rate means four traces per run, plus the AP hours spent managing them and the contractor relationships strained while everyone waits.
The Per-Payment Total
Add it up for one $500 payout: $35 to $50 sender fee, $15 to $90 in correspondent deductions, $10 to $15 incoming fee, and $5 to $15 of FX spread. The realistic range is $55 to $170 per payment, or 11% to 34% of the amount sent. That is how a contractor ends up with $473, and why the World Bank finds banks averaging nearly 15% on small cross-border payments.
What Local Payment Rails Cost for Cross-Border Payouts
Local rails are the domestic payment systems of the recipient's own country: SEPA and SEPA Instant in the eurozone, Faster Payments in the UK, ACH in the US, and their equivalents elsewhere. Instead of pushing a payment through the correspondent chain, the payer converts currency once and delivers a local credit that behaves like any domestic transfer.
Per-Transaction Fees on ACH, SEPA, and Faster Payments
The economics are structurally different. Routefusion's March 2026 breakdown prices local rail payouts through API-first providers at $0.50 to $5 per transaction with FX markups of 0.3% to 0.8%, and no intermediary deductions because there are no intermediaries. The payee receives the full local amount. Settlement is same day or instant on most of these rails rather than the 1 to 5 business days typical of SWIFT end-to-end settlement.
On the same 200-payee, $100,000 batch, transaction fees fall from $7,000+ to somewhere between $100 and $1,000, and FX cost falls from $1,000 to $3,000 down to $300 to $800.
What Local Rails Do Not Remove: Identity, Tax, and a Reason to Pay
Cheaper rails do not make the compliance work disappear. You still need to know who you are paying, verify their identity, collect a valid tax ID, determine whether reporting obligations like DAC7 in the EU or Germany's KSK levy apply, and hold a contractual basis for paying that person at all. A local credit to an unverified payee in a country you have no tax position in is a cheap payment and an expensive audit finding.
This is the part most rail comparisons skip. The rail solves the cost of moving money. It does not solve the cost of being allowed to move it.
For a treasury team, that second cost shows up as vendor onboarding, W-8/W-9 or local equivalent collection, sanctions screening, and a reporting obligation calendar that now spans every country on the payee list.
The Math at 200 Payees: Wires vs Local Rails Side by Side
Assume a batch of 200 contractor payouts at $500 each, $100,000 total.
The ranges are wide because corridors differ, but the shape of the result does not.
- On wires, the batch costs 13% to 34% of the amount sent, and a large share of it is invisible because it comes out of the payees' credits rather than your fee line.
- On local rails, the batch costs under 2%.
The absolute gap on a single monthly run is five figures.
The Costs That Never Show Up on a Fee Schedule
Bank pricing captures maybe half of what treasury actually pays. The rest is operational.
- Short-payment disputes: Every SHA deduction generates a payee who believes they were underpaid. Each case costs AP time to investigate, a decision on who absorbs the difference, and a correcting entry. At 200 payees, this is a recurring workstream, and it lands during the exact week the team is closing the books.
- Reconciliation: Two hundred wires produce two hundred debits, at two hundred slightly different net amounts once deductions and FX land, against two hundred expected values. Matching them is manual work that scales linearly with payee count.
- Vendor sprawl: Paying contractors directly means onboarding each one as a vendor: banking details, tax forms, sanctions checks, ERP records. Gigapay's analysis of a brand running 600 creator collaborations a year found roughly 840 admin hours consumed by this process, at an all-in cost near €139,590 annually.
- Payment repair: Wrong IBANs, closed accounts, and name mismatches bounce. Each returned wire costs a return fee, a re-send fee, another FX conversion, and days of delay for a payee who was already waiting.
- The relationship cost: Contractors and creators talk. A brand known for payments that arrive short and late pays for it in negotiating leverage and in who agrees to work with them at all.
What a Merchant of Record Changes for Treasury
A merchant of record restructures the problem instead of discounting it. Under Gigapay's model, Gigapay contracts with each contractor or creator, formally purchases their deliverable, and resells it to you. The consequences for the treasury are concrete.
1. You pay one invoice, in your currency
One consolidated invoice per batch or campaign, funded in USD, EUR, GBP, SEK, DKK, or NOK. There is no wire file with 200 rows, no per-payee FX decision, and no SHA-versus-OUR debate. Gigapay reports an 80% reduction in invoice volume for its clients, and the ERP effect is starker: 300+ vendor records collapse into one.
2. The payouts run on local rails
Gigapay delivers payouts through SEPA Instant, Faster Payments, ACH, and their local equivalents, instantly in most markets. Payees receive the full local amount. The "$473 of $500" conversation stops happening because there is no correspondent chain to deduct from.
3. Identity, tax, and reporting move with the contract
Because Gigapay is the counterparty, it runs KYC on every payee, validates tax IDs and VAT numbers, and handles reporting obligations such as DAC7 in the EU, KU14 for Denmark, and KSK assessment in Germany. Payees can onboard as individuals without a registered business, which matters when your payee list is full of nano and micro creators.
One point of precision: as merchant of record, Gigapay is not withholding income taxes or social contributions on payees' behalf outside its Swedish employer-of-record service. Payees remain responsible for their own taxes, and the reporting is what gets automated.
4. You stop being the treasury desk for 65 countries
The corridor-by-corridor questions about rails, deduction practices, reporting rules, and payee verification become Gigapay's operating problem rather than a spreadsheet your team maintains. Treasury's cost of payments becomes one number on one invoice, which is the format a cost review can actually work with.
The trade is transparency for stacked opacity. Gigapay charges a disclosed admin fee per payout on its Base plan, with volume pricing at enterprise scale. That fee is visible, budgetable, and comparable, which is more than can be said for a correspondent chain's lifting fees.
How to Run a Cost-of-Payments Review That Includes Contractor Payouts
Most treasury cost reviews scrutinize supplier payments and bank relationship fees and skip campaign payouts entirely, usually because the costs sit in a marketing budget or inside payees' deductions where finance never sees them. A review that captures the full picture takes four steps.
- Full twelve months of cross-border payments and separate them by profile: low-count high-value supplier wires versus high-count low-value contractor payouts. The two have opposite economics and should not share a rail by default.
- Compute true cost per payment for the contractor segment. Include sender fees, an estimate of deductions (compare what payees confirmed receiving against what was sent), the FX spread against mid-market rates on conversion dates, and trace or repair fees from bank statements.
- Add the operational load: AP hours on disputes, reconciliation, vendor onboarding, and payment repair, priced at loaded cost. Gigapay's 600-collaboration benchmark of 840 hours a year is a reasonable starting reference for scale.
- Price the alternatives against that true cost, not against the published wire fee. Compare local-rail providers and merchant-of-record pricing on the same all-in basis. If treasury's cost-of-payments review includes campaign payouts, Gigapay belongs on the page next to the SWIFT line, because that is the line it replaces.
When an International Wire Is Still the Right Rail
Wires are not obsolete. They remain the correct choice in specific situations, and a credible payout policy names them.
A $50,000 payment to a single production partner is wire territory. The fixed cost is negligible at that value, wires carry high value ceilings, and SWIFT gpi has genuinely improved speed, with SWIFT reporting that around 90% of cross-border payments now reach the destination bank within an hour.
Corridors with no reliable local rail coverage, payments requiring specific documentation for currency controls, and one-off transactions where setting up anything else is not worth the effort are all legitimate wire use cases.
The policy that falls out of this article is simple to state. Wires for large, infrequent, high-value payments. Local rails, ideally through a merchant of record, for batch payouts to individuals.
The expensive mistake is running the second category on the first category's rail because that is how the bank relationship was set up years ago.
Conclusion
Gigapay gives treasury teams one vendor, one invoice, and local-rail payouts across 65+ countries, which is the structural answer to a cost problem that wires cannot price their way out of.
The numbers in this article point one direction: an international wire costs $55 to $170 on a $500 payout once fees, correspondent deductions, and FX spread are counted, while local rails deliver the same payment for a few dollars with the full amount arriving.
At 200 payees per batch, the difference is five figures per run, before counting the AP hours spent on short-payment disputes and reconciliation.
A merchant of record moves the entire stack, rails, compliance, and payee support, behind a single invoice in your funding currency.
If your next cost-of-payments review is going to include campaign and contractor payouts, book a demo with Gigapay and put a real number next to the SWIFT line.
Read Next:
- How to Pay International Contractors in 2026: W-9, W-8BEN, 1099, and 1042-S
- Vendor Master Data When Your Suppliers Are 400 Individuals
- Accounts Payable Audit Trails for High-Volume Contractor Payments
FAQs:
1. What do international wire transfers cost for batch contractor payouts?
International wire transfers cost $55 to $170 per payment for batch contractor payouts once sender fees ($35–$50), correspondent bank deductions ($15–$90), recipient bank fees ($10–$15), and a 1% to 3% FX spread are combined. On a $500 payout, that is 11% to 34% of the amount sent, which is why contractors often receive credits short of the agreed amount.
2. Are local payment rails cheaper than international wires for cross-border contractor payouts?
Local payment rails are significantly cheaper than international wires for cross-border contractor payouts, typically costing $0.50 to $5 per transaction with FX spreads of 0.3% to 0.8% and no intermediary deductions. On a 200-payee batch of $100,000, local rails cost roughly $400 to $1,800 in total, against $13,000 to $34,000 on wires.
3. Can treasury teams use Wise Business for batch contractor payouts?
Treasury teams can use Wise Business for batch contractor payouts when the payee count is small, but at 200 payees the team still owns the payment file, payee onboarding, identity verification, tax ID collection, and reporting obligations in every payee country. A merchant of record like Gigapay removes that ownership by contracting with each payee directly and consolidating the batch into one invoice.
4. Who owns FX risk when a merchant of record handles cross-border payouts?
FX risk on a merchant-of-record invoice issued in your funding currency sits inside the provider's payout stack rather than on your treasury desk, because you pay a fixed amount in your own currency. The applicable rate policy is defined in the service agreement, so treasury should review the contract's FX terms before signing to confirm how conversion rates are set.
5. Can batch contractor payouts settle same day on local rails?
Batch contractor payouts can settle same day or instantly on local rails such as SEPA Instant and Faster Payments, but treasury should commit payees to a defined batch schedule rather than promising same-day delivery, because settlement timing varies by corridor, cut-off times, and verification status. A predictable schedule that always holds beats a same-day promise that sometimes fails.
.jpg)
.jpg)
.jpg)
