A beneficiary name mismatch means the recipient name entered for a transfer does not appear to match the name associated with the destination account or payout record. It is a warning or discrepancy, not a transfer code. If you see one while sending money internationally, pause and confirm the recipient’s details before you authorise the payment.
What does “beneficiary name mismatch” mean?
The beneficiary, also called the payee, is the person or business intended to receive the money. For a bank transfer, the sender may be asked for the beneficiary’s name and account number or IBAN, plus details such as an address, country and bank identifier. A name mismatch arises when a check cannot reconcile the name supplied by the sender with the name held for the destination details.
It is not the same as an invalid account number. An IBAN identifies an account using a country code, check digits and country-specific account information; it does not identify the account holder by name. Likewise, an account-number check does not necessarily verify who owns that account. Name-check availability and results depend on the payment route, participating providers and local rules.
What might a mismatch look like?
A payment screen might display close match, no match or wording such as could not confirm the recipient. These are examples of possible results, not universal error messages. A close match may point to a spelling difference; an unavailable result does not establish that the name is wrong.
Fictional example: A sender enters “Mira Exempl” as the beneficiary, while the recipient says her account is registered as “Mira Example.” The account field in the example reads “FICTIONAL-ACCOUNT-123”; it is a placeholder, not a usable bank identifier. A name check might flag the one-letter difference. The sender should ask Mira to confirm the exact name held by her bank and recheck the account details before proceeding.
Other differences can be less obvious: a shortened given name instead of a formal one, omitted parts of a registered business name, diacritics, or a different transliteration. Do not assume a familiar name, invoice heading or contact-list label is the name registered to the receiving account.
Where can you find the name and the check result?
- Before sending: Ask the recipient for their full registered account-holder name and the required payout details. A business recipient can confirm the legal or registered trading name associated with its account.
- During checkout: If the sending service offers a name check, review any match result or warning beside the recipient details before authorising. The wording and whether a check is offered vary by route.
- After sending: Review the recipient information and transfer status in your sending service. If something looks wrong, contact that service promptly and give it the transfer reference shown in your records.
For a bank deposit, the recipient can ask their bank which name is associated with the account. For a mobile-wallet or cash-pickup payout, confirm the recipient identity and payout details required for that method rather than trying to make a bank-account name check fit a different type of payment.
When is a beneficiary-name check needed—and when is it not?
A correct beneficiary name is important whenever the transfer asks for one. A formal, before-you-send name check, however, is not a feature of every international payment. In the EU, Verification of Payee (VoP) applies to covered euro credit transfers, including standard and instant transfers. It provides a comparison of the payee’s name and account identifier before the payer authorises the transfer. Possible results include match, close match, no match and other. A warning does not, by itself, prevent authorisation.
VoP should not be mistaken for a rule covering every international currency or every destination outside the EU. The compliance date for relevant providers in euro-area EU member states was October 9, 2025; for relevant providers in non-euro-area EU member states it is July 9, 2027, with distinct later deadlines for certain institutions. Whether a particular provider must offer it depends on the applicable rules.
In the UK, Confirmation of Payee (CoP) compares a name with UK sort-code and account-number details for domestic payments, including routes such as Faster Payments, CHAPS and Bacs where offered. It is not, by itself, a check on an overseas beneficiary account. If no name-check result appears for your international transfer, that does not mean the recipient details have been verified. Confirm them directly with the recipient.
How is this different from the codes on a transfer?
| Term | What it tells you | Does it confirm the recipient’s name? |
|---|---|---|
| Beneficiary name mismatch | A possible discrepancy between the entered name and the name associated with the payout details | It signals a concern; investigate before sending |
| IBAN | Identifies an account in countries that use IBANs | No, an IBAN is not the holder’s name |
| SWIFT/BIC | Identifies a financial institution for relevant bank-transfer instructions | No |
| EU Verification of Payee | A name/account-identifier check for covered euro credit transfers | It reports a match outcome within its scope |
| UK Confirmation of Payee | A name check for eligible domestic UK account details | It reports a match outcome for that domestic check, not an overseas account |
Common mistakes and what can happen if the name is wrong
Common mistakes include copying a nickname from a phone contact, using an invoice’s brand name instead of the account’s registered name, reversing name fields, or overlooking a change in the recipient’s legal name. For business payments, check the supplier’s beneficiary instructions against the account holder named on its payment documents. Independently confirm any unexpected change of account details with a trusted contact.
There is no single outcome for a mismatched name. A check may show a close match or no match; another route may have no name check at all. Depending on the provider and payout method, the recipient may be unable to collect the money, or a bank may process a payment using the account number despite an inconsistent name. A could not confirm result can also mean a check was unavailable, rather than proving the name is incorrect.
A wrong account number or bank identifier is a separate and potentially more serious problem: the money may be directed to the wrong account. Do not treat a correctly formatted IBAN or a matching bank identifier as proof that all recipient details are safe to use.
If you notice an error before authorising, stop and ask the recipient to confirm the details through a trusted channel. If you have already sent the transfer, contact the sending provider immediately to ask whether the instruction can be corrected or cancelled. Changes may not be possible after payout; the recipient may need to ask their bank or payout provider whether it can credit or return the payment. Do not send a second transfer until you understand what happened to the first.
How to check recipient details when sending with Coinepay
- Register with your real identity and complete any required verification. Open Coinepay Global Remittance in the self-service dashboard or the Coinepay app for iOS or Android.
- Choose the destination and available payout method. Coinepay supports bank account deposit, mobile wallets—including methods such as UPI, GCash, Maya and M-Pesa—and cash pickup. Enter the recipient’s real name and the details requested for that payout method.
- Compare the entered name with the recipient’s bank or payout records. For a bank deposit, also check the account identifier and any requested bank details. If a screen shows a mismatch or cannot confirm the name, pause; do not assume Coinepay has verified the account holder merely because an account identifier was accepted.
- Review the recipient details, the exchange rate and any fees shown before confirming. Once submitted, use the transfer’s status tracking to follow its progress.
If you spot a discrepancy after confirmation, contact Coinepay support promptly with the transfer reference and the details that need checking. Coinepay can explain the options available for that transfer; a correction, cancellation or return cannot be assumed.
Coinepay transfers are subject to identity verification, sanctions screening and local regulations. Coinepay may request documents concerning the purpose or source of funds. It does not serve sanctioned persons or residents of jurisdictions under comprehensive sanctions, and transfers cannot be sent to those jurisdictions. Name checks help identify possible mistakes, but they do not replace these requirements or the sender’s responsibility to verify the intended recipient.
Get your Coinepay virtual card: Sign up · App Store · Google Play · Customer support
FAQ
Is a beneficiary name mismatch a bank code I need to enter?
No. It describes a difference between the name entered for a recipient and the name associated with the payout details. Check the recipient’s registered name before sending.
Does a valid IBAN mean the beneficiary name is correct?
No. An IBAN identifies an account, not its holder. Confirm both the account details and the recipient’s registered name.
Will an international transfer always be rejected if the name does not match?
No universal outcome applies. A mismatch may trigger a warning or collection problem, while some payments may be processed using the account number. Pause and verify the details.
What should I do if I entered the wrong recipient name in Coinepay?
Before confirmation, correct it using details verified with the recipient. After confirmation, contact Coinepay support promptly with your transfer reference to ask what options remain.
Related guides
- Bank Account Number Formats by Country: What They Are and How to Use Them
- OUR, SHA and BEN charge options: What They Mean for Transfers
- MT103 Payment Confirmation: What It Is and How to Use It
- Purpose of Remittance Codes in India: What They Are and How to Use Them
- SEPA Transfers: What It Is and How to Use It for Transfers
- Intermediary and Correspondent Banks: A Transfer Guide
