Optional cookies require your permission.Privacy & cookies

Your account works. Why did the international transfer fail?

A bank may keep the customer’s account open while a correspondent declines an international payment. First establish where the transfer stopped and whether the funds were returned.

Adam Juchniewicz, CEO, Bitcoin Lawyer10 min read
Sources cited in this essay (2)
Banking district façades face a wide intersection lined with stone financial buildings.
In this essay10 sections
  1. Your bank is one part of the route.
  2. De-risking describes a cause, not every delay.
  3. Separate a document problem from a route problem.
  4. Reconcile the first transfer before replacing it.
  5. A failed contribution payment needs two separate decisions.
  6. Design alternatives around real obligations.
  7. Test independence with an actual payment requirement.
  8. A Bitcoin transfer changes one dependency.
  9. Preserve the lesson without overgeneralizing the incident.
  10. The Bitcoin Lawyer take

Your bank is one part of the route.

A company has an active account and an agreed invoice. Its international transfer is delayed, then returned. The immediate reaction is to resend it or open another account. Neither action identifies what happened to the first payment. The problem may concern the sender, the recipient, an intermediary, the currency route, or a missing reference.

Correspondent banking allows one bank to obtain services from another. The FSB’s explanation of FATF guidance describes its importance to international payments and the additional due-diligence responsibilities around cross-border relationships. A customer can therefore depend on an institution that does not appear on the front of their account statement.

Ask the sending bank for the status and any reference or return information it can provide. Distinguish an instruction not yet executed from money sent, a review in progress, a returned payment, and a credit that the beneficiary cannot yet use. Those states create different next steps and different duplicate-payment risks.

De-risking describes a cause, not every delay.

A bank may narrow or end relationships because the commercial return, compliance work, and risk no longer fit its model. That can affect an entire payment route. It does not follow that every customer on the route has done something wrong. Equally, a delayed transfer does not prove a correspondent withdrawal.

The World Bank’s September 2025 Pacific account describes the difficulty small markets face when correspondent links decline and the collective work needed to preserve them. It is evidence of a structural challenge in that region, not proof that a named bank or country cannot process your transfer today. Current availability belongs in a current provider check.

Ordinary explanations remain possible: incomplete beneficiary information, a sanctions-name review, a purpose question, operational cut-offs, or an instruction error. Record the bank’s explanation without replacing it with a more dramatic one. Where the reason remains undisclosed, write “not confirmed” rather than classifying the event as de-risking.

Separate a document problem from a route problem.

If the bank requests a sale agreement or source-of-funds explanation, the next step concerns evidence. Send the requested material through its authenticated channel and connect it to the payment reference. A coherent response should identify the parties, amount, purpose, and underlying economic event without asking the reviewer to reconstruct the entire file.

If the bank confirms that the relevant currency or intermediary route is unavailable, an extra statement cannot restore the infrastructure. Ask what alternatives the bank can actually support. Those might involve a different currency or recipient account, but any change needs the beneficiary’s authenticated agreement and a clear account of conversion costs and net receipt.

Do not split an amount to escape review, use an unrelated payer to obscure ownership, or rename the purpose to fit a payment field. If the proposed alternative changes the payer, beneficiary, asset, or economic arrangement, revisit approval and documentation before execution. A technically possible route is not necessarily an authorized one.

Reconcile the first transfer before replacing it.

Preserve the original invoice, instruction, bank debit, payment reference, and every subsequent status message. Ask whether the instruction can still complete, has been recalled, or has definitively returned. A request to recall is not proof of return. The beneficiary should know that reconciliation is underway before another payment is initiated.

When funds return, compare the credited amount with the original debit. Record fees, currency conversion, and any shortfall without assuming the beneficiary has accepted them. An expired invoice or changed exchange rate may require new written instructions. Keep the first and replacement payments separately identifiable even when they settle the same commercial obligation.

A request to send again while the first amount remains unresolved deserves particular care. Confirm the contractual deadline and obtain an agreed treatment of possible duplicate receipt. Do not allow a ticking invoice screen to substitute for knowing where the money is. If the institution cannot establish the status, escalate through its formal support process.

A failed contribution payment needs two separate decisions.

Consider a fictional applicant, Marco, whose bank debits a dollar payment on Monday. The intended recipient reports no credit on Wednesday. An intermediary requests the payment purpose on Thursday. The application’s funding deadline falls the following week. Marco now faces both an unresolved transfer and a deadline. Treating them as one problem encourages a rushed second payment before anyone knows whether the first can still arrive.

The first decision concerns the existing instruction. Marco asks his bank for the available status, the information requested, the payment reference, and the process for escalation. He provides the underlying instruction and supporting records through the bank’s authenticated channel. He does not assume that a debit proves receipt or that the recipient’s empty account proves the money is already returning.

The second decision concerns the deadline. The authorized recipient needs to know the supported facts and decide whether an extension, revised instruction, or other arrangement is available. That is a contractual or program question for the responsible party. A customer-service representative at the sending bank cannot promise that the citizenship authority will treat a delayed transfer as timely.

Suppose Marco requests a recall on Friday. A recall request is still an action in progress. If he immediately sends another payment, both may arrive or one may remain tied up. The family could temporarily lose access to twice the intended amount. Before replacing the transfer, he needs a documented understanding of the first payment’s state and how any duplicate receipt would be handled.

