Key takeaways
- Every cross-border payout is taxed three ways: an FX markup baked into the rate, days of float while money sits in transit, and intermediary banks that deduct fees you never see quoted.
- At volume the tax compounds. Fifty contractors and twenty suppliers each lose 1 to 3 percent to FX and $15 to $50 to wire deductions, so a routine payout run can shed thousands before anyone gets paid.
- A payout layer fixes all three. Settling in dollars, under 5 minutes, at a 0.5 percent flat fee with no rate markup turns a multi-day, multi-fee process into one batch you send and reconcile the same day.
It is the 28th. You owe 50 contractors and 20 suppliers across 15 countries, and every one expects to be paid by month end. You start the wires. The first few clear. Then a bank in the chain deducts $38 from a designer in Manila, a supplier in São Paulo gets 2.4 percent less than you sent because of the exchange rate, and three payments sit "in process" for four days. This is what contractor and vendor payouts look like at scale: not one invoice, but a queue of them, each leaking money in a way the quote never showed. The leak is not random. It is structural, and it gets worse the more people you pay.
What are contractor and vendor payouts?
Contractor and vendor payouts are the payments a business sends to people and suppliers outside payroll: independent contractors, freelancers, agencies, and vendors of goods or services. Contractors and freelancers invoice for labor. Suppliers invoice for inventory, materials, or services. Both sit outside your employee payroll, both often bill in a currency that is not yours, and both expect the full invoice amount, on the date you promised.
That distinction matters because the two flows get grouped under one job. Your finance team runs contractor payments and supplier payments out of the same account, on the same cadence, under the same deadline pressure. Treating them as one operational problem, rather than two tools, is what makes a payout layer worth building.
Why are cross-border payouts so expensive?
Cross-border contractor and vendor payouts are expensive because three costs stack on every transfer, and only one of them is quoted. You see the wire fee. You rarely see the other two until the money lands short.
Here is the anatomy of the tax:
| Cost | Where it hides | Typical hit |
|---|---|---|
| FX markup | Baked into the exchange rate, not shown as a fee | 1 to 3 percent of the amount |
| Days in transit | Money sits in correspondent banks for one to five days | Lost float, late recipients |
| Intermediary deductions | SWIFT correspondent banks skim en route | $15 to $50 per transfer |
The exchange-rate markup is the quiet one. A bank quotes you a "no fee" transfer and then hands you a rate 2 percent off the mid-market rate, so a $10,000 supplier payment arrives as $9,800 and the $200 never appears on a statement. Do that across a payout run and the markup alone can outweigh every visible fee combined. For the full breakdown of how these charges compound, see our guide to cross-border payments.
What are the main ways to pay contractors and suppliers?
You have four realistic methods, and each trades cost against control. The right one depends on how many people you pay and how fast they need the money.
| Method | Speed | Real cost | Best for |
|---|---|---|---|
| Bank wires (SWIFT) | 1 to 5 days | FX markup + $15 to $50 per wire | One-off large payments |
| Payout platforms | Hours to 2 days | Lower FX, per-payout fees | Recurring mixed payouts |
| Contractor-management tools | 1 to 3 days | Platform fee plus FX | Compliance-heavy hiring |
| Stablecoin rails | Under 5 minutes | Flat fee, no rate markup | Fast, high-volume runs |
Bank wires are familiar and work for a single large transfer, but the per-wire deductions and multi-day float make them the worst option at volume. Payout platforms and contractor-management tools like Wise, Payoneer, and Deel narrow the FX gap and add workflow, though you still pay per transaction and often wait a day or more. Stablecoin rails settle in minutes at a flat fee, which is why they fit high-frequency runs. The honest trade-off: your recipient has to accept the method, and compliance still sits with you.
How do you pay contractors and suppliers at scale?
At scale you stop sending payments one at a time and move to a batch. The manual approach, logging into a bank portal and keying 70 transfers by hand, is where errors, duplicate payments, and missed deadlines come from. A payout layer built for volume replaces that with one funded run.
The pattern for paying contractor and vendor payouts at scale looks like this:
- Collect recipients once. Bank details or wallet addresses, currency, and amount in a single file, reused every cycle.
- Fund the run once. Move dollars into the payout layer instead of pre-funding dozens of destination accounts.
- Release the batch together. Every contractor and supplier gets paid in one action, not one at a time.
- Reconcile from one ledger. One statement, one fee line, one export to your accounting tool.
This is the core idea behind mass payouts: collapse the queue into a single event. Layer on vendor payment automation so recurring suppliers get paid on schedule without re-entry, and if you run high headcount every cycle, stablecoin payroll applies the same batch model to your team. Teams that pay programmatically can wire the whole flow into their own systems through a payouts API and trigger runs from the tools they already use.
What do you need to stay compliant?
Compliance for contractor and vendor payouts comes down to two things: documenting who you pay and classifying them correctly. The following is general information, not tax or legal advice, and rules vary by country, so confirm your specifics with a qualified advisor.
For US businesses, the baseline is documentation. You collect a W-9 from domestic contractors and a W-8BEN from foreign ones, then report qualifying US contractor payments on a 1099-NEC. Our primers on how to pay 1099 contractors and what a W-8BEN is walk through the forms in plain terms. The second piece is worker classification: treating a contractor as a contractor and not a misclassified employee, which carries real penalties if you get it wrong. Paying across borders adds a third layer, covered in how to pay international contractors, where local tax and labor rules in the recipient's country come into play. Get the paperwork right before the payment, not after.
Three ways cross-border payouts get taxed
FX markup
A margin baked into the exchange rate on every payment.
Days in transit
Money sits in correspondent banks while people wait.
Intermediary deductions
Each hop skims a fee, so less lands than you sent.
Fix all three with a payout layer that settles fast, in dollars, at a flat fee, to many recipients at once.
How Endl fits
Endl is a payout layer for exactly this job: paying people and suppliers across borders without the three-way tax. You charge a 0.5 percent flat platform fee plus a small fixed rail fee, both shown in the quote before you send, and there is no markup in the exchange rate. Local-rail fees are $0 on the Pro plan. Payments settle in under 5 minutes, 24/7, to 160-plus countries over 40-plus local rails.
The model is built for batches. You hold a self-custodial stablecoin balance in USDC or USDT, convert between fiat and stablecoin as you need, and pay out to bank accounts or wallets. You can receive in USD, EUR, GBP, MXN, or BRL; the same account also handles how to receive international payments from your own customers. Endl-to-Endl and external-wallet transfers are $0 and instant, so paying a contractor who also uses Endl costs nothing and lands immediately. Onboarding takes under 24 hours, and you can open a business account online remotely without a local entity.
Two honest limits: Endl is not a bank, and balances are not insured. Endl is a registered VASP in the EU and an MSB in Canada, operating with licensed partners. Treat the stablecoin balance as a settlement tool for moving money fast, not as a place to park reserves.
See the full breakdown on the pricing page, or start free and run your first batch.
