Middle names and middle initials

This is the single most common form of name mismatch, and it is also the one people are least likely to suspect, because the name looks correct to them. The system is not reading your name the way you do. It is comparing strings, and a middle name is a string that is either present or absent.

Four variants cause almost all of these failures. Your document shows a full middle name and your profile has nothing. Your document shows a full middle name and your profile has only the initial. Your document shows only an initial and your profile has the full name spelled out. Or your middle name has been merged into the first name field, so the system reads a first name of "Maria Elena" against a document that says the first name is "Maria" and the middle name is "Elena".

Some verification systems normalise for this. Many do not. Documented examples exist of financial platforms rejecting an account link specifically because the middle name format on one side did not exactly match the other, and the error message in those cases usually says nothing about middle names at all. It simply says the names do not match.

The rule that works: reproduce the document exactly, field for field. If your passport prints a full middle name, type the full middle name. If it prints only an initial, type only the initial, with no full stop unless the document shows one. Do not add a middle name that the document omits, even if it is legally yours, and do not drop one the document includes.

If the platform gives you one name field rather than separate ones, enter the names in the order the document prints them, separated by single spaces, with no commas.

Maiden names, married names and legal name changes

A name change creates a period during which your documents disagree with each other, and verification systems have no sense of history. They compare what you typed against what the document says, right now.

The failure usually appears in one of two shapes. Either the account was opened under a former name and the document now shows the new one, or the account uses the new name while the document you are submitting was never updated. Both produce the same generic rejection.

Work out which document you are actually going to submit, then make the profile match that specific document. Do not try to satisfy both names at once by hyphenating or by putting the former name in a middle name field. That produces a third string that matches neither.

Where the platform has already verified you under the old name and you need the record changed, that is a different process from verification and it usually requires the change document itself: a marriage certificate, a deed poll, a court order, or an updated passport showing the new name. Most platforms have a documented route for this, and it goes through support rather than through the verification flow. Trying to force it through verification tends to burn attempts without moving anything.

One practical warning. Some identity checks compare your details against public records held by credit bureaus and similar databases rather than against your document alone. Those records lag. If you changed your name, moved address or changed your phone number recently, you can fail a check even though every document you hold is correct and consistent, simply because the reference data has not caught up. Documented error codes exist for exactly this situation, and the resolution is usually to confirm the details on screen and, if it still fails, to escalate to a human review rather than to keep retrying.

Accents, diacritics and characters the form will not take

If your name contains characters outside the basic Latin alphabet, you have a structural problem that is not your fault and that no amount of careful typing fully solves. Names like Muñoz, Fernández, Müller, Łukasz, Škoda or Åberg carry marks that many signup forms silently strip, refuse, or convert.

What tends to happen is that you type the name correctly with its accents, the form stores a stripped version, and the comparison then runs your stripped profile name against a document that prints the accented form. Sometimes it is the reverse: the reader extracts the accented characters correctly from the document and your profile holds the plain version you typed years ago.

There is a useful asymmetry to exploit here. Passports carry a machine readable zone, and that zone is restricted to a limited character set. It cannot represent diacritics. So the machine readable zone on a passport belonging to Muñoz will encode MUNOZ, while the printed field above shows Muñoz. Both are correct renderings of the same name, and a verification system reading the machine readable zone is comparing against the stripped form.

In practice that means if the form accepts accented characters, enter the name exactly as the printed field shows it. If the form strips them or refuses them, enter the plain form exactly as the machine readable zone renders it, which for most European diacritics means dropping the mark rather than expanding the letter. The important thing is to be consistent and to avoid inventing a third spelling.

Two specific traps worth naming. The German ß is expanded to SS in the machine readable zone, so Straßer becomes STRASSER, not STRASER. And the Nordic Ø and Æ expand rather than simplify, becoming OE and AE respectively. Guessing at these produces a mismatch that looks inexplicable.

Transliteration between different scripts

