If your team is starting to build cross-border payouts, the fee structure alone can catch you off guard. Exchange rate markups, correspondent bank cuts, and compliance overhead all layer on top of each other in ways that aren't obvious until you're already processing volume. Getting a clear picture of how these payments actually move, and where they tend to break, is the right place to start. Cross-border payment flows vary by corridor, currency, rail, provider, bank partner, FX setup, and program structure. This article covers common models, not every possible structure.
TLDR:
- The global cross-border payments market had a total addressable market of $194.6 trillion in 2024 and is forecast to reach $320 trillion by 2032, per FXC Intelligence.
- On many corridors, SWIFT transmits instructions, not funds, so transfers may pass through multiple correspondent banks and can take 2-5 business days depending on the corridor and intermediary chain.
- FX markups can be a significant cost in certain scenarios, with the amount varying by provider, corridor, currency pair, transaction size, and pricing model.
- Build exception handling with defined SLAs and audit trails before you scale; manual resolution is where cross-border programs can be operationally expensive and difficult to manage.
What Is a Cross-Border Payment?
A cross-border payment is any transfer of funds between parties in different countries. That covers a wide range: a U.S. business paying a supplier in Vietnam, a freelancer in Nigeria receiving a client payment from Canada, or a consumer buying from a foreign e-commerce store.
What makes these transactions complex is that no single financial system spans the globe. Each country tends to operate its own banking infrastructure, currency, and regulatory framework, so moving money across borders generally requires coordination between multiple institutions. These transactions can move through different models, including correspondent banking, international wire transfers, card-network flows, local payout partners, account-to-account networks, wallets, and specialized payment providers.
The Cross-Border Payments Market in 2026
Cross-border payments represent a massive global market. According to FXC Intelligence, the total addressable market was approximately $208 trillion in 2025 and is forecast to reach approximately $320 trillion by 2032. The FSB's cross-border payments roadmap identifies cost, speed, access, and transparency as the four core challenges driving reform efforts globally.
That growth spans a wide range of use cases, including B2B trade, international workforce payments, and consumer remittances. How a cross-border payment moves can vary significantly based on the use case, corridor, currency, payment rail, provider, and program structure.
For teams evaluating cross-border payments, the key questions are practical: How do cross-border payments work? How long do international payments take? What do they cost? And what does it take to add cross-border payment capabilities to a financial product?
Types of Cross-Border Payments
Cross-border payments fall into four categories based on who is sending and who is receiving. Each often involve different volume profiles, compliance requirements, and infrastructure considerations.
How a Cross-Border Payment Works, Step by Step
Here is one common way a cross-border payment can move from sender to recipient. Specific steps and timing may vary depending on the corridor, rail, and program structure in use.
The Core Steps
On many cross-border payment flows, a few key handoffs commonly occur:
- The originating bank or payment service receives the transfer instruction and debits the sender's account, capturing currency, amount, and recipient banking details.
- If the two institutions don't hold accounts with each other, one or more correspondent banks may be used to help route and settle the payment, each potentially applying their own fees and exchange rates along the way.
- Currency conversion typically happens at whichever point in the chain the FX rate is applied, which may not be the most favorable moment for the end user.
- The receiving bank may credit the recipient's account once it clears applicable compliance checks, which can take anywhere from hours to several business days depending on the corridor and rails used.
Other cross border models may use local payout partners, card networks, account-to-account networks, wallets, or other structures besides a traditional correspondent banking chain.
Why Each Step Adds Cost and Delay
On many corridors, each intermediary in the chain may hold funds briefly, run its own compliance check, and extract a spread or fee. Where SWIFT is used, messages coordinate these handoffs but carry instructions, not funds. In correspondent banking models, settlement may involve multiple banks, which can add time and cost. Banks may also request for additional information about the beneficiary or sender, which can increase time before the transaction reaches its final destination.
The Role of SWIFT in Cross-Border Payments
SWIFT is a messaging network widely used for international bank-to-bank payments. It transmits payment instructions between financial institutions rather than moving or holding the funds itself.
On SWIFT-routed transfers, payments may pass through multiple intermediary banks before reaching the recipient, with each one potentially deducting fees and adding time. Depending on the corridor and intermediary chain, a transfer that might otherwise settle quickly can take several business days.
SWIFT's GPI (Global Payments Improvement) initiative improved tracking and speed, but fees and intermediary friction may remain a real constraint for high-volume or time-sensitive transfers.
FX Quoting Explained: Why Quotes Expire
When a bank or payments provider quotes you an exchange rate, that quote has an expiration window that varies by provider and program. FX markets move continuously, so the rate at the moment of quoting reflects live interbank conditions. If a transaction is not confirmed within that window, the provider may re-price.
If a quote expires before funds are sent, the amount the end user expected to send may no longer match the amount required at the new rate. This can disrupt cash flow and, if the platform still uses the original send amount, change how much the beneficiary ultimately receives for expenses like rent, invoices, subscriptions, or payroll.
This matters for builders because your product needs to handle quote expiry gracefully. Show users a rate, consider locking the quote server-side, and confirming the transaction before the window closes or surfacing a refresh prompt if the quote expires. Product design should also make clear who bears FX repricing risk.
Cross-Border Payment Fees and Cost Structure
Cross-border payment fees can stack up across multiple layers, and teams building for the first time may underestimate the total cost until they are already processing volume. Understanding how these fees can translate into revenue opportunities is covered in the guide to revenues from financial capabilities.
The main fee categories to understand:
- Exchange rate markups can be a significant cost, with banks and intermediaries potentially adding markups above the mid-market rate on currency conversion, which may vary by corridor and provider.
- Transaction fees vary by rail, ranging from flat fees on SWIFT wires to percentage-based fees on card networks.
- On SWIFT payments, fees depend on the charging arrangement. With shared (SHA) or beneficiary pays (BEN), intermediary or receiving-bank fees may reduce the amount received. With OUR (sender pays all fees), the sender is intended to cover those charges.
- Compliance and screening costs may be reflected in pricing depending on the provider, program, corridor, transaction type, and compliance mode.
How Fees Compound Across Rails
The rail you choose directly determines your cost structure. SWIFT transfers may involve multiple correspondent banks, each potentially applying fees or affecting timing. Card network cross-border transactions carry interchange plus a foreign transaction surcharge. Alternative models, including some stablecoin-based flows, may reduce intermediary hops in certain structures, but introduce separate regulatory, sanctions, custody, liquidity, and compliance considerations.
For B2B cross-border payments in particular, the all-in cost often matters more than the headline fee. As an illustrative example, a wire with a flat transaction fee may look inexpensive until FX markup on a large invoice is factored in.
Supported Currencies, Countries, and Restrictions
Cross-border payments operate under a patchwork of currency access rules, country-level restrictions, and compliance requirements that vary by corridor.
Most major services cover the G10 currencies well. Coverage thins out considerably for developing market currencies, where liquidity is lower and regulatory requirements are stricter. Some corridors require local entity presence, beneficiary documentation, or purpose-of-payment codes before a transfer can settle.
Sanctions lists maintained by OFAC, the EU, and the UN restrict or block transactions to certain countries entirely. Availability may also depend on the provider, bank partner, payout partner, currency, beneficiary type, documentation, sanctions rules, local licensing requirements, purpose-of-payment requirements, and transaction type.
Challenges of Cross-Border Payments
Cross-border payments come with friction that purely domestic rails don't face. A few of the most common sources of friction:
- Currency conversion can add cost and unpredictability. Exchange rates may shift between initiation and settlement, and FX costs may be reflected in the spread rather than presented as a separate fee.
- Compliance requirements can be similar or the same across multiple jurisdictions. KYC checks, AML screening, sanctions screening, and local licensing rules may each apply independently, and a gap in any one jurisdiction can hold or prevent settlement of a transaction.
- Settlement times can be slower on legacy rails. SWIFT-based transfers may take multiple business days depending on the corridor, introducing cash flow uncertainty for businesses that need faster finality.
- Intermediaries can add cost. Where correspondent banks are involved, they may apply fees or affect the amount received, making the total cost harder to predict in advance.
What Can Go Wrong: Exceptions and Exception Handling
Even well-designed cross-border payment flows encounter failures. Knowing where they break and how to handle them is what separates a production-grade build from a fragile one.
Common failure points include rejected transactions due to sanctions screening hits, incorrect or missing beneficiary details, correspondent bank refusals, and compliance holds triggered by transaction monitoring rules. Each has a different resolution path and a different clock on resolution time.
Example: A $25,000 payment to an overseas supplier triggers a potential sanctions match. The payment may require additional review, leaving the platform responsible for communicating the delay, tracking the funds, providing additional information if requested, and coordinating with the payment provider until the issue is resolved. While the payment may have been initiated on time, it may not reach the recipient on time causing a delay in their invoice payment.
Exception handling requires:
- Clear ownership of who investigates and resolves each failure type
- Defined SLAs for communicating status back to end users
- A reconciliation process that accounts for funds in transit or held by intermediaries
- Audit trails that satisfy both your compliance team and your banking partners
- Clear responsibility allocation among the platform, provider, bank partner, and any other relevant participant
The overhead here is real. Manual exception handling at scale is where cross-border programs become operationally expensive and difficult to manage. See the Enterprise-Grade Financial Infrastructure Guide for a deeper look at building resilient payment operations.
What to Consider When Building Cross-Border Payouts Into a Product
Regulatory compliance is a critical area to address early. Programs generally need appropriate KYC/KYB, AML, sanctions, and other controls, depending on the payment flow, parties, jurisdictions, and allocation of responsibilities. Gaps in this area may create legal exposure and execution delays.
Currency handling matters more than most teams expect. Program design should make clear when an FX rate is locked, who bears any repricing risk, and how rates and fees are presented to end users. Each of these decisions ties directly into your revenues from financial capabilities.
If the program uses FBO accounts and wallets, their structure is another part of the fund flow and program design to consider.
How Unit Supports Cross-Border Payments
Cross-border payments are a core money movement challenge for fintechs building for global users. Unit can support cross-border payment workflows through applicable payment-provider integrations and related account and money movement infrastructure.1 Choosing a build path on Unit determines how much of that infrastructure you control directly. The cross-border payment lifecycle, including onboarding, FX quoting, counterparty management, and payment execution, can be supported through Unit’s cross-border payments API, subject to product availability and implementation scope.2
For teams building cross-border financial workflows, these factors matter. Settlement timing, compliance handling, and currency conversion each depend on how well your infrastructure maps to the underlying rails and partner integrations. Talk to the Unit team to discuss how cross-border capabilities may fit into your product's financial workflows.
Final Thoughts on Cross-Border Payment Complexity
Each layer of a cross-border payment can add cost, time, or risk, and the teams that build well tend to be the ones who understand where those layers sit. Your rail choice, FX strategy, and compliance setup all connect to what your end users experience. Connect with our team to talk through cross-border payment workflows and available program options.
The content in this article is provided for general informational and educational purposes only and should not be construed as legal, tax, accounting, financial, compliance, or regulatory advice. Unit does not warrant or guarantee the accuracy, completeness, adequacy, or currency of the information provided, and the content may not reflect all considerations relevant to a particular business, product, or use case.
Cross-border payment capabilities, supported corridors, currencies, payment methods, timing, FX rates, and availability may vary by program, provider, bank partner, and jurisdiction.
1 Unit is a financial technology company and is not a bank. Banking services are provided by Unit's bank partner(s), Members FDIC. Unit provides technology infrastructure and platform services, and in certain implementation models program management services to support clients to offer financial products through partner bank programs.
2 Banking and payment services are provided by Unit's bank partners, Members FDIC, and are subject to applicable program terms, eligibility, and approval requirements.
FAQ
What are cross-border payments and how do they work?
Cross-border payments are transfers of funds between parties in different countries, covering B2B supplier payments, B2C marketplace payouts, and C2C remittances. On many corridors, money may move through a chain of correspondent banks where SWIFT messaging is used to coordinate handoffs, with each intermediary potentially applying its own fees and exchange rate before the recipient's bank credits the final amount. This process can take multiple business days on legacy rails, depending on the corridor. Other cross-border payment models may use card networks, local payout partners, account-to-account networks, wallets, or specialized payment providers, depending on the corridor and use case.
What are the real costs of cross-border payments beyond the headline fee?
The true cost can stack across multiple layers: exchange rate markups above the mid-market rate that vary by corridor and provider, per-transaction fees that vary by rail, correspondent bank fees that may be deducted mid-transfer, and compliance screening costs that may be passed through to senders. On a large B2B wire, the all-in cost including FX markup can be significantly higher than the headline transaction fee alone. Actual costs vary by provider, corridor, currency pair, transaction size, transfer method, customer type, and pricing model.
How do I handle FX rate expiry when building a cross-border payments product?
Consider locking the quoted rate server-side the moment a user confirms intent, and build a refresh prompt triggered before or when the expiry window closes. Quote validity windows vary by provider and program configuration, so the UI should be designed to handle expiration gracefully regardless of window length. If your settlement flow runs longer than the lock window, a clear policy on who may bear re-pricing risk is important to define before launch.
What should I get right before building cross-border payouts into my product?
Start by defining your target use case, corridors, currencies, payout methods, and customer types. Then confirm how compliance, FX pricing, fees, settlement timing, exception handling, and reconciliation are handled across the platform, payment provider, and bank partner. Because these requirements can vary by corridor and program structure, establish clear responsibilities and customer expectations before launch.
What currencies and countries are supported?
Currencies supported include: USD, AED, ARS, AUD, BDT, BRL, CAD, CLP, CNY, COP, CZK, DKK, EGP, EUR, GBP, GHS, HKD, IDR, ILS, INR, JPY, KES, KRW, LKR, MAD, MXN, MYR, NGN, NPR, NZD, PEN, PHP, PKR, PLN, SEK, SGD, THB, TRY, TZS, UGX, UYU, VND, XAF, XOF, ZAR
Payout countries supported include: Albania, Algeria, Andorra, Argentina, Armenia, Aruba, Australia, Austria, Azerbaijan, Bahamas, Bahrain, Bangladesh, Barbados, Belgium, Belize, Benin, Bermuda, Bhutan, Bolivia (Plurinational State of), Bonaire, Sint Eustatius and Saba, Bosnia and Herzegovina, Botswana, Brazil, Brunei Darussalam, Bulgaria, Cabo Verde, Cambodia, Cameroon, Canada, Cayman Islands, Chad, Chile, China, Colombia, Cook Islands, Costa Rica, Côte d’Ivoire, Croatia, Curaçao, Cyprus, Czechia, Denmark, Dominica, Dominican Republic, Ecuador, Egypt, El Salvador, Estonia, Ethiopia, Fiji, Finland, France, French Polynesia, Georgia, Germany, Ghana, Greece, Greenland, Guatemala, Guyana, Haiti, Honduras, Hong Kong, Hungary, Iceland, Indonesia, Ireland, Isle of Man, Israel, Italy, Jamaica, Japan, Jersey, Jordan, Kenya, Korea, Republic of (South Korea), Kosovo, Kuwait, Latvia, Lebanon, Liberia, Liechtenstein, Lithuania, Luxembourg, Macao, Malawi, Malaysia, Maldives, Mali, Malta, Mauritania, Mauritius, Mexico, Moldova, Republic of, Monaco, Montenegro, Morocco, Mozambique, Namibia, Nepal, Netherlands, New Zealand, Nigeria, North Macedonia, Norway, Oman, Pakistan, Palestine, State of, Panama, Papua New Guinea, Paraguay, Peru, Philippines, Poland, Portugal, Qatar, Romania, Rwanda, Saudi Arabia, Senegal, Serbia, Singapore, Sint Maarten (Dutch part), Slovakia, Slovenia, Solomon Islands, Spain, Sri Lanka, Suriname, Sweden, Switzerland, Taiwan, Province of China, Tajikistan, Tanzania, United Republic of, Thailand, Timor-Leste, Togo, Trinidad and Tobago, Tunisia, Turkey, Turks and Caicos Islands, Uganda, United Arab Emirates, United Kingdom, United States of America, Uruguay, Uzbekistan, Vanuatu, Viet Nam, Virgin Islands (British), Zambia, Zimbabwe
