Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


If recipient details don’t match on an international transfer, pause before authorizing it. Compare the recipient's legal or account name, account type, account number or IBAN, local routing fields, BIC or SWIFT code, and any intermediary instructions separately, then obtain the details again through a trusted channel. An account type mismatch, such as personal versus business or checking versus savings, is a field to reconfirm with the recipient, not to guess. If the payment has already been sent, contact the sending provider immediately instead of sending a duplicate.
Key Takeaways:
- A name warning is different from an invalid account, routing, BIC, or intermediary-bank error.
- Never “correct” unfamiliar bank details by guessing from a country format or an old payment.
- Reconfirm changed instructions through a phone number, portal, or contact already known to be genuine.
- Match, close match, no match, and check unavailable are examples from particular services, not universal bank outcomes.
- If the transfer was sent, preserve the receipt and ask the sending provider about correction, trace, recall, or return.
- An ignored warning can increase risk, but a match result is not proof that a payment is safe or recoverable.
The international travel planning guide covers broader account preparation. This checklist deals only with verifying one recipient and deciding what to do before or after payment.
Do not treat “recipient details” as one field. Open the provider's warning and record exactly what it checked and what it could not check. A name-comparison result may say nothing about a BIC, while an IBAN format check may say nothing about who controls the account.
Separate the details into these groups:
| Field group | Examples | What to verify |
|---|---|---|
| Recipient identity | Personal or company name, middle name, suffix, legal form | Name expected on the receiving account and permitted transliteration |
| Account identifier | Account number, IBAN, card or wallet identifier where supported | Exact characters, country prefix, length, and destination account |
| Account type | Personal or business, checking or savings, currency account | Type the receiving bank holds, where the provider asks for it |
| Local routing | Routing, sort, branch, institution, transit, clearing, or bank code | Field required for that country and payment route |
| Institution identity | BIC or SWIFT code, bank name and country | Receiving institution and branch or routing role |
| Intermediary instructions | Correspondent bank, beneficiary-to-bank reference, further-credit details | Whether the sending provider actually requires them |
Copy the field from the warning rather than relying on memory. Check for transposed digits, missing leading zeroes, letter-versus-number confusion, obsolete branch details, or information pasted into the wrong box. Do not add spaces or remove characters unless the provider's official format guidance permits it.
If the interface only says “details do not match,” ask support which comparison produced the warning and whether the check was completed, unavailable, or inconclusive.
Names can differ because of accents, punctuation, middle names, married names, company suffixes, scripts, or transliteration. A minor visual difference is not permission to ignore a warning. Ask the recipient for the account-holder name exactly as their bank expects it for incoming payments.
For a person, compare the bank-record name with the recipient's explanation, not only with a passport or email signature. A bank may store a shortened, local-script, or transliterated version. For a business, distinguish the registered legal entity from a trading name, brand, employee, landlord, or payment processor.
Do not decide that the account number “matters more” everywhere. Some payment systems route primarily by an account identifier while a separate name-checking service supplies a warning; others have different correction or rejection rules. The sending provider must explain which fields control the payment and what the warning means for that route.
If the recipient says the mismatch is harmless, ask for confirmation through the trusted channel and retain it. Then follow the provider's documented process. A screenshot of a banking app can be altered and may expose unrelated data; prefer bank-issued account details, a secure portal, or a verified conversation where appropriate.
For euro credit transfers within the Single Euro Payments Area (SEPA), payment providers now run Verification of Payee to compare the account name with the IBAN before you authorize the payment. The European Payments Council scheme rulebook, in force since October 2025, defines responses such as match, close match, no match, or verification check not possible.[1] This is a specific European payment framework, not a description of every international bank or transfer service.
Use a result as a decision signal:
A positive result is not fraud insurance. A criminal may control an account under a matching name, and a genuine recipient may have a legitimate variation. The result also does not decide liability, recovery, or whether another bank will accept the payment.
If your provider does not offer name checking, use the same independent verification discipline. Confirm the complete payment instruction and recipient authority rather than trying to reproduce another region's service yourself.
Use contact information obtained before the change: a saved phone number, official customer portal, signed contract, known company directory, or in-person contact. Do not verify changed bank details by replying to the same unexpected email or message that introduced them.
Ask the recipient to confirm:
Read back selected characters or use a two-person review for a high-consequence business payment. Avoid sending the full account details through several insecure channels. The aim is independent confirmation, not wider exposure.
Treat last-minute changes, secrecy, urgency, altered invoice domains, requests to split the amount, and instructions to bypass a warning as fraud indicators. Pause the business process and escalate internally or to the genuine recipient. Keep identity verification separate from confirming where the payment will go.
If the transfer has not been authorized, cancel the draft or edit it only through the provider's supported flow. Some providers cache beneficiary details, so compare every field again after saving. Do not assume changing the displayed name changes the underlying account identifier.
When several fields are wrong, creating a fresh beneficiary from newly verified information can be clearer than repairing an old record. Keep the old instruction and change request as evidence, but do not leave an ambiguous duplicate beneficiary active if your provider offers a safe way to archive it.
Check the amount, currency, fee payer, purpose code, payment reference, and recipient notification after correcting the bank fields. A correct beneficiary can still receive the wrong currency, amount, or reference.
If the provider continues to warn after the recipient reconfirms the details, ask the provider what evidence it accepts and whether the route supports that recipient. Do not work around the warning with another product or smaller “test” payment unless the genuine provider and recipient have agreed on a safe, documented approach.
Contact the sending bank or transfer provider using the details on the genuine receipt or official app. Provide the transaction reference, date, amount, currency, recipient fields used, exact error discovered, and how you verified the corrected information. Ask whether the payment is pending, released, rejected, credited, or returning.
Request the process that fits the stage: correction before release, trace, recall request, recipient-bank contact, error notice, or formal complaint. None guarantees recovery. Do not send a replacement until the first payment is accounted for or the provider gives clear written instructions.
The US Consumer Financial Protection Bureau explains how a consumer can notify a remittance-transfer provider about an error and what transfer information to provide.[2] Its timing and remedy rules apply in their stated US context. Elsewhere, follow the contract, regulator, complaint body, and deadlines that govern your provider.
If the mismatch followed a suspicious email or account takeover, protect the sender's account and email, preserve message headers and documents, and report the fraud through relevant channels. Tell the genuine recipient without using the compromised conversation. A bank's attempt to recall the transfer should run alongside, not replace, the security response.
When recipient details don't match on an international transfer, identify the precise field, stop the payment, and obtain the complete instructions again through a trusted channel. Treat regional name-check results as limited signals, not global rules. If funds were sent, preserve evidence and ask the sending provider for the stage-appropriate correction, trace, recall, or complaint process without making a duplicate payment.
It depends on the payment route, provider, and receiving institution. Do not assume it will pass or fail. Ask which field was checked and confirm the account-holder name exactly as expected.
Obtain the bank-record form of the name from the recipient through a trusted channel. A legitimate variation can exist, but only the relevant provider can explain how its comparison and payment route handle it.
There is no safe global answer. Routing and name-verification rules differ. Verify both, and ask the provider which fields control the particular payment rather than overriding one based on an assumption.
Do not ignore it. Pause, independently reconfirm the details, understand what was checked, and follow the provider's documented process. A close match is not the same as a confirmed safe recipient.
Contact the sending provider immediately with the receipt, error, and corrected details. Ask about the current stage and available trace, correction, recall, return, or complaint process. Do not duplicate the payment.
Treat it as unverified until confirmed through a previously trusted channel. Do not reply to the same email to validate it, and do not use new phone numbers or links contained only in that message.
Prepare the transaction reference, date, amount, currency, entered recipient details, exact mismatch, corrected details, evidence of independent verification, and a chronology of communications.
Pause the payment, reconfirm details through a trusted channel, and contact the bank immediately if funds have left.
Sources checked 4 October 2026.
This article provides general payment and fraud-prevention information, not financial, legal, compliance, or recovery advice. Matching services, payment routing, correction, recall, liability, and complaint rights vary by provider, network, contract, and jurisdiction.
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.





