Why Is It Called Stripe? The Rename That Cost Nothing

The origin: a company named after a file path

Stripe was originally called /dev/payments, and replacing it took a couple of months and one arbitrary deadline. Here is the run of events, each telling attributed to whoever told it.

1. 2010: two brothers start a payments APIPatrick and John Collison, from Limerick, found the company in Palo Alto: a payments API a developer can call in a few lines instead of spending weeks opening a merchant account.
2. The first name is a file pathThey call it /dev/payments. On a Unix system, /dev holds device nodes, and writing to one is about as simple as an operation gets. The name is a promise: taking money should be that easy.
3. Delaware rejects the slashIn Patrick Collison’s telling: “We thought /dev/payments was a super awesome and cool name. The rest of the world didn’t agree. When we filed our paperwork in Delaware, we were rejected.”
4. The legal name is worse than the jokeThe slash gets spelled out. Greg Brockman, who joined in November 2010 and became the first CTO in 2013, records it as SlashDevSlashFinance; Patrick Collison’s retelling gives SlashDevSlashPayments. That two accounts disagree tells you how well it stuck.
5. It stops being funny in meetingsBrockman’s summary: “Imagine being in talks with a very serious banker from a very serious bank and then telling them you worked at ‘Slash Dev Slash Finance’. It’s not a great way to build trust.” Post arrived misaddressed too.
6. A script goes looking for a wordBrockman inverts the usual shortlist: generate random nouns, check by script which domains exist, email the owners. Several hundred emails go out. “Forge” is dropped once someone points out forgery.
7. A deadline picks itThe owner of stripe.com replies with a liveable price. By Patrick Collison’s telling nobody could choose between Stripe and PayDemon, so they set a date, 20 December 2010, and agreed to default to Stripe. The public launch follows in September 2011.

Note what forced the decision. Not a focus group, not a brand agency: an incorporation form, a bank’s patience, and the daily friction of saying the thing out loud.

What /dev/payments was actually saying

The old name deserves a defence, because it was a good piece of writing. On a Unix system, /dev is the directory of device nodes: files that are not really files, standing in for hardware. You write bytes to one and something happens in the physical world. Naming a payments API /dev/payments claimed money would work the same way. For the audience it targeted, that was a small work of art.

The problem was never that the joke was bad. It was that the joke had an audience, and the company needed a name for everyone outside it. “Stripe” was picked, by Brockman’s account, largely for what it lacked: no brand associations to fight, and mild positive echoes instead of a fixed meaning. Racing stripes. Striping across a RAID array. The magnetic stripe on a card. None of those is the product, and none is wrong either.

The mechanism: naming for the room, not the team

Every naming story turns on one decision, and Stripe’s is this: the founders worked out early that their name’s audience was much bigger than their in-group, and paid to fix it while the bill was nothing. /dev/payments named the product for the people who built it. “Stripe” names it for everyone who has to say it: a compliance officer, a bank’s onboarding team, a customer reading a line on a card statement, a regulator writing it into a letter.

That is a different move from Airbnb’s. “AirBed and Breakfast” was no in-joke, just an accurate description grown too long, and the fix was compression: squeeze it until it becomes a brand. Stripe compressed nothing. It threw the first name away and bought an unrelated word, because the problem was not length, it was audience. The compression play is worked through in why is it called Airbnb.

The closer relative is Slack, another plain one-syllable English word attached to a product built by and for technical teams. Both refuse to signal what the company sells, and both stay easy to say for customers whose first language is not English. Set them side by side in why is it called Slack: this corner of software keeps choosing the word your parents already know.

1. Phonetics: one syllable, one honest problem

Say it: Stripe. One syllable, one stress, and a spelling that comes straight back out of a single hearing with no fork between two plausible versions. Nobody has to say “that’s with a Y” or spell it letter by letter on a call, which is the most underrated property a name can have and precisely what the old name lacked.

