When businesses face international payment problems, daily operations can quickly grind to a halt. The global banking system moves huge sums every day, yet payments still get stuck, rejected, or arrive short.
Incorrect beneficiary data is one of the most common reasons international payments fail. This diagnostic guide identifies the exact root causes of common payment issues. It also provides actionable steps to recover your funds and prevent future failures using modern B2B payment solutions.
Key Takeaways
- Many payment failures start with simple typos in beneficiary details or SWIFT codes.
- Recovering a failed international wire can take several business days.
- Banks on SWIFT gpi can track payments end to end, so your bank can often see where a wire is held.
- Intermediary bank fees and hidden FX markups (often 2% to 4%) are the primary reasons payments arrive short.
- Local payment rails can help you avoid long correspondent chains.
The 6 most common international payment problems (and what causes each)
Cross-border payment issues occur for several predictable reasons. Identifying the root cause is your first step toward resolution.
- Incorrect beneficiary data: Typographical errors in account numbers or SWIFT codes are a leading cause of payment failures. For instance, inputting “LTD” instead of “Limited” causes the receiving bank’s automated compliance system to reject the transaction instantly.
- Compliance and AML flags: Transactions touching high-risk jurisdictions or sanctioned entities trigger immediate manual reviews. Depending on the corridor, these compliance holds can freeze funds for 5 to 10 business days while officers verify commercial invoices.
- Correspondent bank bottlenecks: SWIFT payments bounce through multiple intermediary banks. If a payment routes through a low-liquidity corridor (e.g., sending USD to a regional bank in Vietnam), it sits in a queue until the correspondent bank secures the necessary funds, adding 2 to 3 days to the timeline. By understanding how long a SWIFT payment takes, treasury teams can anticipate these specific corridor delays.
- Currency conversion failures: If the receiving account does not support the inbound currency, the bank forces an immediate conversion. If the bank lacks the liquidity or the daily FX threshold is breached, the payment fails entirely.
- Missed cut-off times: Different banking jurisdictions operate in entirely different time zones. Missing a 3:00 PM cut-off in New York on a Friday means a payment destined for Asia will not even begin processing until the following Monday.
- Hidden intermediary deductions: Shared (SHA) billing codes allow intermediary banks to deduct processing fees directly from the principal amount. Consequently, the final delivery falls short of the invoiced total, causing massive reconciliation issues.

Why international payments get delayed: diagnostic table
You can use this comparison matrix to identify your specific issue and find the right fix.
Diagnostic matrix
| Symptom | Most Likely Cause | Urgency | Who to Contact | Fix |
|---|---|---|---|---|
| Delayed 2 to 3 Days | Normal SWIFT routing or missed cut-off. | Low | Sender | Request MT103 document. |
| Funds Frozen | Compliance/AML manual review triggered. | High | Sending Bank | Provide commercial invoice. |
| Short Delivery | Intermediary bank deducted processing fees. | Medium | Both Banks | Change instruction to “OUR”. |
| Payment Returned | Incorrect account or SWIFT details. | High | Sender | Correct the details and resend. |
What to do when your international payment has not arrived
When a payment misses its expected settlement window, you must act systematically. Here are three steps to trace a missing wire.
Step 1: Request the MT103 document
First, ask the sender to provide the MT103 document from their bank. Specifically, the MT103 is a standardized SWIFT payment message that acts as a definitive digital receipt. It proves the bank actually released the funds. Furthermore, without an MT103, the payment likely never left the sender’s account, meaning the delay is entirely on their end.
Step 2: Verify the payment details
Next, review the MT103 closely. Check the beneficiary name, account number, and SWIFT code against your invoice. As a result, a single transposed digit guarantees the receiving bank will hold the funds in a suspense account.
Step 3: Initiate a formal SWIFT trace
Finally, if the details are perfectly correct, instruct the sending bank to open a formal SWIFT trace. If the payment went through SWIFT gpi, the bank can use the gpi tracker to see which intermediary institution is holding the funds and why.

Why international payments are rejected or returned
A failed payment is frustrating, but understanding the timeline gives you a clear path to a fix. There is a meaningful difference between a rejection and a return, and that difference determines exactly what you do next.
Rejections happen instantly. The sending bank’s automated system stops the transfer before it even leaves the building because of a structural error, such as an invalid routing number or an unsupported currency format.
Returns happen days later. The funds successfully travel through the correspondent network and reach the destination bank, but that bank refuses to credit the account. This occurs due to compliance flags, name mismatches, or closed accounts. When a bank returns a payment, the funds reverse through the exact same correspondent chain. Unfortunately, you lose money on currency conversions twice, alongside original processing fees.

Why payments arrive with the wrong amount (and how to prevent it)
Short payments create massive reconciliation headaches for finance teams. Consequently, indeed, this issue arises entirely from two distinct financial traps: intermediary fees and forced FX markups.
First, when initiating a wire, senders choose a billing code: BEN, SHA, or OUR. Specifically, if the sender selects SHA (Shared), intermediary banks deduct their processing fees (typically $10 to $30 per bank) directly from the principal amount during transit. Therefore, a $10,000 payment might arrive as $9,960. To prevent this, always instruct the sender to use the OUR billing code, forcing the sender to cover all fees upfront.
Second, if a payment arrives in a currency different from the destination account’s native currency, the receiving bank applies a forced exchange rate. Legacy banks typically hide a 2% to 4% margin inside this conversion.
To eliminate both intermediary fees and hidden FX markups, global businesses should explore the best SWIFT alternatives, specifically platforms with clear pricing and no FX markup on major currencies.

