International Payment Returned: Why It Happens and How to Prevent It

Your international payment was sent. Then, a few days later, the money is back in your account — often with fees deducted.

If you've ever seen a “payment returned,” “payment rejected,” or “payment failed” message while paying an overseas supplier, the problem may be more specific than it looks.

A payment can be rejected before settlement, returned after settlement, or held because the receiving bank needs more information. The reason determines what you should do next.

This guide explains why international business payments are returned, what common ISO 20022 return codes mean, how to fix a returned payment, and how businesses can reduce payment failures when paying suppliers or collecting from overseas customers.

A returned payment usually means the payment could not be completed as originally instructed and the funds have been sent back through the payment chain.

The first thing to establish is where in the payment process the problem occurred.

Under ISO 20022:

• Reject: the payment instruction is rejected rather than completed.

• Return: funds that have already been settled are sent back.

Swift's guidance specifically distinguishes pacs.002 payment-status/reject messages from pacs.004 payment-return messages. A pacs.004 return also carries information about the original transaction and its return reason.

That distinction matters because a returned payment may already have travelled through several financial institutions before coming back.

The most common reasons include:

1. Incorrect account details

2. Closed or blocked beneficiary account

3. Beneficiary information does not match

4. Missing or inconsistent payment information

5. Insufficient funds or amount-related issues

6. Compliance or regulatory restrictions

7. Payment-route or currency restrictions

8. Incorrect payment purpose or supporting documentation

A return is therefore not necessarily a sign that the payment method itself is broken. Often, the payment cannot be processed because the information attached to the payment does not satisfy the requirements of the next bank in the chain.

If your bank gives you an ISO 20022 return reason code, don't ignore it.

The code can tell you whether you need to correct the beneficiary details, check the amount, provide more information or contact your bank about a regulatory issue.

Return code	What it generally means	What to check
AC01	Incorrect account number	Account number / IBAN
AC04	Account closed	Ask supplier to confirm active account
AC06	Account blocked	Contact beneficiary bank
AM04	Insufficient funds	Available balance and payment amount
AM05	Duplication / duplicate payment	Check whether the payment was already processed
BE01	Incorrect beneficiary information	Beneficiary name and account details
BE04	Invalid creditor address	Beneficiary address information
RR03	Missing or invalid regulatory information	Payment purpose / required data
RR04	Regulatory reason	Contact the bank or payment provider

The exact meaning and handling of a return code depends on the payment flow and the institutions involved. ISO 20022 return/reject codes are maintained as external code sets, while Swift's payment-return guidance explains how the codes are carried through the return process.

The practical rule: get the return code before you send the payment again.

1. Find the exact return reason

Ask your bank or payment provider for:

• Return reason code

• Return date

• Returned amount

• Currency

• Any intermediary-bank message

• Original payment reference or UETR

Do not rely on a generic status such as “payment failed.”

A specific return reason can turn a multi-day investigation into a simple correction.

2. Verify the beneficiary details

Ask your supplier to confirm the payment details independently.

Check:

• Legal business name

• Account number or IBAN

• Bank name

• SWIFT/BIC

• Bank country

• Currency

• Beneficiary address

• Payment purpose

• Invoice number

Do not copy a new bank account directly from an unexpected email.

If bank details changed shortly before the payment was returned, verify the change through a trusted channel.

3. Check whether the payment was actually returned

A payment that is “missing” is not necessarily returned.

Ask:

Was the payment rejected, returned, held for review, or successfully credited but not yet reconciled?

These are four different situations and require different actions.

If the payment has been returned, confirm the net amount received back. Intermediary and bank fees may mean the returned amount is lower than the amount originally sent.

4. Correct the underlying problem

For example:

AC01 — incorrect account number

→ Get the correct account details and resubmit.

AC04 — account closed

→ Ask the supplier for an active account and verify it independently.

BE01 — beneficiary information problem

→ Make sure the beneficiary name and account information match the receiving bank's records.

RR04 — regulatory reason

→ Do not simply resend the payment. Ask the bank what information or documentation is required.

5. Resend only after the issue is resolved

This sounds obvious, but it is one of the easiest ways to create a duplicate payment.

Before resending, confirm:

Original payment = returned
Reason = identified
Beneficiary details = verified
New payment = approved

Keep the original return record for reconciliation and audit purposes.

How Long Does an International Payment Return Take?

There is no universal return time.

A payment may be returned quickly when an error is detected early, while a payment that has travelled through several financial institutions can take longer to investigate and reverse.

