The Cost of a Failed Cross-Border Payment

A failed cross-border payment rarely fails in one simple way.

A payment may be delayed for a compliance review, rejected by a receiving bank, returned because of incorrect beneficiary information or held while an intermediary requests more details. In each case, the original payment instruction becomes an operational case.

The direct cost can be visible. A bank may charge a return or repair fee. The larger cost usually sits across the payment provider’s operations, treasury, compliance and client-support teams.

That matters because delayed payments are not a rare edge case in cross-border operations. The Financial Stability Board reported that, in 2025, 55 percent of cross-border wholesale and remittance payments were credited within one hour of initiation, compared with the G20 target of 75 percent. The gap shows why payment providers still need robust processes for payments that fall outside the expected delivery window. The Bank for International Settlements review of cross-border payment progress outlines the latest results and remaining frictions.

For a payment provider, the useful question is not only whether a payment failed. It is what the failure cost from the first alert to the final resolution.

A payment failure becomes a case

A cross-border wire involves several parties. The originating provider, sending bank, correspondent banks, receiving bank and local payout partner may all contribute data, screening checks and processing steps.

When a payment does not move through that chain as expected, the provider needs to identify where it stopped and why.

Common triggers include incomplete or incorrect beneficiary information, a mismatch between account details and recipient name, sanctions or transaction-monitoring alerts, missing payment-purpose information, local bank cut-off times and currency conversion issues. A payment may also fail because a beneficiary account is closed or restricted, there are insufficient funds in a pre-funded payout account or an intermediary institution requires manual review.

Some issues can be fixed quickly. Others require a payment trace, a request for additional information or a return of funds through the same chain of institutions that handled the original transfer.

The payment is no longer automated. It becomes a case with an owner, a queue, communications and a client waiting for an update.

Direct fees are only the first cost

The most obvious costs are external charges.

These can include repair fees, return fees, recall fees, intermediary charges and local bank fees. A provider may also face FX costs if the payment is returned after the exchange rate has moved.

These charges matter, especially for lower-value transfers where a fixed fee represents a meaningful share of payment value. They are still only one component of the cost.

A $25 repair charge may trigger an investigation involving operations staff, a compliance analyst, a treasury team member and a customer-support agent. The payment provider may also hold local liquidity longer than planned, issue an update to the client and monitor the case until funds arrive or return.

SWIFT estimated in April 2025 that delayed-payment investigations cost the financial industry around $1.6 billion annually. Its research suggested that more standardised case management and end-to-end tracking could reduce operational and liquidity costs by more than $600 million each year. SWIFT’s 2025 announcement on payment investigations highlights the scale of the overhead.

Measure the work behind every exception

Payment providers need to measure the time spent on an exception, not only the bank fee attached to it.

A useful starting point is to map every team involved in a failed payment:

• Payments operations checks the transaction status and begins the investigation
• Compliance reviews alerts and requests any missing information
• Treasury confirms available balances and monitors the impact on funding
• Customer support responds to the client and follows up on promised delivery
• Finance reconciles returned funds, fees and potential FX differences
• Product and engineering investigate recurring data or routing problems

The exact workflow varies by provider. The principle is consistent. Each handoff consumes time and creates a risk that the client receives incomplete, inconsistent or delayed information.

A practical calculation is:

Internal exception cost = total staff time spent on payment exceptions × fully loaded hourly cost

For example, a returned wire might require:

• 25 minutes from payments operations
• 20 minutes from customer support
• 15 minutes from treasury
• 10 minutes from compliance
• 10 minutes from finance

That is 80 minutes of total work.

If the blended fully loaded cost for the relevant team is $45 per hour:

80 minutes ÷ 60 = 1.33 hours
1.33 hours × $45 = approximately $60 in internal labour cost

Add a $25 bank return fee and the direct cost becomes $85, before accounting for FX movement, retained liquidity, client remediation or lost future volume.

The actual number will differ between providers. The framework makes the cost measurable.

Treasury carries the timing risk

A payment exception can also disrupt treasury planning.

If a provider expects a payment to settle and replenish a local balance, a delay may leave less available liquidity than forecast. The treasury team may need to move funds through another route, retain a larger safety buffer or delay a planned reallocation of capital.

A returned payment creates a different issue. The provider may not know exactly when the funds will arrive back, whether fees will be deducted or whether the returned amount will match the original value after conversion.

This uncertainty affects the way a provider manages pre-funded balances.

For example, a provider may normally need $1 million to support local payouts in a corridor. If payment exceptions and uncertain returns occur regularly, the treasury team may hold an additional $200,000 or $300,000 to avoid a payout shortfall.

That buffer has a cost.

Annual funding cost of an exception buffer = additional balance held × annual cost of capital

If a provider holds an additional $250,000 at an 8 percent cost of capital:

$250,000 × 8 percent = $20,000 in annual funding cost

