Cross-border payments are still slower, costlier and less predictable than domestic ones, and the gap is closing more slowly than regulators intended. Although significant progress has been made in developing policies for cross-border payments, practical implementation continues to lag. Many of the regulatory foundations are already in place, but the underlying payment infrastructure has yet to deliver the intended improvements fully.
For a business selling internationally or paying suppliers abroad, that gap shows up as specific operational problems: fees that erode margin on every corridor, settlement timing you cannot forecast, screening delays that hold up legitimate transactions, and the occasional loss of banking access on a route you depend on. This article sets out what is actually blocking cross-border business payments in 2026, what current data say about cost and speed, and where crypto-based rails genuinely reduce friction rather than shift it elsewhere.
Where cross-border payments still break down
Regulatory fragmentation and duplicated compliance work
Anti-money laundering (AML) and know-your-customer (KYC) requirements differ between jurisdictions, and that variance multiplies the compliance work across every corridor you operate in. The same customer can require different identity documents, different source-of-funds evidence and different transaction reporting formats depending on where the payment lands. The result is manual review, slower onboarding and a higher cost per relationship.
Sanctions screening compounds the problem. Lists, matching thresholds and interpretations are not uniform, so a transaction cleared in one jurisdiction can be flagged in another. The FSB identifies misaligned AML and counter-terrorist financing controls, inconsistent privacy rules, and inefficient implementation of capital controls as frictions still holding back progress. Its joint work with the IMF found that processing capital controls alone can delay crediting funds to a beneficiary by hours or even days, particularly when beneficiary verification or supporting documentation is incomplete.
A shrinking correspondent banking network
Most cross-border bank payments still travel through correspondent banking. Correspondent banking relationships have become increasingly concentrated over time, with fewer institutions handling a growing share of international payment traffic. Rather than reducing payment volumes, this concentration has increased dependence on a smaller number of intermediaries, contributing to operational complexity and reduced resilience across some cross-border payment corridors.
That concentration carries a direct operational cost. Fewer direct relationships mean longer payment chains, and each additional intermediary adds a fee, a handoff and another point at which an exception can occur. Lower-volume corridors and smaller economies have lost the most access, which is why pricing and reliability deteriorate fastest on exactly the routes where alternatives are hardest to find.
Foreign Exchange (FX) spreads and the cost of liquidity
FX is not a single line on an invoice. It combines the bid-offer spread, the margin applied at conversion, the intraday liquidity required to fund positions, and any hedging your treasury conducts. The FSB’s 2025 monitoring found that FX costs remain the largest single component of total retail cross-border payment costs, ahead of the visible transfer fee.
Pricing typically worsens when liquidity is fragmented, which is why less-traded currency pairs often carry wider spreads than major currency pairs. The impact becomes more pronounced when you invoice customers in one currency and pay suppliers in another, as conversion costs can be incurred at multiple stages. Businesses should also account for receiver-side fees and foreign exchange margins, as these can further reduce the final amount received and increase the total cost of cross-border payments.
Settlement speed you cannot forecast
Speed remains one of the biggest weaknesses of traditional cross-border business payments. Many international transfers still take one or more business days to reach the recipient, and settlement times can vary significantly depending on the payment corridor, intermediary banks and local processing rules. This lack of consistency creates delays for businesses that depend on predictable cash flow, particularly when making supplier payments or settling time-sensitive commercial transactions.
Time-zone differences and bank cut-off times compound the delay. The practical consequence for the treasury is that predictable cash flows become contingent. You hold larger buffers, forecast with wider tolerances, and occasionally reschedule supplier payments because a single transfer has stalled somewhere you cannot see.
What the friction costs a business
Margin erosion on international sales
Transfer fees, foreign exchange margins and intermediary charges all reduce gross margins on cross-border sales. For businesses operating with thin margins, even relatively small payment costs can significantly affect profitability and influence whether serving a particular market remains commercially viable. Understanding the total cost of international payments, including currency conversion and intermediary fees, is therefore essential when evaluating cross-border expansion.
Treasury and working capital strain
Uncertain timing lengthens days sales outstanding and forces larger liquidity buffers. Forecasting becomes harder, vendor payment schedules need built-in slack, and capital sits idle, covering timing risk rather than funding growth. This cost rarely appears as a line item, which is part of why it persists. It surfaces as a financing cost and an opportunity cost rather than as a payment fee.
Checkout friction and lost conversions
Slow or failed payments directly cost revenue. Customers who face long confirmation times, declined cards or unfamiliar payment steps abandon purchases and are less likely to return. Where card acceptance rates are weak in a particular market, the loss is not only the transaction but the customer relationship behind it.
Compliance pressure and banking access
Screening, false positives and manual review
Real-time screening tools struggle with false positives and context-dependent name matches. Each false positive consumes analyst time and delays a legitimate payment, and the cost lands either directly on you or in the fees your provider charges.
A structural fix is in progress. FATF revised Recommendation 16 on payment transparency in June 2025, standardising the originator and beneficiary information that must accompany cross-border payments and requiring it to be structured in line with messaging standards such as ISO 20022. Better structured data should reduce false positives over time. Financial institutions are expected to implement the revised standard by the end of 2030, so the benefit is real but not immediate.
De-risking and account access
Banks continue to limit relationships with certain corridors and with businesses connected to crypto activity. In practice, that means longer onboarding, periodic re-underwriting and the possibility of losing an account on a route you depend on. Contingency planning matters here. A second banking relationship, clean documentation of your fund flows, and a transparent account of your compliance controls all reduce the likelihood that a relationship will be terminated on risk-appetite grounds rather than for anything you have done.
Reporting and data requirements across jurisdictions
Selling into multiple markets means multiple reporting formats, tax treatments and thresholds. You may need to file separate transaction reports, collect additional tax documentation, or apply different VAT treatment to the same product depending on the customer’s location. Each variation adds reconciliation work and another opportunity for error.
Infrastructure that is changing slowly
Legacy rails and conditional finality
Traditional payment rails were not built for instant finality. Intermediary banks and net settlement cycles introduce delay, and in some cases, finality is conditional, with reversal possible for a period after the payment appears to have arrived. That uncertainty is why treasury practice around cross-border payments tends to be conservative, and why “the payment has been sent” and “the funds are ours” remain different statements.
Messaging standards after the end of coexistence
The adoption of ISO 20022 is improving the quality of cross-border payment messaging by enabling richer, more structured data than legacy formats. This supports better straight-through processing, more accurate sanctions screening, and more efficient automated reconciliation, particularly as financial institutions continue to modernise their payment infrastructure.
However, the benefits depend on consistent implementation across the payment chain. During periods where institutions or domestic payment systems operate on different migration timelines, differences in messaging standards and incomplete data can still lead to manual investigations, processing delays and reconciliation challenges.
Where central bank digital currencies fit
Central bank digital currencies (CBDCs) are often presented as a solution to cross-border friction. The timelines suggest otherwise. The ECB expects a 12-month digital euro pilot to begin in the second half of 2027, with a potential first issuance in 2029, contingent on the adoption of the digital euro Regulation. The digital euro is also designed primarily as a euro-area retail instrument rather than a cross-border settlement rail.
The wholesale experiments sit closer to the problem. BIS projects such as Agorá, on tokenised central bank and commercial bank money, and Meridian FX, on settling foreign exchange across different infrastructures, address cross-border settlement directly. Still, they remain research initiatives rather than production systems. For planning purposes in 2026, treat CBDCs as a medium-term development rather than an available option.
Where crypto rails reduce friction
Settlement speed and continuous availability
Blockchain networks operate continuously, so a payment initiated on a Friday evening does not wait until Monday’s cut-off. Settlement of the on-chain leg typically completes within minutes rather than days, thereby narrowing the gap between shipping goods and holding usable funds.
Two qualifications matter. Confirmation on-chain is not the same as fiat settlement in your bank account, and if you convert to euros or dollars, the conversion and payout legs carry their own timing. Traditional rails are also improving in parallel. Under the EU Instant Payments Regulation, euro-area banks have been required to send instant euro credit transfers, with funds available to the payee within ten seconds, since October 2025. Within the euro area, the speed argument for crypto rails is now considerably weaker than it is on corridors with limited banking infrastructure.
Liquidity aggregation and execution cost
Liquidity for any single asset or corridor is fragmented across venues. Connecting to multiple liquidity providers and routing each conversion to the best available execution narrows the effective spread and reduces slippage on larger transactions. This is a genuine cost advantage, and it also explains why single-venue execution tends to disappoint. The pricing you achieve depends on the depth you can reach, not on the technology itself.
Reconciliation and programmable payouts
On-chain records are timestamped and immutable, providing a reliable audit trail and a stable reference for each transaction. That helps with reconciliation without completing it, since you still need to map on-chain transactions to invoices, customers, and ledger accounts within your own systems.
Programmability adds something that traditional Rails does not offer easily. Payouts can be released automatically based on defined conditions, such as delivery confirmation or a contractual milestone, thereby removing manual approval steps from vendor payment and escrow workflows.
Keeping the volume figures in proportion
Reported blockchain transaction volumes can be misleading because they often include trading activity, transfers between exchanges and automated on-chain transactions rather than genuine commercial payments. Actual business payment volumes represent a much smaller share of overall blockchain activity, although they continue to grow as more organisations adopt stablecoins for cross-border settlement. Business-to-business payments remain one of the strongest areas of adoption, particularly where faster settlement and lower transaction costs offer a clear operational advantage. Crypto payment rails are therefore well suited to specific use cases and payment corridors. Still, they should be viewed as a complement to traditional banking infrastructure rather than a universal replacement.
Where crypto rails do not solve the problem
On-ramp and off-ramp liquidity
The blockchain leg is rarely the constraint. Converting between fiat and crypto at either end is where cost, delay and execution risk concentrate, and depth varies significantly by asset, currency and market. In corridors with thin local liquidity, an off-ramp can be slower and more expensive than the payment it was meant to accelerate. Plan on-ramp and off-ramp capacity corridor by corridor before committing volume.
Banking acceptance of crypto-derived funds
Banks continue to apply enhanced due diligence to funds with crypto origin, and some decline the business entirely. This affects your ability to move settled funds back into the traditional banking system without friction, and it is worth testing with your own bank before building a process that assumes it will work.
What does adoption require operationally?
Integration and reconciliation
Connecting crypto rails to your systems means handling APIs, webhook endpoints and ledger mapping. Verify webhook retry logic and idempotency handling early, because duplicate settlement events are the most common integration defect. Your enterprise resource planning and reconciliation workflows will need to recognise crypto transactions, conversion rates and settlement timestamps as distinct data points.
Accounting and tax operations
Accurate ledger mapping and timestamped records are the foundation of correct tax treatment in each jurisdiction. Map out accounts for crypto receipts, conversions, and fees before you go live rather than afterwards, and involve your tax adviser early enough so that the record structure supports what they will eventually need to file.
Custody, security and counterparty risk
Private key management and operational security are the highest-consequence decisions in the stack. Many businesses prefer a managed or custodial arrangement precisely because the operational risk of self-custody is difficult to hold internally. If you take that route, assess the provider’s security architecture, insurance cover, segregation of client assets and third-party attestations, and establish what contractual recourse you actually have.
Data protection and audit trails
The GDPR applies to customer data you process in connection with payments, so contractual safeguards, encryption and access controls belong in any provider arrangement involving personal data. Separately, define retention policies and reporting capabilities for transaction monitoring records. You need to be able to reconstruct a case for a regulator or a banking partner, sometimes years later.
How Bitpace fits into this
Bitpace connects to multiple liquidity providers and routes each transaction against price, execution risk and corridor suitability, which is the mechanism behind narrower spreads rather than a claim about them. Settlement can be taken in crypto or automatically converted into EUR, USD, or USDC and paid out to a bank account, so the treasury can decide how much exposure to hold and for how long.
For businesses that would rather not present a third-party brand at checkout, the whitelabel option runs the gateway under your own branding. At the same time, Bitpace handles liquidity, execution, and settlement behind the scenes. Integrated onboarding checks, transaction monitoring, and audit logging reduce the amount of compliance tooling you need to build yourself, and REST APIs and plugins keep the integration work proportionate. Payment service providers can extend the same infrastructure to their own clients through a sub-merchant structure.
Building the case and running a pilot
Map where your corridors actually hurt
Start with data rather than assumption. Identify which corridors incur the highest FX costs, have the longest settlement times, or have the most banking friction, then map them against revenue and margin by corridor. The corridor that irritates your finance team the most is not always the one that costs the most.
Quantify the potential gain
Model the specific effects: reduced days sales outstanding, projected FX saving, and any conversion improvement in markets where card acceptance is weak. Net cash flow improvement and cost per transaction saved are usually enough to justify or reject the project without building a more elaborate business case.
Confirm technical and treasury readiness
Before launch, work through the following:
- API endpoints, webhook configuration, SDK availability and developer documentation
- Webhook retry and idempotency handling, to prevent duplicate settlements
- Settlement policy: which receipts stay in crypto, which convert to fiat, and on what schedule
- Reconciliation steps and timing for netting crypto and fiat positions
- Liquidity buffers for the pilot period, to be reduced as execution certainty improves
Put compliance and accounting controls in place
The controls below should be operational before the first live transaction:
- Onboarding checks with tiered verification and sanctions screening
- Transaction monitoring thresholds and alerting for higher-risk patterns
- Audit trails and reporting configured for regulators and banking partners
- Ledger accounts mapped for crypto receipts, conversions and fees
- Customer-facing content explaining settlement times and payment confirmation
Measure what the pilot actually changed
Set the metrics before you start and give the pilot a fixed end date. Settlement performance is the core measure: time to settlement, the proportion settling within your target window, and the rate and resolution time of exceptions. On cost, compare the average spread, conversion fee and net FX cost per transaction against your incumbent rails on the same corridor. On the customer side, track the international conversion rate and the payment decline rate. On treasury, watch days sales outstanding, liquidity usage, and the compliance false-positive rate, since a fall in manual reviews is often where the operational savings actually land.
Sector applications
E-commerce merchants
Crypto payments reduce chargeback exposure, though not because they settle faster. On-chain transfers are final once confirmed, so there is no card-scheme dispute mechanism through which a payment can be reversed. That removes a category of fraud loss and administrative cost, and it also removes a protection that some customers expect. Refunds become a commercial process you design and communicate rather than a scheme obligation. In markets where card decline rates are high, an alternative rail can also recover revenue that currently fails at checkout.
Payment service providers
PSPs can offer crypto acceptance to their merchant base without having to build and maintain the infrastructure themselves. That shortens time to market and moves the ongoing burden of liquidity management, compliance tooling and rail maintenance to a specialist, which matters most when crypto acceptance is a supporting product rather than the core business.
FX and CFD brokers
Brokers benefit from faster client deposits and withdrawals, which directly affect onboarding conversion and client satisfaction. Access to multiple liquidity sources improves conversion executions, and consolidated reporting reduces the reconciliation load associated with high transaction counts.
Real estate businesses
Payment timing is rarely the longest step in a property transaction, but where funds move across borders, it can be a significant one. Settling the payment leg faster removes a source of delay and shortens the period during which capital is committed but unusable. Legal, registration and conveyancing timelines are unaffected, so the gain is real but bounded.
Benefits and trade-offs
The case for adding crypto rails to your payment mix rests on the following:
- Faster settlement of the on-chain leg, releasing working capital tied up in transit
- Potentially lower cost and narrower spreads where liquidity is aggregated across providers
- Continuous availability, independent of banking hours and cut-off times
- Programmable payouts and timestamped records that reduce manual intervention
- An alternative route on corridors where correspondent banking access has deteriorated
The trade-offs are equally concrete:
- Tax and accounting treatment varies by jurisdiction and requires specialist input
- Banking acceptance of crypto-derived funds remains uneven
- On-ramp and off-ramp liquidity, not the blockchain, sets the real limit on many corridors
- Treasury and accounting teams face a genuine learning curve
- Custody and counterparty risk require active management and periodic review
Where to start
The realistic assessment for 2026 is that cross-border payment friction is structural and will not be resolved by any single development. ISO 20022 will gradually improve data quality. Correspondent banking will keep concentrating. CBDCs remain years away from being relevant to your operations. Waiting for the system to fix itself is not a strategy.
The practical response is narrower. Pick the corridor where cost, delay, or banking access hurts most, quantify the value of a change, and run a bounded pilot with defined metrics before committing further. Favour providers that combine liquidity access, compliance tooling and settlement flexibility, since vendor sprawl carries its own overhead. Keep legal counsel engaged as EU rules continue to move, and document your compliance processes clearly enough that a banking partner can understand them without a meeting.
Start accepting crypto payments with Bitpace’s crypto payment gateway.
Get paid in Bitcoin, Ethereum, Litecoin and many more established cryptos with the Bitpace crypto payment gateway. Reach out now to start accepting crypto payments.
Frequently asked questions about cross-border business payments in 2026
What is blocking cross-border business payments in 2026?
The biggest barriers to cross-border business payments remain regulatory fragmentation, differing AML and sanctions requirements, foreign exchange costs, fragmented liquidity and slow settlement through traditional banking networks. Together, these factors increase payment costs, create operational exceptions, delay settlements and make cash flow more difficult to forecast, particularly for businesses operating across multiple jurisdictions.
Why are correspondent banking relationships declining, and what does that mean for payments?
Banks have gradually reduced correspondent banking relationships over time as rising compliance costs and regulatory obligations have made some lower-volume payment corridors less commercially attractive. For businesses, this often results in longer payment chains, higher transaction costs, more operational exceptions and reduced access to cross-border payment services, particularly in markets with fewer alternative settlement options.
Can crypto rails fix cross-border payment problems?
They address some of them. Crypto rails settle the on-chain leg in minutes, operate continuously and bypass correspondent chains entirely. They do not remove compliance obligations, volatility management or the need for fiat conversion at each end, and on-ramp and off-ramp liquidity is frequently the real constraint. Genuine stablecoin payment volumes remain a small fraction of global payments, so the sensible approach is a targeted pilot on a corridor where the friction is measurable.
How can SMEs reduce FX and liquidity costs on international payments?
Reduce the number of conversions first: invoice in the currency you pay suppliers in where commercially possible, and hold balances in your main trading currencies rather than converting on every transaction. Beyond that, compare providers on total cost, including FX margin, rather than on headline fees; ask specifically about receiver-side charges; and consider platforms that aggregate liquidity to improve execution. Netting and simple hedging can also help where flows are regular and predictable.