Swift has highlighted the operational cost of payment investigations: around 2–5% of payments generate an enquiry, and investigations can take five to ten working days in some cases. Swift has also estimated that the industry spends more than US$1.6 billion annually on payment investigations.

That is why prevention matters.

For a business, the real cost of a returned payment is not only the bank fee.

It can also mean:

• Delayed production

• Missed shipment dates

• Supplier follow-up

• FX conversion losses

• Reconciliation work

• Additional bank fees

• Working-capital disruption

The easiest return to resolve is the one you never create.

1. Verify beneficiary details before every first payment

For a new supplier, independently confirm:

• Account number

• Bank name

• SWIFT/BIC

• Beneficiary legal name

• Payment currency

For recurring suppliers, maintain an approved beneficiary list and require additional verification whenever bank details change.

2. Use complete payment information

As international payment systems move further toward structured ISO 20022 data, incomplete or inconsistent payment information can create avoidable exceptions.

Swift has published guidance focused specifically on improving data quality in payment messages, including structured party and address information.

For businesses, that means keeping supplier records consistent across:

ERP → invoice → payment instruction → beneficiary bank

3. Match the payment currency to the supplier's requirements

If a supplier expects CNY but receives a payment routed through an intermediary in another currency, additional conversion or bank processing may be required.

Before sending, confirm:

• Invoice currency

• Payment currency

• Supplier's receiving currency

• Whether the receiving bank accepts that currency

• Who bears conversion and bank charges

4. Reduce unnecessary intermediary-bank steps

Traditional international wires may involve correspondent or intermediary banks.

Every additional institution can introduce another point where:

• Payment data is checked

• Fees are deducted

• Compliance screening occurs

• Currency is converted

• A payment may be delayed or returned

For recurring B2B payments, using local payment infrastructure where available can reduce this complexity.

There is no payment method with zero failure or return risk.

The risk simply looks different depending on the payment method.

Payment method	Common failure / return issue	Best suited to
International bank wire / T/T	Incorrect account details, intermediary issues, compliance checks	Large or established supplier relationships
Local payment rail	Local account or beneficiary issues	Recurring payments within supported markets
Letter of credit	Document discrepancies	Large or higher-risk trade transactions
Escrow / marketplace protection	Order or release-condition disputes	New supplier relationships
Card	Chargebacks and payment disputes	Smaller purchases and samples
B2B payment platform	Account, compliance or corridor-specific restrictions	Recurring cross-border trade

A letter of credit, for example, replaces a simple payment instruction with a document-based trade-finance process. That reduces some payment risks but creates another category of risk: documentary discrepancies.

The ICC Banking Commission has estimated that 65–80% of documents presented under documentary credits are refused on first presentation, although many discrepancies are subsequently resolved.

The lesson is not that one method is universally better.

It is that payment method should match the transaction risk.

For businesses making regular international trade payments, XTransfer takes a different approach from relying exclusively on correspondent-bank wires.

Instead of treating every payment as a traditional cross-border bank transfer, XTransfer combines:

• Local Accounts

• Global Accounts

• X2X transfers

• FX management

• Trade-focused compliance

• Global supplier payouts

XTransfer currently provides access to local clearing networks across around 60 countries and regions, and its global payment service supports payments to 200+ countries and regions.

The right XTransfer product depends on how your business moves money.

1. Local Accounts: Pay and Get Paid Through Local Payment Rails

For businesses trading in emerging markets, the biggest advantage of a local collection account is not simply faster settlement. It can allow local buyers to pay in their own currency when access to US dollars is limited or expensive.

In many emerging markets, importers may earn revenue and hold working capital in local currency but face limited access to USD liquidity. When a Chinese supplier asks to be paid in USD, the buyer may need to source dollars through a local bank, navigate foreign-exchange controls, or wait for USD availability before making the payment.

A local collection account can bridge that gap.

With XTransfer, eligible businesses can collect local-currency payments through supported domestic payment networks and then use those funds for cross-border supplier payments.

How it works

Local buyer → pays in local currency → XTransfer Local Account → FX conversion → Chinese supplier receives the required currency

This means an importer in an emerging market does not necessarily need to obtain USD from a local bank before paying a Chinese supplier.

Examples across emerging markets

Market	Why it matters
Brazil	Brazilian buyers can pay using BRL rather than sourcing USD for the payment
Mexico	Buyers can use local MXN liquidity instead of initiating a USD international wire
Colombia	Local-currency collection simplifies payment for domestic buyers
Argentina	Buyers can pay from local ARS liquidity
Peru	Local-currency payment supports buyers who primarily hold PEN
South Africa	Buyers can pay through a local ZAR payment method
Vietnam	Local-currency collection supports importers operating primarily in VND