• Nothing to clipCustomers shorten long names into something you did not choose. A one-syllable name has no shorter form, so the version in the market is the one you shipped.
• It spells itselfCommon word, common spelling, no invented letters. Heard once, typed correctly, which is precisely what a deliberately misspelled name gives up.
• The “str” caveatThree consonants stacked at the front is a shape other languages rebuild. Speakers without initial clusters insert a vowel, giving something like “su-to-raipu”. A real cost, not a fatal one.

The honest reading: this scores well, and the cluster is what keeps it off the ceiling. Names built on “str”, “spl” or “chr” are the likeliest to be re-shaped abroad, and it is better to know that in advance than to discover it in a meeting in Tokyo.

2. Memorability: the dictionary-word trade

This is where the analysis has to ignore the company and look at the word. “Stripe” is an ordinary English noun, so it takes the dictionary-word caveat: the reader already owns a picture of it, which makes recall effortless and ownership expensive. A coinage starts life belonging to nobody. A dictionary word starts life belonging to everybody, and the brand buys the association back one customer at a time.

The trade is two-sided, which is why this lands in Good rather than Fair. The founders bought distinctiveness within the category, the kind that matters commercially. In 2010 the payments field was thick with names built from “pay”, “bill”, “charge” and “merchant”, including the team’s own runner-up, and a word with no payments content stood out by refusing to join in. That reasoning is set out in descriptive vs. abstract brand names.

One caution before copying it: a meaning-light common word is hard to defend and hard to search for early on, when every query returns clothing and paint. Stripe absorbed that cost with a decade of usage. A famous example does not prove the shape works for a company with no traffic yet.

3. Cross-language: no flags, and one predictable reshape

The check finds no flags in the languages examined: nothing rude, nothing unfortunate when the word is clipped or heard quickly, no diacritics to lose in transit. The honest phrasing is no flags in the languages checked, never a blanket “safe”, because no automated pass clears every dialect on earth.

What it does flag is shape rather than meaning. The opening cluster changes in transit, and the English sense travels nowhere: elsewhere, “stripe” is an arbitrary sound. For a company selling infrastructure to developers who read English documentation all day, that is close to free. For a consumer brand it would be a bigger question.

• Check the sound, not the spellingMost cross-language trouble is heard, not read. Say the name at speed to a native speaker of each language you sell in, and listen to what comes back.
• Expect clusters to be rebuiltConsonant stacks get vowels inserted, and the result becomes the local version of your name whether you approve it or not. Decide in advance if you can live with it.
• Know which markets read a meaningSplit your markets into languages where your name is a word and languages where it is a sound. Both are workable; not knowing which is which produces surprises.

The full method is in the cross-language safety checklist.

The Namoly Report simulation: “Stripe”

Here is how “Stripe” performs against the four weighted checks, scored on the name rather than the company it became. Illustrative worked example: the overall is the weighted mean of the sub-scores, using the weights every real report uses (domain 0.30, memorability 0.25, phonetics 0.25, cross-language safety 0.20).

• Global Namoly Score67 / 100Good
• ReadabilityHighOne syllable, spells itself
• Linguistic safetyMediumNo flags in the languages checked

1. Domain availabilityweight 0.30The string existed long before the company, so stripe.com was an acquisition rather than a registration: an owner to find, email and pay. A common one-syllable noun is the hardest class of .com to get, and every meaningful extension now resolves to the company.52Fair
2. Memorability & distinctivenessweight 0.25The honest ding. An ordinary English word every reader already owns a picture of: effortless to recall, expensive to own. Distinctive inside payments, undistinctive in general, because a dictionary word arrives carrying whatever the dictionary already put in it.64Good
3. Phonetics & readabilityweight 0.25One syllable, one stress, and it types straight back out from a single hearing. The “str” onset is the only friction: three consonants stacked at the front is exactly the shape some languages rebuild with an inserted vowel.84Strong
4. Cross-language safetyweight 0.20No flags in the languages checked. Medium rather than High because the word carries an English sense that does not travel, and the opening cluster gets reshaped by speakers whose languages do not stack consonants that way.74Good
5. Overall Namoly Scoreweighted meanA plain, sayable word that cost a premium domain and trades ownability for working in every room the company has to walk into. Good rather than Strong, and deliberately so: the founders were not buying distinctiveness, they were buying the end of the spelling conversation.67Good