If your name is written natively in Arabic, Cyrillic, Chinese, Japanese, Korean, Greek, Hebrew, Thai, Hindi or any other non Latin script, your documents contain a Latin rendering that somebody chose. That choice is not unique, and different authorities make different choices for the same name.

The same Arabic name can appear as Mohammed, Muhammad, Mohamad, Mohamed or Muhammed. The same Cyrillic surname can appear as Ivanov or Ivanoff, Sergey or Sergei or Serhii. Chinese names vary by whether the romanisation follows Pinyin or Wade Giles, and by whether the family name is printed first or last.

The problem is that you may hold several documents that disagree. Your passport says one thing, your national identity card says another, your bank has a third version from ten years ago, and you habitually type a fourth because it is the spelling you prefer in English.

The resolution is to nominate one document as your reference, ideally your passport because its machine readable zone gives the verifier a second confirmation, and then make every profile match that document precisely. Not the version you like. Not the version your employer uses. The version printed on the document you are going to upload.

Name order deserves separate attention. Many East Asian documents print the family name first. Many Arabic names include a patronymic chain that a Western form has no field for. If the form asks for a first name and a last name and your document does not divide neatly into those two, use the fields the way the document's machine readable zone divides them, because that division is what the system will read.

Bank name mismatches are a different problem

There is an important distinction between a platform saying your document does not match your profile, and a platform saying your bank account name does not match your verified identity. People search for both using almost identical words, but the fixes are not the same.

The second case appears when you link an external bank account, add a withdrawal method, or connect an account through an instant verification service. The system compares the account holder name at your bank against the name it has verified for you. Documented error codes exist for precisely this, including cases where linking fails because the name at the external institution does not match the name on the receiving account.

This one cannot be fixed by editing your platform profile, because the mismatch is at the bank. Common causes are a joint account where only one holder is named in the system, a business account being linked to a personal identity, an account still held in a former name, or a bank that stores your name in an abbreviated form.

The fix runs through the bank. Ask your branch what exact name string they hold for the account, in writing if possible, then make the platform profile match it, or ask the bank to update their record. Banks generally have a formal name amendment process requiring identity documents, and it is worth doing properly because a mismatched payout name will keep failing every time you try to withdraw.

When the name is right and it still fails

A category of name rejections has nothing to do with spelling. Your name is entered perfectly, it matches your document character for character, and you are still refused. In that case the comparison that failed was probably not against your document at all.

Regulated platforms screen every applicant against sanctions lists, politically exposed persons databases and adverse media records. Those checks match on names, and names are not unique. If your name resembles an entry on one of those lists, the screen can flag you even though you are an entirely different person. This is called a false positive, and it is common enough to have its own handling procedures inside compliance teams.

You can usually recognise it by the timing. Document and photo failures come back within seconds, because they are automated image checks. A screening match tends to arrive after your documents were accepted, sometimes hours or days later, and often as a request for more information rather than a flat refusal.

Retaking your photograph will do nothing here, and neither will editing your profile. We have written this up separately, because the resolution is completely different: see sanctions and PEP false matches.

A checklist that catches almost all of them

Work through this before spending another attempt. Open your profile settings and your document side by side and compare, character by character, out loud if it helps.

1. Does the first name field contain exactly what the document prints as the given name, and nothing more?
2. Is the middle name present or absent in the profile in exactly the way the document has it, full name for full name, initial for initial?
3. Is the surname complete, including any prefix such as van, de, al or bin, spelled and spaced the way the document shows?
4. Are accented characters either both present or both absent on the two sides, with no third variant?
5. If your name transliterates from another script, does the profile match the document you are actually uploading rather than a different document?
6. Is the date of birth in the format the form expects, and does it match the document rather than being off by the day and month being swapped?
7. Is the document currently valid, with more than three months before expiry?
8. If this is a bank link rather than an identity check, does the name held by the bank match too?

If all eight are true and it still fails, you are most likely looking at a screening match or a public records lag rather than a spelling problem, and the right next step is to ask for human review rather than to submit again.