XTransfer currently supports local payment across markets including Brazil, Mexico, Colombia, Argentina, Chile, Peru, South Africa, Vietnam, the UK, the US and others.

2. Global Accounts: One Account for Multi-Currency Trade

Local Accounts solve a specific market problem.

Global Accounts solve a multi-market treasury problem.

XTransfer's Global Business Account supports 20+ currencies and 200+ countries and regions, allowing businesses to receive and pay internationally through a single business account.

This can be useful when a business:

• Receives payments from multiple countries

• Pays suppliers in different currencies

• Holds multiple currency balances

• Needs centralized FX management

• Wants to reduce the number of separate banking relationships

• Manages international payables from one platform

The distinction is important:

Local Accounts connect your business to local payment rails. Global Accounts give you a broader multi-currency operating layer.

For businesses with several trade corridors, both can work together.

3. X2X: Near-Instant Transfers Between XTransfer Users

When both businesses use XTransfer, X2X provides another payment route, ensuring near-instant, 24/7 transfers between XTransfer accounts with zero transaction fees.

This is particularly relevant when:

• Buyer and supplier both use XTransfer

• Funds need to move outside traditional banking hours

• Both parties want a direct transfer within the same platform

• The payment does not need to travel through a traditional correspondent-bank chain

In simple terms:

Local Account → local payment network

Global Account → multi-market payment and collection

X2X → XTransfer-to-XTransfer transfer

XTransfer for Regular Supplier Payments

For businesses paying overseas suppliers repeatedly, the biggest benefit of a payment platform is not simply making one transfer.

It is creating a repeatable payment process.

A typical workflow can look like this:

Supplier invoice → beneficiary verification → payment approval → FX conversion → payment → reconciliation

XTransfer supports B2B payment workflows around these recurring activities, including global payouts and local-currency payment capabilities. Its public product information also highlights 24/7 FX management, local currency accounts and global supplier payouts.

That can be especially relevant for businesses managing:

• Multiple suppliers

• Multiple currencies

• Recurring purchase orders

• Cross-border marketplaces

• China sourcing

• International wholesale

• Import and export payments

Before clicking Send, check these seven items:

Beneficiary

☐ Legal name matches the supplier's records

Account

☐ Account number / IBAN is correct

Bank

☐ SWIFT/BIC and bank country are correct

Currency

☐ Payment currency matches the supplier's instructions

Amount

☐ Amount and fees are understood

Purpose

☐ Payment purpose and required supporting documents are ready

Verification

☐ Any recent change in bank details has been independently verified

These seven checks can prevent many avoidable payment exceptions before they happen.

Why was my international payment returned?

Common reasons include incorrect account details, a closed or blocked account, beneficiary information that does not match, missing payment data, insufficient funds or regulatory restrictions. Ask your bank for the return reason code rather than relying on a generic “payment failed” message.

What is the difference between a rejected and returned payment?

A reject means the payment instruction was not processed as intended. A return sends funds back after settlement. In ISO 20022, pacs.002 is used for payment status/reject information, while pacs.004 is the payment-return message.

What does AC01 mean?

AC01 generally means an incorrect account number. Check the beneficiary's account or IBAN before resending the payment.

What does AC04 mean?

AC04 generally means the beneficiary account is closed. Ask the supplier for an active account and independently verify the new details.

What should I do if my payment is returned?

First identify the return reason, then verify the beneficiary details, check the returned amount and correct the underlying issue. Do not resend the payment until you know why it was returned.

How long does an international payment return take?

It depends on the payment route and where the payment was stopped. Swift notes that payment investigations can take five to ten working days in some cases.

Can a local account prevent international payment returns?

A local account cannot guarantee that a payment will never fail. It can, however, reduce reliance on correspondent-bank routes where local payment infrastructure is available. XTransfer currently provides local payment capabilities across around 60 countries and regions.

What is the difference between an XTransfer Local Account and Global Account?

Local Accounts are designed around a specific local currency and payment network. Global Accounts provides multi-currency business-account functionality across 20+ currencies and 200+ countries and regions.

What is X2X?

X2X supports near-instant, 24/7 transfers between two XTransfer accounts with zero transaction fees.

Should I use a bank wire or a B2B payment platform?

It depends on the transaction. Bank wires may be appropriate for certain large or established transactions, while a B2B payment platform can be useful for recurring supplier payments, multi-currency operations and local payment corridors. Compare the total cost, settlement route, traceability, and supported currencies rather than looking only at the transfer fee.