The earlier article on capital tied up in cross-border payouts explains why replenishment time and payment uncertainty can increase the capital required to support a corridor.

A payment provider should therefore track exception-related funding separately from normal operating liquidity. It reveals whether a corridor needs a larger balance because of genuine customer demand or because payments are difficult to predict.

Support cost is part of payment cost

Clients do not separate an operational failure from their payment experience.

They want to know whether the recipient has been paid, where the money is and when the issue will be resolved. A support request may begin with a simple status question, then develop into several exchanges involving the client, recipient and internal payments team.

Track support contacts per 1,000 payments, the average number of client contacts per exception, average time to first response and average time to close a case. It is also useful to measure the share of exceptions requiring manual client outreach, along with client refunds, fee reversals or goodwill credits.

These figures help the provider see the full effect of payment failures. A low rate of returned wires may still be expensive if each case requires several hours of investigation and repeated client updates.

Payment tracking is especially important. The Financial Stability Board’s cross-border payments work identifies expected delivery time, payment-status tracking, total transaction costs and terms of service as key information that providers should give to customers. Its 2025 G20 Roadmap report sets out these transparency expectations.

A clear status update will not solve an underlying payment issue. It can reduce the number of avoidable contacts and help client-facing teams provide a consistent response.

Identify repeat causes

The purpose of measuring payment failures is to reduce them.

A provider should classify exceptions by cause, corridor, partner, payment type and client segment. This makes recurring patterns visible.

Examples include:

• A local bank that frequently rejects payments with a particular reference format
• A client group that regularly submits incomplete beneficiary information
• A corridor where payment-purpose codes are often missing
• A payout route with slow handling of compliance reviews
• A time of day when payments miss a local processing cut-off
• A currency pair where delayed conversion creates repeat funding pressure

Once a provider can see these patterns, it can decide which changes are worth making.

Some fixes are simple. Better input validation can prevent incorrect account details from entering the workflow. Clearer client guidance can reduce incomplete payment information. Improved routing rules can avoid known cut-off risks.

Other issues need a structural response. A corridor may require a different local partner, stronger pre-funding controls or a new settlement process.

The goal is to distinguish between exceptions that can be prevented at the point of instruction and exceptions that are inherent to the route.

Compare the full settlement outcome

Stablecoin-supported settlement can reduce some sources of payment uncertainty. It can provide a more direct transfer path, faster transaction confirmation and clearer on-chain visibility for the value-transfer leg.

It does not remove every failure mode.

A payment can still be delayed by screening, incorrect wallet details, unsupported networks, constrained local liquidity, off-ramp availability or a failed local payout. The client still needs usable funds in the destination market.

The comparison should therefore focus on the full payout outcome. Measure the percentage of payments completed within the promised window, the exception rate by corridor and the average time to resolve an exception. Teams should also calculate internal labour cost and external fees per failed payment, track liquidity held because of settlement uncertainty, monitor support contacts per 1,000 payments and record client credits or refunds caused by service issues.

The recent Gravity Team article on payment reliability and stablecoin settlement provides context on how settlement paths can affect payment operations.

A provider should run this comparison using its own payment data. The cost of an exception varies greatly by corridor, payment type and local payout setup.

Build an exception-cost dashboard

A practical dashboard does not need to be complicated. It should give treasury, operations and product teams a shared view of the payment failures that matter most.

For each corridor, track:

‍

‍

Review this data monthly and after major changes to a corridor.

The most valuable insight is often not the overall exception rate. It is the small number of recurring causes that generate the largest operational burden.

Treat failed payments as a margin issue

A failed payment is a service problem. It is also a margin problem.

When a provider prices a cross-border route, it should include the expected cost of exceptions. If 2 percent of payments require manual work, the cost of those cases is part of the route’s underlying economics.

For example, a provider processing 100,000 payments annually with a 2 percent exception rate handles 2,000 exceptions. If the total average cost is $85 per case:

2,000 exceptions × $85 = $170,000 annual exception cost

Reducing the exception rate from 2 percent to 1 percent would reduce the annual cost by around $85,000, assuming the same volume and cost per case.

That saving could support better pricing, additional operations coverage or a stronger service-level commitment.

Payment providers cannot eliminate every exception. They can make the cost visible, identify the causes and design payment flows that create fewer avoidable failures.

Glossary

Exception: A payment that cannot continue through normal automated processing and requires manual review, correction or investigation.

Payment repair: Changes made to a payment instruction so that it can be processed after a data, format or compliance issue.

Payment return: Funds sent back to the originator because the payment could not be completed.

Pre-funding: Holding funds in advance in a destination market to ensure local payouts can be completed on time.

Reconciliation: Matching payment records, account balances, fees and settlement outcomes to confirm that transactions have been correctly processed.

Straight-through processing: Automated payment processing without manual intervention.

Visual brief: Show one delayed cross-border payment branching into repair fees, operations time, treasury buffers, compliance checks and client-support contacts to illustrate its full cost.

‍