# The Slash That Broke Delaware
Before Stripe processed $1.4 trillion in annual payment volume, before the $91.5 billion valuation, before it became the financial infrastructure behind Amazon, Google, and Shopify, the company had a different name. Patrick and John Collison called it /dev/payments. The slash was intentional. The reference was clever. It was a Unix file path — the kind of thing that would make a developer smile and a lawyer's eye twitch.
The problem arrived when the Collisons tried to incorporate in Delaware. Forward slashes are not permitted in corporate entity names under Delaware General Corporation Law. The name that was designed to signal developer credibility couldn't legally exist as a company. It couldn't be a clean URL. It couldn't be dictated over a phone call without someone asking, "Wait, is that a backslash or a forward slash?" And it couldn't be mentioned in conversation without the speaker pausing to wonder whether they needed to say "slash dev slash payments" or just "dev payments."
/dev/payments was erased from oral history before it ever entered it.
## The Linguistics of Unspeakability
Rory Sutherland has a phrase for this: "the phone test." If you can't say your company name to someone over the phone and have them type it correctly on the first try, you've built friction into every conversation about your product. That friction compounds. Every investor pitch that starts with a spelling clarification. Every podcast mention that gets transcribed incorrectly. Every word-of-mouth referral that dies in transit because the listener couldn't reconstruct the name from what they heard.
/dev/payments fails the phone test catastrophically. It contains two special characters, a three-letter directory name borrowed from Unix conventions, and a plural noun. It's a name built for people who already know what it means — which, in a world where the goal is to process payments for every business on the internet, is a fatally small audience.
David Placek's processing fluency research, supported by peer-reviewed studies in the Journal of Consumer Research, shows that names requiring effortful processing — names that demand the listener parse special characters, decode references, or disambiguate spellings — are recalled less accurately and evaluated less positively than names with high processing fluency. The cognitive load isn't just an inconvenience. It's a measurable drag on brand formation.
## What Stripe Gets Right
The Collisons chose Stripe sometime in 2011. The name is a single English word, one syllable, six letters. It begins with an ST- consonant cluster — a voiceless fricative followed by a voiceless plosive — that creates what phoneticians call a "clean attack." The sound is crisp, immediate, and forward-moving. It doesn't linger. It doesn't need explanation. It arrives and it's done.
The short I vowel in the middle is what sound symbolism research classifies as a front vowel — perceived across languages as smaller, faster, and sharper. For a payments company, that perceptual fingerprint is ideal. You don't want your payments infrastructure to feel large and slow. You want it to feel precise and quick. The name's sound does this work before the conscious brain has finished processing the word.
The -ipe ending is unusual in English. It doesn't rhyme with common words or slot into familiar phonetic patterns. That novelty creates distinctiveness — the quality Placek identifies as the most reliable predictor of long-term brand recall. Stripe doesn't sound like any other company. It doesn't sound like a payments company. It sounds like itself, which is exactly the point.
Semantically, "stripe" carries useful associations without being descriptive. A stripe on a credit card. A racing stripe suggesting speed. The stripe of a tiger suggesting precision. None of these meanings are the meaning — the word creates an associative field rather than a definition. This is the compound multiplier that Placek describes in his work on naming architecture, applied to a single word: multiple meaning pathways converge to create a richer impression than any one definition could achieve.
## The Naming Paradox of Developer Tools
The Stripe story reveals a specific paradox in developer tool naming. The instinct among technical founders is to name for the in-group: the developers who will be the first users, the people who will get the joke, the audience that values cleverness over clarity. /dev/payments is a name for developers. Stripe is a name for the world.
This isn't snobbery. It's growth mathematics. Stripe's ambition was never to be a niche tool for developers who understand Unix file paths. It was to become the payments layer for the entire internet. A name that requires Unix literacy to parse caps the company's identity at its initial market — and initial markets are, by definition, the smallest a successful company will ever serve.
Scott Galloway calls this "naming for your Series D, not your seed round." The name you choose when you have ten customers needs to work when you have ten million. /dev/payments would have become increasingly absurd as Stripe expanded into lending, treasury management, corporate cards, and tax compliance. Stripe absorbs every expansion without strain because it doesn't describe any specific product.
## The $91.5 Billion Monosyllable
In February 2025, Stripe finalised a tender sale valuing the company at $91.5 billion. The payments volume flowing through the platform exceeded $1.4 trillion annually. The name "Stripe" appears on invoices in 195 countries, is spoken in earnings calls by executives at companies across every industry, and is typed into search engines millions of times per month.
None of this would be structurally impossible with a different name. But the name's properties — its monosyllabic efficiency, its phonetic crispness, its semantic flexibility — reduced friction at every point where the brand needed to cross a boundary. From developer tool to enterprise platform. From payments processor to financial operating system. From American startup to global infrastructure.
The research on name length and recall, compiled across studies published in Memory & Cognition and Psychonomic Bulletin & Review, consistently shows that shorter names are recalled more accurately under cognitive load. In a world where your company's name competes for attention against thousands of other names, emails, notifications, and advertisements every day, a single syllable is a significant structural advantage.
## The Lesson in the Slash
The forward slash that prevented incorporation in Delaware did the Collisons a favour they couldn't have recognised at the time. It forced a naming decision that might otherwise have been deferred indefinitely. Technical founders often treat naming as a problem to solve later — get the product right, and the name will sort itself out. But /dev/payments was already training early users to associate the product with a name that couldn't scale. Every month spent under that name would have made the eventual rename more expensive and more disruptive.
The slash broke. Stripe emerged. And a payments company that couldn't legally exist under its original name went on to process more money annually than most countries' GDP.
Sometimes the best thing a name can do is fail early enough that the right name still has room to work.