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.


When a crypto exchange deposit name does not match the bank account, the transfer can be delayed or returned: the sender name in the payment record differs from the verified name on the exchange account. Stop sending repeat transfers. First identify the actual sender, payment rail, account type, and name shown by each institution; then give each side the same traceable transfer facts.
Key Takeaways
- Do not send another payment until the exchange explains whether the first transfer is pending, rejected, or being returned.
- Compare the legal account-holder name, not a nickname, card label, email address, or bank-app display name.
- Treat joint, business, trust, payment-processor, and third-party accounts as separate cases.
- Preserve the bank statement, transfer reference, sender account details, exchange instructions, amount, time, currency, and case numbers.
- Contact your bank and the exchange through independently opened official channels; never pay an “unlock” fee.
The online security guide explains how to protect the email and authentication channels you will use during support.
Bank funding creates a record of the originating account holder. Exchanges use that record with their verified customer profile to reduce mistaken credits, third-party funding, fraud, and compliance risk. Coinbase and Kraken both publish rules requiring the bank-account name to match the exchange account name.[1][2] The precise comparison, accepted account types, and return process remain platform-specific.
This is a fiat-funding problem. If cryptocurrency already has blockchain confirmations but the exchange balance is missing, use the confirmed crypto deposit checklist. If the entire account is restricted, use the exchange account freeze guide.
| What you find | What it may mean | Safe next action |
|---|---|---|
| Minor spelling, spacing, or order difference | Formatting or transliteration mismatch | Ask which exact profile field must be corrected |
| Previous name versus current legal name | Bank and exchange records are out of sync | Use the formal name-update route; keep supporting records private |
| Joint account | Only one holder is visible in the payment message | Ask whether joint accounts are accepted and which holder must match |
| Company, trust, or organization account | Account type differs from a personal exchange profile | Do not represent it as personal funding; confirm eligibility |
| Payment processor or fintech intermediary | The processor may appear as sender | Ask whether that rail is supported before retrying |
| Family member, employer, customer, or friend sent it | Third-party funding | Do not invent ownership; request return or the platform's documented remedy |
Record the transfer once. Save the amount and currency, initiation and settlement times with timezone, bank reference, beneficiary details used, sender account's masked number, transfer rail, and the status shown by the exchange. Download the statement or payment confirmation from the bank itself. Keep the exchange's original deposit instructions, including any unique reference or memo.
Do not edit screenshots, combine two transfers into one story, or omit a rejected attempt. Support needs a clean timeline. Redact unrelated transactions, full account numbers, identity numbers, and balances before sharing any image. Keep an unredacted copy offline for your own records if a bank formally requires it.
Open the bank account profile and determine who legally owns the sending account. The name printed on a debit card may differ from the account title. A mobile-wallet label may identify the app rather than the underlying sender. A business account can display an employee's login while the legal owner is the company.
Write down the exact bank account title and the exact verified name displayed by the exchange. Compare punctuation, name order, middle names, transliteration, accents, maiden or former names, and business suffixes. Do not change either profile casually just to force a match. A legal-name correction should follow the institution's documented process.
Confirm whether the source is personal, joint, business, trust, brokerage cash, fintech, or a third-party payment service. Then identify whether the transfer was domestic wire, international wire, ACH-like bank transfer, instant bank payment, or another local rail. Deposit instructions for one rail may not work for another.
A joint account is not automatically accepted. One platform may accept it when the exchange customer is a named holder; another may require additional proof or reject it. A processor can also replace your name with its own settlement name. Do not assume that a payment “from your app” is technically sent from an account in your name.
Look for pending review, action required, rejected, canceled, credited, or returned. A missing balance alone does not show where the funds are. Check whether the amount was deducted, merely authorized, settled, or already returned by the bank.
If the exchange asks for information, verify that the request also appears inside the authenticated account. Upload only the minimum required evidence through that official route. Do not send a full bank history, password, MFA code, seed phrase, private key, or remote-access session.
Tell the bank that the recipient reports a sender-name mismatch. Ask for the transfer's official trace or reference, the sender name actually transmitted, the payment rail, settlement status, return status, and whether an intermediary rewrote the remitter field. The bank should not need your exchange password or wallet secrets.
If the bank confirms a return, ask for the return date and reference rather than sending again immediately. Returned funds can take a different route from the original payment, and another transfer can create duplicate cases.
Use the case form inside the official site or app. Include your case number, masked bank account, legal sender name, account type, rail, amount, currency, timestamps, bank trace, exchange reference, and a redacted proof of transfer. State any spelling or former-name difference plainly.
Do not claim that a third party is you. If someone else sent the money, say so and ask whether the only supported outcome is a return. If the funding came from a business or joint account, name that account type and identify your legitimate relationship without exposing other holders' unnecessary personal data.
If your legal name changed, ask both institutions which record should be updated and what evidence is necessary. Complete one documented change at a time and preserve confirmation. Do not repeatedly rename profiles while a transfer is under review.
If the mismatch is only formatting, ask the exchange to confirm whether it can reconcile the payment or whether the bank must amend or recall it. Never fabricate a statement or alter the sender line. That can turn a routine reconciliation problem into a serious account review.
Do not send a second “test” payment, split the amount, route money through a friend, or use a different bank account to bypass the review. Do not open a duplicate exchange account. Do not ask the bank to disguise the sender name. Avoid public posts containing references, balances, legal names, or screenshots of deposit instructions.
Be skeptical of direct messages from supposed recovery agents. Neither institution should require cryptocurrency, gift cards, screen sharing, or an advance fee to release a bank transfer.
No. Matching rules differ, and some systems normalize spacing or name order. Ask the exchange how it classified the transfer before changing records or paying again.
Only if the platform explicitly supports that arrangement and your account is configured correctly. Do not describe a company account as a personal account.
Policies vary. Confirm that the platform accepts joint accounts and that your verified name is transmitted as an account holder.
Use each institution's formal profile-update process and provide only the requested evidence. Keep confirmation of the change and avoid repeated edits during review.
Yes. A payment processor or fintech may appear as the remitter. Ask the provider which sender field was transmitted and whether the exchange supports that rail.
No. First determine whether the original transfer is pending, rejected, or returning. A repeat can create duplicate funding and support cases.
Disclose that it is third-party funding. Ask for the documented return or remediation path; do not pretend the bank account belongs to you.
No. A VPN cannot change bank ownership records, exchange identity records, payment messages, or compliance decisions.
Disclaimer: This article is for general informational purposes and is not legal, financial, investment, banking, tax, or platform-specific advice. Rules, evidence requirements, timelines, and outcomes vary by provider and jurisdiction.
Sources checked 9 September 2026.
Related articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.





