Information checked October 21, 2026
A payment screen says the recipient’s name does not match. The booking deadline is close, and the person asking for the money says to ignore it. What should you check before sending?
Start by separating three questions: Are the account details correct? Does the name belong to that account? And is this payment request genuine? A name-check result helps with part of that decision. It does not answer everything.
Our practical rule is simple: pause an unexplained mismatch rather than treating the warning as a minor spelling problem. The checklist below is editorial guidance, not a promise that every bank uses the same checks or can recover an incorrect payment.
1. Ask for the account name, not just the familiar name
The name on an invoice, the name a friend uses, and the account name can differ. Ask the intended recipient for the name held on the receiving account and the payment details required for this particular route. Do not invent a shorter spelling to make a warning disappear.
For UK Confirmation of Payee, Pay.UK says personal payments use the exact registered account name. Business payments use the registered business name or a trading name registered to that account. This is not a rule that any brand name printed on an invoice will work. [1]
For a Wise EUR receiving account, Wise tells recipients to share the account name and IBAN as displayed, including spelling and middle names. Apply that instruction to that product rather than assuming all providers have identical naming rules. [2]
2. Establish which check you are seeing
Pay.UK describes Confirmation of Payee as a UK domestic account-name checking service. It can include whether the account is personal or business. [3] Wise describes Verification of Payee for relevant EUR IBAN recipients in the SEPA zone. [2]
Those are specific systems and scopes, not proof that every international transfer receives the same protection. Read the result your own provider displays. If the app cannot accommodate the recipient’s name, ask the provider how to enter it for that currency and destination. Do not guess how punctuation, accents or transliteration will be handled.
3. Treat the result as information, not permission to stop checking
Match: useful confirmation of account-name alignment, not a warranty that the underlying booking or seller is genuine.
Close match: compare the suggested name with independently confirmed details before changing the entry.
No match: stop and resolve the discrepancy with the intended recipient and, where needed, the provider.
Unavailable or unable to check: no successful name confirmation. It is not the same thing as a match, and it is not proof of fraud either.
Pay.UK lists match, close match, wrong name and unavailable outcomes. It explicitly says its service does not guarantee fraud detection or reimbursement. [1] Wise also distinguishes a failed check from a match and warns that money sent to the wrong account may not be recoverable. [2]
4. Reconfirm the payment request separately
If someone unexpectedly replaces the bank details for a hotel, tour or other travel service, use a contact route you already trust. Our recommendation is to confirm both the change and the reason for the new account before proceeding. HSBC similarly recommends confirming changed details with the company on a number known to be genuine. [5] Do not rely only on a phone number or link supplied in the same unexpected message.
A mismatch deserves investigation, not an accusation. There may be a naming explanation, but urgency is not evidence that an account is correct. Keep the payment request, the details you verified, and the provider’s response together. Do not post account numbers or screenshots containing personal details publicly.
5. If the transfer has already been sent, change the question
Do not assume that editing a saved recipient fixes a payment already in progress. Check the actual transfer status and contact the provider through its official support route.
Wise’s published guidance says correction options depend on the transfer’s progress: cancellation may still be available while pending, but Wise cannot change a completed transfer after it has entered the banking system. If cancellation is unavailable, its guidance directs the sender to ask the recipient to check with their bank about delivery or return. That is Wise-specific, not a universal cancellation right or refund deadline. [4]
Before sending again, establish what happened to the first payment. Our recommendation is to avoid creating a second unresolved payment just to meet a deadline.
The final pre-send check
Confirm the account name, account identifiers, account type where requested, currency, amount, required reference and final provider quote. A name match does not establish the cost of sending. Keep transaction principal, meaning the amount being transferred, separate from the total budget that must also cover applicable fees. This article uses no live rates, price quotes or illustrative monetary amounts.
Before you spend. Before you send. Check the details, not just the name.
Reporting note: This is an original editorial synthesis of official published guidance. It includes no interviews, test transfers or independent measurement of provider performance. Numbered references map to the source log. Educational information, not personalized financial advice. Recheck the provider’s current process before a transaction.
Related guides: transfer says complete but has not arrived; check what the recipient will receive; rate-lock deadlines.
Sources
[1] Pay.UK Confirmation of Payee FAQs. Reviewed October 21, 2026. No publication/update or separate effective date displayed.
[2] Wise: What is Verification of Payee?. Reviewed October 21, 2026. No publication/update or separate effective date displayed.
[3] Pay.UK Confirmation of Payee. Reviewed October 21, 2026. No publication/update or separate effective date displayed.
[4] Wise: I spelt my recipient’s name wrong. Reviewed October 21, 2026. No publication/update or separate effective date displayed.
[5] HSBC UK: Common scams. Reviewed October 21, 2026. No publication/update or separate effective date displayed.
Leave a Reply