If the first payment returns, the arithmetic is another task. An invented original debit of $100,000 followed by a $99,940 return leaves a $60 difference to explain. The return does not discharge the original $100,000 obligation. If a replacement uses another currency, the parties also need agreement on conversion, fees, and the amount that counts as settlement. Preserve the debit, return, and replacement as separate events.

Design alternatives around real obligations.

A useful continuity plan starts with the payments that matter: salaries, taxes, living expenses, suppliers, and an exceptional contribution or investment. Identify the currency, permitted payer, recipient, and tolerable interruption for each. Two account logins do not guarantee two independent routes if both depend on the same intermediary or service provider.

Where practical, establish a second lawful arrangement before a deadline makes the choice urgent. Confirm the customer profile, intended counterparties, supported funding sources, and withdrawal method. Maintain the evidence needed to use it. An unused account with stale identity information is a weak fallback when a payment has already failed.

Keep operating liquidity available for essential obligations within the risk limits you have chosen. Avoid moving the same money through several institutions simply to make it look conventional. Every additional transfer adds records and possible review. Resilience should make the economic explanation easier to follow, not harder.

Test independence with an actual payment requirement.

Two banks can offer different interfaces while depending on the same foreign institution for a particular currency. A bank and a payment application may also rely on the same underlying banking partner. The account count therefore tells you less than the dependencies relevant to the payment you need to make. Ask what the provider can confirm, while recognizing that it may not disclose every operational relationship.

A useful fictional business test is a monthly payroll in local currency and an annual dollar supplier payment. Losing a dollar correspondent may interrupt the supplier payment while leaving local payroll functional. Losing access to the business’s only authorized signer could interrupt both. The first problem concerns routing; the second concerns authority. Buying another financial product without identifying the failure would be an expensive way to remain exposed.

Assess the fallback before funding it. Does the account permit this business activity and payer? Can it receive the asset you intend to use? Are transfer limits sufficient? Can an authorized person access it during travel or illness? What documents need refreshing? These are practical acceptance questions for the institution, not assumptions that follow from a successful online registration.

Choose an affordable reserve for obligations that cannot wait. Holding extra operating cash has a cost and creates institution exposure of its own. The amount should reflect the interruption the household or business can withstand, rather than a universal number of months. Review the arrangement when revenue, suppliers, currencies, or residence change.

A Bitcoin transfer changes one dependency.

An on-chain Bitcoin payment can reach an agreed wallet without the same chain of correspondent banks. Whether that solves your particular obligation depends on the recipient’s acceptance, the permitted asset, source-of-funds clearance, and contractual acknowledgment. It does not answer what happens when either party later needs fiat or services from a regulated institution.

Stablecoins introduce a separate issuer and network analysis. A transfer working on-chain does not establish redemption access, account eligibility, or freedom from issuer controls. The proposed recipient must confirm the exact asset and network, and the person paying must check the restrictions applicable to that use. No payment technology removes the need for accurate identity and provenance.

We can help you tell an evidence problem from a settlement dependency and put the right questions to the institutions involved. We cannot reopen a correspondent relationship or guarantee that a payment executes. A change of payment method should be a documented response to an actual constraint, with a preserved receipt at the end.

Where a proposed Bitcoin payment is accepted, confirm what establishes discharge of the obligation. A transaction identifier shows an on-chain event; the recipient’s receipt connects that event to the invoice. Preserve both. If conversion or onward remittance is part of the arrangement, identify the party responsible and the point at which its obligation is complete. A working network is valuable, but it does not settle a disagreement about the agreed payment terms.

Preserve the lesson without overgeneralizing the incident.

After the obligation is settled, record what the available evidence actually established. If a missing beneficiary reference caused the return, fix the instruction process. If the bank confirmed a currency restriction, review that dependency. If the reason remained undisclosed, preserve the unresolved status rather than turning a suspicion into a public claim about the bank or jurisdiction.

Marco’s next payment can benefit from advance notice, current documents, and authenticated instructions. It still needs its own confirmation. A transfer that worked six months ago does not prove the same route will remain available, while a one-off delay does not establish that the route has permanently closed. Refresh the facts close enough to the obligation for the information to be useful.

For recurring payments, decide who monitors changes and who may approve a replacement route. A business owner traveling without access to the normal signatory can otherwise become the weakest dependency. Keep escalation contacts and records available to the people with authority, using appropriate access controls. Continuity is partly financial infrastructure and partly the ability to make a correct decision when the usual person is unavailable.

The whole picture

The Bitcoin Lawyer take

Obtain the original payment reference and a reliable status from the banks involved. Make a replacement transfer only when the first payment’s position and the recipient’s instructions are clear.

Build continuity around actual obligations, authorized payers, and usable alternatives. Bitcoin may remove one correspondent dependency for an accepted payment, while a local bank remains necessary for another. The strongest arrangement explains the money clearly and remains affordable to maintain when nothing has gone wrong.

Cite this essay

Adam Juchniewicz, CEO, Bitcoin Lawyer. “Your account works. Why did the international transfer fail?” https://www.bitcoinlawyer.com/journal/correspondent-banking-payment-failures