On June 17, 2019 (PT), Mastercard announced a commitment to introduce “True Name” so “true names, not deadnames, [appear] on cards without the requirement of a legal name change” (Mastercard newsroom). The post cites a concrete harm signal: “nearly one-third (32%)” of people whose IDs did not match their presentation reported negative experiences like harassment or denial of services (same source). Lesson: inclusion can be implemented as a privacy-respecting operational process, not just a UI change.
When a card name exposes a “deadname,” routine transactions can become humiliating or unsafe. Identity mismatch also forces repeated disclosure and “explaining yourself” in public, which is avoidable harm in a basic service flow (Mastercard). The benefit of fixing it is measurable: fewer negative encounters, higher trust in payments, and less friction for people who cannot or do not want to complete legal name changes. If you build identity systems, design for chosen names, minimal disclosure, and flexible formats end-to-end.
Join "Resonate", my weekly series that puts the best examples, tips, and insights for designing products that resonate with everyone, everywhere.
Join The Newsletter