International Payouts: Sending 50+ Currencies Without the FX Markup

Paying a vendor in London, a contractor in Manila, or a subsidiary in Sao Paulo usually costs more than the invoice says. The gap is the FX markup, the margin a bank or card network folds into the exchange rate before your money reaches the payee. It rarely shows up as a line item, which is exactly why it survives. International payouts done well strip that markup out and send the payee their local currency at a rate close to the real one.

This post is the playbook for paying international vendors, contractors, and subsidiaries in local currency without the hidden conversion cost. It covers where the FX markup hides, how Meow International Payouts sends 50+ currencies from one dashboard with no wire fees, when to pay in local currency versus US dollars versus USDC, the operational flow from adding a payee to funding and sending, how the reconciliation ties back to your ledger, and the corridors where stablecoin rails still win.

Where the FX Markup Hides

Most cross-border payments carry three separate costs, and only one of them is ever quoted to you up front.

The exchange-rate spread: When a bank or card issuer converts dollars into a foreign currency, it does not use the mid-market rate you see on Google. It uses a rate marked up in its favor. On card transactions, the conversion runs on the network rate plus an issuer fee. Visa publishes the rate it applies to a converted transaction, and the issuing bank adds its own charge on top, commonly around 3 percent all in. You can check the network side of that math on Visa's own exchange rate calculator, which shows the rate before the issuer's added fee.

The wire fee: Send an international wire through a traditional bank and you pay a flat fee to send it, often 20 to 50 dollars, sometimes with a separate charge for the SWIFT message. If the payment routes through correspondent banks, each one in the chain can take a cut before the funds land.

The receiving-side deduction: When the payee's bank converts an incoming dollar payment into their local currency, it applies its own spread. The invoice was for a set amount, but the payee receives less, and now you are fielding an email asking where the rest went.

Add these together and a 10,000 dollar payment can quietly lose a few hundred dollars to conversion and fees. At one payment a quarter, nobody notices. Across a full accounts-payable program running dozens of international payees a month, it becomes a real line item. The World Bank tracks this globally through its Remittance Prices Worldwide database, which puts the average cost of sending money across borders above 6 percent of the amount sent. Business payments are cheaper than consumer remittances, but the same markup mechanics apply.

What International Payouts Costs on Meow

International Payouts sends money to 50+ currencies from the same dashboard you use for domestic banking. The pricing is built to remove the layers above rather than repackage them.

No wire fees: Domestic and international wires carry no fee. The flat send charge that a traditional bank adds to every outbound wire is not part of the structure.

FX without manual conversion: You do not pre-buy foreign currency or run a separate conversion step. You choose the currency the payee should receive, fund the payment from your checking balance in dollars, and the conversion happens as part of the send.

A tighter rate: In select currencies, Meow customers save an average of about 2 percent on FX compared with the roughly 3 percent conversion fee baked into a typical card or issuer transaction. That difference is the markup you stop paying. On a 50,000 dollar annual vendor relationship, two points is a thousand dollars that stays with your business instead of the rate spread.

The point is not that currency conversion becomes free. Someone always carries the cost of moving between two currencies. The point is that the margin shrinks toward the real rate and stops hiding inside a number you never agreed to.

Local Currency, US Dollars, or USDC: How to Choose

Paying internationally is really three questions in one: what currency the payee wants, what rail carries it, and who absorbs the conversion. Here is how to think about the three options.

Pay in local currency: This is the default for most vendors, contractors, and subsidiaries. The payee invoices in their own currency, receives that exact currency, and never touches an exchange rate on their end. You carry the conversion once, at a tight rate, and the payee gets certainty. Use this whenever the payee runs their business in a currency other than the dollar and cares about the amount landing whole.

Pay in US dollars: Some payees prefer dollars. Exporters who price in USD, contractors who hold a dollar account, and subsidiaries that consolidate in dollars often want the payment to arrive unconverted so they control the timing of any conversion themselves. Paying in dollars also keeps your books simple when the payee has explicitly asked for it. The trade-off is that the payee, not you, then decides when and how to convert, and their bank's spread applies on their side.

Pay in USDC: For a subset of corridors, a dollar-denominated stablecoin beats both fiat options. If the payee is set up to receive USDC, settlement is fast, traceable on-chain, and cheap, and the payee chooses when to convert to local currency through their own on-ramp. This is covered in more depth below and in the post on paying international suppliers in USDC.

A simple rule: pay in the payee's local currency unless they have asked for dollars, and reach for USDC only in corridors where the payee already lives on that rail.

The Operational Flow: Add Payee, Fund, Send

The mechanics are deliberately close to sending a domestic payment. Three steps.

Add the payee: Enter the payee's details once: legal name, country, receiving bank or account information, and the currency they should be paid in. The payee is saved, so the next payment to the same vendor or contractor reuses the verified details rather than re-entering them.

Fund from checking: The payment draws from your Meow business checking balance in dollars. There is no separate FX wallet to top up and no pre-funding of foreign currency. You hold dollars, and the conversion to the payee's currency happens at send time.

Send: Confirm the amount, the currency, and the payee, and send. The conversion is applied, the payment goes out, and the transaction lands in your activity feed with the payee, amount, currency, and rate recorded against it.

For teams using AI agents, Meow's MCP endpoint lets an assistant run the checks that sit around a payment before a human confirms it. An agent can find a saved payee, pull up their outstanding bills, validate a US routing number against the Federal Reserve database, and confirm the account before anything is sent. By default an agent has zero ability to move money; the account holder turns on each capability explicitly, and every agent-initiated action routes back to a person for approval through Claude, SMS, Telegram, or the dashboard. Account and routing numbers are never exposed to the model.