• Strong80–100Short, distinctive, sticks after one exposure.
• Good60–79Solid and workable; minor trade-offs.
• Fair40–59Usable but forgettable or hard to spell.
• Weak0–39Reconsider; friction outweighs the upside.

Illustrative analysis for education. Every number in a real report ships with a justification, a confidence signal, and a tip. Not checked here: trademark and social-handle availability.

What founders can take from a name that got replaced

Most naming case studies celebrate a first choice. This one celebrates a second one, made early and cheaply, which is a more useful thing to copy.

• Name for the room, not the teamYour name gets said by people outside your subculture: bankers, lawyers, procurement, a receptionist reading it off a form. If it only lands with people who share your references, you named the product for the people who built it.
• Jokes and namespaces do not survive paperworkA legal name starting with a slash is a bug. Punctuation, casing tricks and namespace puns break on incorporation forms, bank records, invoices and card statements: systems with no sense of humour and no support for your character set.
• Rename before anyone knows youThe cost tracks how many people have learned the old name. At stealth stage it is a domain, a logo and an afternoon. After a few years of press it is a migration project with real traffic at stake.
• A meaning-light word gives you roomA stripe is a band of colour. It says nothing about payments, so there is nothing to outgrow when the company stops being only about payments. Names that describe today’s product date as fast as today’s product.
• Set a decision date, then defaultThey could not choose, so they picked a date and a default instead of arguing. That bounds an unbounded debate, and a good-enough name shipped beats a perfect name still under discussion.

The namespace trap catches technical founders most often, because a clever name inside a package registry feels like the same object as a company name, and it is not. Sub-sector conventions and the namespaces a free .com will never warn you about are in how to name a tech startup, with the wider process in how to name a startup.

The rename was free because nobody was watching

The most transferable part of this story is not the word they chose, it is the timing. The change came during a stealth period, before press, before customers had learned the old name and before any of it had accumulated search traffic. The bill was a domain and an afternoon.

Run the same change three years later and it is a different project: redirects, contracts, card statement descriptors, app store listings, integration docs written by other people, and every customer who has to be told that the company they trust with money is now called something else. The reasoning does not change, only the invoice. The test for whether that bill is worth paying is in when to rename your startup.

One honest footnote on the domain: Stripe did not find a free .com, it found an owner and paid, and the price has never been made public. Budget for that conversation if you want a one-word common noun. Tech startup domain names covers the alternatives.

Frequently asked questions

What was Stripe originally called?

/dev/payments. The company the Collison brothers founded in 2010 spent its stealth period under that name, a Unix file path chosen because the product was meant to make taking payments as easy as writing to a device node.

Why did Stripe change its name from /dev/payments?

Because the name could not survive paperwork. By the founders’ own telling, Delaware would not accept a corporate name with a leading slash, so the company incorporated under a spelled-out version nobody could parse: SlashDevSlashFinance in Greg Brockman’s account, SlashDevSlashPayments in Patrick Collison’s. Explaining it to bankers cost credibility on every call.

What does the name Stripe mean?

Nothing in payments, which was the appeal. In Greg Brockman’s account it was picked partly for being free of existing brand associations, while everything it evoked was at least vaguely positive: racing stripes, striping across a RAID array, the magnetic stripe on a card.

Did Stripe buy the stripe.com domain?

Yes. The team generated random nouns, checked by script which domains existed, and emailed several hundred owners; the owner of stripe.com came back with a price they were willing to pay. The amount has not been made public.

When did Stripe get its name?

Around the end of 2010. By Patrick Collison’s telling nobody could choose between Stripe and PayDemon, so they set a deadline of 20 December 2010 and agreed to default to Stripe if nothing better turned up. Nothing did, and the company launched publicly in September 2011.

How was this score calculated?

The numbers here are illustrative, built from the same four checks Namoly runs on any name: domain availability, memorability, phonetics, and cross-language safety. The overall is the weighted mean of the sub-scores, using the canonical weights (0.30, 0.25, 0.25, 0.20).