Best practices when choosing a payment infrastructure
Choosing the right infrastructure guarantees smooth operations. Therefore, finance teams should actively demand transparent, modern capabilities during procurement.
Demand transparent, mid-market FX rates from your provider. If a platform cannot show you the live mid-market rate alongside their applied rate, they are extracting a hidden margin. Furthermore, businesses must require multi-rail access. Specifically, relying exclusively on SWIFT for every transaction guarantees you will overpay on fees and experience maximum settlement delays. Modern infrastructure must provide localized routing options.
How different payment models (and their costs) scale
When businesses scale their international operations, they must evaluate how different payment infrastructure models apply fees to high-volume B2B transactions.
For example, network intermediaries like Wise and Airwallex offer excellent local rail access across dozens of currencies. However, their pricing relies on percentage-based transaction models. Wise applies a variable transfer fee that depends on the corridor, while Airwallex adds an FX markup on many cross-border conversions.
While highly transparent, this percentage-based model scales linearly with your volume. For a business processing $100,000 monthly, even a small percentage margin adds up to thousands of dollars a year.
Similarly, robust domestic accounting tools like Bill.com excel at internal workflow automation. Bill.com charges a flat fee for each international wire sent in USD, on top of monthly subscriptions, and USD wires can still face intermediary bank deductions and correspondent delays.
To scale profitably, more B2B treasuries are moving to infrastructure with clear, published FX pricing and local payout networks, so high-ticket invoices are less exposed to intermediary deductions.

How to build a payment setup that prevents these problems
Prevention is always cheaper than recovery. Ultimately, the right infrastructure removes many common causes of payment failure.
Prevention checklist
| Problem Type | Prevention Step | Frequency |
|---|---|---|
| Data Errors | Use digital click-to-pay invoices to automate details. | Ongoing |
| Short Payments | Ask clients to pay in USD to your named USD account details. | Ongoing |
| Compliance Holds | Digitally attach commercial invoices to every payment. | Ongoing |
| SWIFT Delays | Use local payout rails where possible. | One-Time Setup |
How Bancoli solves international payment problems
Bancoli is built to help businesses avoid common causes of international payment problems. Rather than relying only on the correspondent banking network, Bancoli gives businesses ACH, RTP, US domestic wire and stablecoins from one dashboard.
When you pay a supplier abroad, Bancoli sends a local payout in their currency, which helps avoid deductions by intermediary banks.
Combined with free FX in 25+ currencies and named USD account details, available on every plan, including Free, once verified, Bancoli turns international payments from a frustrating bottleneck into a predictable part of your growth. Banking services are provided by regulated providers, including Bancoli’s affiliated chartered bank. You control your funds. Bancoli does not own or control them. Smart USD is not a deposit and is not FDIC-insured.

Frequently Asked Questions
How long should I wait before reporting a missing international payment?
You should wait at least three full business days before filing a formal report. Moreover, traditional SWIFT payments take two to five days to settle under normal conditions. Weekends and international banking holidays pause the process completely. However, if five business days pass without delivery, you must request an MT103 document and initiate a formal trace immediately.
Can an international wire transfer be cancelled after it is sent?
Generally, no. Furthermore, once a wire clears the sending bank’s compliance filters and enters the SWIFT network, it becomes extremely difficult to recall. While you can issue a formal SWIFT Recall Request, it is merely a request. If the receiving bank has already deposited the funds into the beneficiary’s account, they cannot reverse the transaction without the beneficiary’s explicit permission.
Why does my international payment arrive with less money than expected?
Payments arrive short because intermediary banks take a cut. Specifically, when funds travel through correspondent banking networks, each middleman institution deducts a processing fee, typically between $10 and $30. If the sender used the “SHA” (Shared) billing code, these fees come directly out of the principal amount. For this reason, to prevent this, senders must use the “OUR” billing code to cover all fees upfront.
What does “payment returned beneficiary details incorrect” mean?
This error means the receiving bank rejected the transfer due to a data mismatch. Specifically, often, the account number provided does not perfectly match the corporate name registered to that account. For example, if you send money to “Acme Corp” but the account is registered as “Acme Corporation LLC,” the bank will hold or return the funds to prevent potential fraud.
Who is responsible if an international payment goes to the wrong account?
The sender bears the ultimate responsibility. Indeed, if you input the wrong account number and the bank processes the wire, the funds are legally transferred. While banks will attempt a “best efforts” recall to retrieve the money, they offer no guarantees. Therefore, finance teams must implement strict verification protocols, such as sending test micro-deposits, before executing large transfers to new vendors.
How do I file a claim for a stuck or lost international wire transfer?
To file a claim, you must contact the sending bank’s wire or treasury department directly. Specifically, provide the Federal Reference number or the MT103 document. Then, formally request a “SWIFT trace.” The bank must investigate the case. If it is not resolved, escalate the claim with your account manager or the bank’s complaints team.
What is the difference between a payment rejection and a payment return?
A rejection happens instantly. The sending bank’s system stops the transfer before it even leaves because of an obvious error, such as an invalid SWIFT code. Conversely, a return happens later. The funds travel through the network, reach the destination bank, and then the destination bank refuses them. Returns take longer to process and cost you money in lost FX margins and processing fees.