Reconciliation and the Books

A cross-border payment is only finished when it ties back to your ledger cleanly. International Payouts records each send with the detail an accountant needs.

The transaction record: Every payout carries the payee, the dollar amount debited from checking, the currency delivered, the exchange rate applied, and the date. That is the source document for the entry, and it removes the guesswork of reverse-engineering a rate from a foreign-currency bank statement.

One balance, one feed: Because the payment funds from your checking balance rather than a separate FX account, the outflow shows up in the same activity feed as your domestic payments. There is no shadow account to reconcile on the side.

Sync to your accounting system: Meow syncs and reconciles with QuickBooks and Xero, so international payouts flow into the same books as the rest of your spend. Vendor spend reports roll up foreign-currency payments alongside dollar payments under the same payee. Month-end close treats an international payout like any other bill paid.

The reconciliation goal is boring on purpose. A payment to a contractor in Poland should close the books the same way a payment to a contractor in Ohio does, with the currency and rate captured as metadata rather than as a research project.

Where USDC Rails Still Win

Local-currency payouts cover most of what a finance team needs to send abroad. For some corridors, though, a stablecoin rail is the better tool, and it sits right next to International Payouts inside the same account.

Speed and traceability: USDC settles on Ethereum, Solana, Base, and Arbitrum, and the on-chain transaction hash gives both sides a shared record of the payment from the moment it is sent. In corridors where a wire can sit in correspondent-bank limbo for days, that visibility is worth more than a marginal rate difference.

Payee-controlled conversion: USDC is dollar-denominated. A payee who receives it decides whether to hold dollars or convert to local currency through their own on-ramp, at the timing and spread they choose. In markets with volatile currencies or thin banking access, that optionality can matter more than a bank transfer ever could.

Cost in hard corridors: Where a traditional wire picks up multiple correspondent-bank fees, USDC settlement carries only the on-chain network fee. In the corridors where SWIFT is slow and expensive, that collapses the cost stack.

USDC also runs on the same balance as your fiat, with same-day reconciliation to QuickBooks, so choosing the stablecoin rail for one payee does not fragment your books. The honest limit is universality: not every international payee is set up to receive USDC. Where they are, it can win. Where they are not, local-currency payouts carry the payment. Most finance teams end up using both, matched to the corridor.

A Note on Meow

International Payouts is one surface in a business account that also runs checking with free wires and ACH, corporate cards, crypto, treasury, and invoicing from a single login. That is the design point: the currency you send in should be a field on the payment, not a reason to open another account or bolt on another vendor. Meow does not set the mid-market rate any more than a bank does, but it declines to hide a markup inside it, which is why the FX cost shows up as a tight, quoted spread rather than a number you have to back into. When a payment is better served by USDC, that rail is already in the same account, so the choice is which rail fits the corridor, not which provider to sign up with.

Frequently Asked Questions

How many currencies can I send with International Payouts? You can send more than 50 currencies from the Meow Dashboard. You fund each payment from your dollar checking balance, choose the currency the payee should receive, and the conversion is applied at send time without a separate manual step.

What is the FX markup, and how much does it usually cost? The FX markup is the margin a bank or card network adds to the exchange rate when it converts your money, on top of the mid-market rate you see quoted. On card and issuer conversions it commonly runs around 3 percent all in. In select currencies, Meow customers save an average of about 2 percent on FX compared with that, which is the markup you stop paying.

Are there wire fees for international payments? No. Domestic and international wires carry no fee on Meow. The flat per-wire charge that traditional banks add to outbound wires is not part of the pricing.

Should I pay a vendor in their local currency or in US dollars? Pay in the payee's local currency by default, so they receive the exact amount without touching an exchange rate on their side and you carry the conversion once at a tight rate. Pay in dollars when the payee has specifically asked for it, for example an exporter who prices in USD or a subsidiary that consolidates in dollars, in which case they control the timing of any later conversion.

When does it make sense to pay in USDC instead of local currency? Reach for USDC when the payee is already set up to receive it and the corridor is one where traditional wires are slow, expensive, or opaque. USDC settles on Ethereum, Solana, Base, and Arbitrum with an on-chain record both sides can see, and the payee chooses when to convert to local currency. Where the payee is not set up for USDC, a local-currency payout is the cleaner option.

How does an international payout reconcile to my accounting system? Each payout records the payee, the dollar amount debited, the currency delivered, the exchange rate, and the date, and it appears in the same activity feed as your domestic payments because it funds from your checking balance. Meow syncs and reconciles with QuickBooks and Xero, so foreign-currency payments close the books alongside dollar payments under the same payee.

Can an AI agent send an international payment on its own? No. By default an agent has zero ability to move money. The account holder turns on each capability explicitly, and every agent-initiated action routes back to a human for approval through Claude, SMS, Telegram, or the Meow dashboard. An agent can prepare a payment, find a saved payee, and validate account details, but a person confirms before funds move, and account and routing numbers are never exposed to the model.

Send the Real Amount

The invoice should arrive whole, in the currency the payee actually uses, without a markup skimmed off the rate. International Payouts sends 50+ currencies from the same dashboard as the rest of your money, with USDC rails a click away for the corridors where they win. Open an account at meow.com.

Meow Technologies is a financial technology company, not a bank or FDIC-insured depository institution. Banking services are provided by Grasshopper Bank, N.A.; Member FDIC. The FDIC's deposit insurance coverage only protects against the failure of an FDIC-insured bank.