Anyway, every time this happens, I just enter "Santa Claus", because the name isn't actually sent over the card network for your bank to validate in the first place.

(This is because comparing people's names is extremely difficult, as seen with Confirmation of Payee in the UK.)
(* Unless it's Amex, which does use some sort of fuzzy matching for fraud scoring. It doesn't straight up decline, but it's more likely to challenge mismatches.

** Also it's sent to your bank with 3DSv2 challenges, where I imagine somebody might do something similar.)
Systems that have Opinions on names make me angry, because I can probably name somebody who breaks every single assumption you're making

My birth name had two first names, the 2nd of which was my name of address; this is common where I was born, UK/US assumes it's always the 1st
A "middle name" in SE/FI/DK/NO is a family name, not a given name; if you change your last name by marriage, you can keep your original one as a middle name.

But the distinction isn't normally made, and for all intents and purposes, somebody like my mum just has two last names.
Before I continue, let me just drop the obligatory link to "falsehoods programmers believe about names": https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/
My proper name is "embr", a mononym.

You don't even need to leave Europe to find these; Icelandic names are mononyms, with patro/matronym (parent's name + son/dottir) to work around last name fields

Which also throws out the assumption that last names are shared within a family
Even cultures that have family names don't necessarily put them last.China and Japan are the best known ones here, but you don't need to leave Europe for this one either; look at Romania

The amount of stuff that ask for "first/last" and trip on honest answers from JP/CN/RO users
Why are you limiting your name field to ASCII?

Not only does Hébert -> Hebert completely change the pronounciation, "Jönsson" and "Jonsson" are patronyms for "son of Jöns" and "son of Jon" respectively, you've given both father and son completely different names!
Every time you put a minimum length on a name field, you're likely excluding one of the world's most common surnames - 李, or if you're also forcing ASCII, Li/Lee/Lei/Lie depending on dialect.

Funfact: Name romanisation is lossy. "Li" commonly means 李/黎/栗/戩 or rarely 理/莉.
(I should mention that neither of these last two are exclusively western problems; I've had my legal name rejected from Japanese forms for being >4 characters, or using latin ones.

I have a transport card here somewhere, issued to a lossy Romaji transliteration of it.)
Everyone knows the name of Leonardo da Vinci, but could he sign up for your website? What about with his full name: Leonardo di ser Piero da Vinci?

A startling number of systems would reject this, turn "da" into a middle name, and/or try to "fix" the capitalisation: "Da".
You can follow @_liclac.
Tip: mention @twtextapp on a Twitter thread with the keyword “unroll” to get a link to it.

Latest Threads Unrolled:

By continuing to use the site, you are consenting to the use of cookies as explained in our Cookie Policy to improve your experience.