Stripe – Making Internet Payments Not Suck

In 2010, Patrick Collison and his younger brother John were frustrated. The brothers, Irish immigrants who had both dropped out of college to pursue entrepreneurial projects, were trying to build web applications and kept running into the same problem: accepting payments online was absurdly complicated. To process credit card transactions, developers needed to navigate baroque legacy systems built for brick-and-mortar retail, fill out extensive paperwork, wait weeks for merchant account approval, integrate clunky APIs with poor documentation, and deal with archaic bank infrastructure that seemed designed in the 1970s (because it was). For developers accustomed to elegant tools and simple APIs in other domains, the payments infrastructure felt like archaeological software that nobody had bothered to modernize.

The brothers believed that payments should be as easy as any other API call—a few lines of code that would let developers charge credit cards without thinking about merchant accounts, PCI compliance, or banking relationships. They built a prototype and called it "/dev/payments" (a Unix joke suggesting payments should be as simple as reading from a device file), then renamed it Stripe. The core value proposition was radically simple: developers could integrate Stripe into their applications in minutes rather than weeks, start processing payments immediately, and let Stripe handle the complexity of banking, fraud detection, and regulatory compliance. The idea seemed obvious, but incumbent payment processors had no incentive to simplify systems that generated revenue from complexity, and banks had no reason to accommodate startup needs when they had established relationships with large merchants.

Stripe launched publicly in September 2011 after a private beta that attracted early adopters through Y Combinator connections and developer word-of-mouth. The adoption was immediate among the startup community—founders who had been building payments infrastructure themselves or struggling with PayPal's limitations rushed to Stripe. Within months, thousands of companies were processing payments through Stripe. Within a decade, Stripe would power payments for millions of businesses globally, process hundreds of billions in annual volume, be valued at $95 billion (making it one of the most valuable private companies in the world), and fundamentally reshape how money moved on the internet. The company succeeded by making something that was complicated and frustrating become simple and elegant, proving that even in heavily regulated, established industries dominated by incumbents, superior developer experience could win.

The Developer-First Philosophy: Documentation as Marketing

Stripe's founding insight was that winning developers would win the market. If developers loved using Stripe and could integrate it easily, they would choose Stripe for their projects, and those projects would generate payment volume as they grew. This bottom-up adoption model contrasted with traditional enterprise sales where payment processors courted CFOs and CEOs with relationship selling. Stripe bet that empowering individual developers to choose payment infrastructure would be more effective than top-down sales, a contrarian strategy that required building products developers genuinely loved.

The focus on developer experience manifested everywhere but most visibly in documentation. Stripe's API documentation became legendary in the developer community—clear, comprehensive, well-organized, with code examples in multiple languages that actually worked when copied and pasted. The documentation was beautiful, with careful typography and visual design that made reading technical specifications pleasant rather than tedious. Developers shared Stripe documentation examples as models of how technical documentation should be done, generating organic marketing that no amount of paid advertising could match.

The API design itself reflected obsessive attention to developer ergonomics. Stripe used RESTful conventions consistently, provided sensible defaults that worked for common use cases, returned detailed error messages that explained what went wrong and how to fix it, and maintained backward compatibility religiously so that code written years ago continued working. These design decisions required significant engineering effort—maintaining backward compatibility while adding features was far more difficult than breaking changes—but they built trust that Stripe was a reliable platform worth building businesses upon.

The integration process was shockingly simple compared to alternatives. To accept payments, developers included Stripe's JavaScript library, added a few HTML elements to create a payment form, and wrote a few lines of backend code to process charges. The entire process could be completed in an afternoon, compared to weeks or months with traditional payment processors. The simplicity was enabled by Stripe handling enormous complexity behind the scenes—maintaining PCI compliance, managing bank relationships, handling fraud detection, reconciling transactions—but presenting a clean, simple interface to developers.

The developer evangelism was subtle and authentic. Stripe engineers participated in developer communities, contributed to open-source projects, gave conference talks about payment infrastructure challenges, and built tools that the developer community needed even when those tools didn't directly generate revenue. This authentic engagement built goodwill and credibility that traditional marketing couldn't achieve. Developers trusted Stripe because Stripe understood developers and treated them as customers worth serving excellently rather than obstacles to navigate en route to signing contracts with CFOs.

The Infrastructure Complexity: Simple Surface, Deep Foundation

The simplicity that Stripe presented to developers concealed extraordinary complexity in the underlying infrastructure. Processing payments required navigating a byzantine system of banks, card networks (Visa, Mastercard, American Express), acquiring banks, issuing banks, regulations varying by jurisdiction, fraud detection, chargebacks, disputes, and numerous edge cases that occurred rarely but required handling. Stripe's achievement was building infrastructure that handled this complexity reliably while exposing a clean, simple API.

The bank relationships were foundational and difficult to establish. Stripe needed partnerships with acquiring banks to settle transactions, relationships that traditional payment processors had built over decades. Banks were conservative institutions skeptical of startups and concerned about fraud risk and regulatory compliance. Stripe needed to convince banks that the company could manage risk effectively and that the developer-focused model wouldn't attract disproportionate fraud. The early bank relationships were hard-won and provided competitive moats that would-be Stripe competitors struggled to replicate.

The fraud detection system was crucial and sophisticated. Credit card fraud was endemic in online commerce, and payment processors bore substantial fraud risk through chargebacks—when customers disputed charges, the payment processor often had to refund the customer and absorb the loss. Stripe built machine learning systems analyzing billions of transactions to identify fraud patterns, assigning risk scores to transactions in real-time, and blocking suspicious charges before they completed. The fraud detection needed to be accurate enough to catch real fraud while generating few false positives that would block legitimate transactions and frustrate customers.

The PCI compliance requirements were extensive and expensive. PCI DSS (Payment Card Industry Data Security Standard) specified hundreds of security controls that any company handling credit card data needed to implement and maintain. Compliance required annual audits, security assessments, and continuous monitoring. Stripe achieved PCI Level 1 compliance—the highest level, requiring the most rigorous controls—allowing merchants using Stripe to greatly simplify their own compliance. Stripe absorbed the compliance burden and cost, providing enormous value to merchants who would otherwise need to implement these controls themselves.

The geographic expansion required navigating different regulatory regimes, banking systems, payment methods, and currencies in each country. Launching in a new country wasn't just translation and localization—it required establishing local bank relationships, understanding local regulations, supporting local payment methods (Alipay in China, iDeal in the Netherlands, SEPA direct debit in Europe), and handling currency conversion and multi-currency settlement. The expansion was slow and expensive, but it created network effects where Stripe's global presence became valuable to businesses operating internationally.

The Pricing Model: Simplicity and Transparency

Stripe's pricing—2.9% + $0.30 per successful card charge for most transactions—was revolutionary for its simplicity and transparency. Traditional payment processors used complex pricing structures with setup fees, monthly fees, per-transaction fees, percentage fees, statement fees, PCI compliance fees, chargeback fees, and various other charges that made it difficult to predict actual costs. The pricing was often customized through negotiation, with different merchants paying different rates based on volume and bargaining power.

Stripe's flat rate pricing eliminated negotiation, made costs predictable, and was the same for everyone—a startup processing $1,000 monthly paid the same percentage as an established business processing millions. This pricing democracy was radical in an industry built on negotiated relationships and volume-based discounting. Critics argued that Stripe's pricing was expensive for high-volume merchants who could negotiate better rates with traditional processors, and this was true—Stripe acknowledged that the flat pricing traded lower rates at high volume for simplicity and ease of use at all volumes.

The transparency extended to how Stripe handled interchange fees—the fees that card networks charged for processing transactions. Stripe explained these costs clearly and showed how its own take (the difference between what it charged merchants and what it paid in interchange and other costs) was reasonable given the value provided. This transparency built trust and differentiated Stripe from processors whose pricing was deliberately opaque to maximize revenue extraction.

The pricing model also aligned incentives well: Stripe earned revenue only when merchants successfully processed payments, creating shared interest in merchants succeeding and growing. Traditional processors with setup fees and monthly charges earned revenue regardless of whether merchants succeeded, creating misalignment where processors profited from signing merchants who later failed. Stripe's model meant the company needed merchants to grow and thrive, encouraging Stripe to invest in tools and support that helped merchants succeed.

However, the flat pricing created pressure as Stripe scaled. Large merchants represented most of the payment volume, and those merchants could get better rates elsewhere. Stripe eventually introduced customized pricing for high-volume merchants, acknowledging that flat pricing couldn't be maintained across all customer segments. The move toward tiered pricing was pragmatic but represented a retreat from the democratic simplicity of early Stripe pricing. The company maintained that even customized pricing was simpler and more transparent than traditional processor pricing, but the original purity was compromised.

The Expansion Strategy: Building the Entire Stack

Stripe's ambition extended beyond basic payment processing to building a complete financial infrastructure platform. The expansion included dozens of products addressing different aspects of online commerce: Stripe Billing for subscription management, Stripe Connect for marketplace payments, Stripe Radar for fraud detection, Stripe Terminal for in-person payments, Stripe Issuing for creating card programs, Stripe Treasury for financial accounts, Stripe Capital for merchant lending, and many others. Each product addressed real merchant needs and created additional revenue while increasing customer lock-in.

The subscription billing product (Stripe Billing) was particularly strategic. SaaS businesses needed not just payment processing but subscription management—handling recurring charges, metering usage, managing plans and pricing, handling upgrades and downgrades, calculating prorated charges, managing failed payments, and providing revenue reporting. Building this infrastructure was complex, and most SaaS startups built it poorly or expensively. Stripe Billing provided sophisticated subscription management out of the box, making it dramatically easier to launch and operate subscription businesses. The product generated recurring revenue for Stripe while creating switching costs—migrating subscription infrastructure after going live with customers was painful and risky.

The marketplace product (Stripe Connect) addressed the needs of platforms like Lyft, Shopify, and Kickstarter that facilitated payments between third parties. These platforms needed to collect money from end customers and distribute it to sellers, drivers, or creators while taking their own commission. Connect handled the complexity of multi-party payments, including compliance with money transmission regulations, tax reporting (1099 forms), identity verification, and managing individual merchant accounts. The product was technically sophisticated and created deep integration with platform customers who found Connect essential to their business models.

The physical payments expansion (Stripe Terminal) moved Stripe beyond online transactions into point-of-sale. The product provided hardware and software for accepting card-present transactions, integrating seamlessly with Stripe's online payment processing. This omnichannel capability was increasingly important as retail businesses operated both online and in physical locations and wanted unified payment processing. Terminal was expensive to build—requiring hardware development, certification, inventory management, and distribution—but it addressed a large market and prevented merchants from using different processors for online and in-person payments.

The banking-as-a-service products (Issuing, Treasury) represented Stripe's most ambitious expansion into financial services that were traditionally banks' exclusive domain. Stripe Issuing allowed businesses to create and distribute their own branded debit or credit cards, serving use cases like employee expense cards, creator payouts, or customer rewards programs. Stripe Treasury allowed platforms to offer financial accounts to their customers, enabling features like instant payouts, checking accounts, or savings products without obtaining banking licenses. These products required deep partnerships with banks and navigation of complex banking regulations, but they positioned Stripe to capture more of the financial services value chain.

The Atlas Program: Incorporating the World

Stripe Atlas, launched in 2016, provided an unexpected and philosophically significant service: helping entrepreneurs anywhere in the world incorporate a company in Delaware, open a U.S. bank account, and access Stripe's payment processing—all remotely without needing to visit the United States. The service cost $500 and handled the legal, banking, and tax paperwork that was complex and expensive for international founders. Atlas was not obviously a payments business, but it represented Stripe's broader mission of increasing internet commerce globally.

The program was inspired by the Collison brothers' own immigration experience and belief that entrepreneurial talent was globally distributed but opportunity was concentrated in specific geographies. A developer in Lagos, Dhaka, or Jakarta might have the skills and ideas to build an internet business but couldn't easily access the financial infrastructure required to operate globally. Atlas reduced these barriers, enabling entrepreneurs to join the global internet economy regardless of their physical location.

The impact was significant: tens of thousands of companies were incorporated through Atlas, including many in countries where startup formation was difficult or where local banking systems made it impossible to accept international payments. The program generated goodwill, attracted customers who would process payments through Stripe, and advanced Stripe's mission in ways that were good for business and good for global economic development. The alignment between mission and business value was powerful and authentic.

However, Atlas also raised questions about regulatory arbitrage and tax avoidance. Stripe was helping companies incorporate in the U.S. (specifically Delaware, known for business-friendly laws) regardless of where they actually operated, potentially allowing them to avoid local taxes and regulations. Some criticized Atlas as facilitating regulatory evasion, while others argued it was helping entrepreneurs escape dysfunctional local systems and corruption. The debate illustrated tensions in global commerce between national sovereignty and internet-enabled business models that transcended borders.

The Atlas program also demonstrated Stripe's willingness to invest in products that might not generate immediate returns but advanced long-term strategic goals. Atlas companies processed relatively small payment volumes initially, but they represented the global expansion of internet commerce and potential future large customers. The investment reflected patient capital and long-term thinking that was difficult for public companies facing quarterly earnings pressure but possible for well-funded private companies with supportive investors.

The Fintech Competition: Square, Adyen, and Everyone Else

Stripe faced competition from multiple directions: traditional payment processors attempting to modernize, banks launching developer-friendly APIs, and fellow fintech startups building payments infrastructure. The most prominent competitors were Square (founded by Jack Dorsey), Adyen (Dutch payment processor), and PayPal (the original online payments company). Each had different strengths and addressed different customer segments, creating a competitive landscape where no single player dominated completely.

Square's competition was primarily in physical retail and point-of-sale, where Square had pioneered simple payment acceptance through the Square Reader attached to smartphones. Square's strength was small businesses and physical merchants, markets where Stripe was relatively weak until launching Terminal. The companies' customer bases overlapped minimally initially, but both expanded toward each other's territories, with Square launching online payment products and Stripe launching physical payment hardware. By the late 2010s, they competed across most payment use cases.

Adyen positioned itself as serving the largest enterprises and provided a unified platform processing payments globally. Adyen's advantage was its own direct acquiring licenses in multiple countries, avoiding middlemen and reducing costs for high-volume merchants. Large companies including Uber, Spotify, and Facebook used Adyen for significant portions of their payment processing. Adyen's pricing was opaque and customized (similar to traditional processors), contrasting with Stripe's transparent pricing. The companies competed for large enterprise customers, with Adyen often winning on price for very high volumes and Stripe winning on developer experience and feature completeness.

PayPal represented the incumbent online payment company, with hundreds of millions of accounts and strong consumer brand recognition. PayPal's strength was its two-sided network—consumers had PayPal accounts and could pay merchants instantly without entering card details. However, PayPal's developer experience was poor, integration was difficult, and the company had reputation for arbitrary account freezes and poor customer service. Stripe won developer mindshare away from PayPal by being dramatically easier to integrate and providing better support. PayPal maintained scale through network effects and consumer-facing payment options but lost developer loyalty.

The competitive landscape also included regional players with strong positions in specific markets: Mercado Pago in Latin America, Razorpay in India, PayStack (acquired by Stripe) in Africa, and numerous others. These regional competitors understood local payment methods, regulations, and business practices better than global players. Stripe's strategy combined direct competition through geographic expansion and strategic acquisitions of regional players to gain local expertise and presence quickly.

The competition dynamics illustrated that payments was not a winner-take-all market. Different segments valued different attributes—small businesses wanted simplicity, large enterprises wanted low costs, developers wanted excellent APIs, consumers wanted convenience. Multiple payment providers could coexist by serving different segments effectively. However, the market did show concentration tendencies with a few major players capturing most volume and smaller players struggling to achieve scale necessary for profitability.

The Startup Ecosystem Dependence: Growing by Powering Growth

Stripe's early customers were disproportionately startups—new companies building internet businesses that needed payment infrastructure. This customer concentration created opportunities and risks. The opportunity was that successful startups would grow into large companies processing billions in payment volume, generating enormous revenue for Stripe as they scaled. The risk was that most startups failed, meaning Stripe invested in onboarding and supporting customers who might never generate significant revenue.

The Y Combinator connection was particularly important. Patrick Collison had participated in Y Combinator, and Stripe maintained close relationships with YC partners including Paul Graham and Sam Altman. Stripe became the default payment processor recommended to YC companies, creating a pipeline of startup customers. As YC alumni companies including Airbnb, Dropbox, and Reddit grew, Stripe's revenue grew proportionally. The symbiotic relationship benefited both parties: YC companies got excellent payment infrastructure, and Stripe got customers at the earliest stages who would potentially grow enormously.

The dependency created challenges as startup funding cycles shifted. During boom periods when venture capital flowed freely and startup formation was high, Stripe's customer acquisition naturally accelerated. During downturns when startup creation slowed and failures increased, Stripe's growth would be constrained. The 2022-2023 technology downturn, with mass layoffs, startup failures, and reduced venture funding, pressured Stripe's growth as fewer new companies launched and existing customers reduced volume.

The expansion toward larger enterprise customers addressed this startup dependency by diversifying customer base. Large companies including Amazon, Google, Salesforce, and numerous others adopted Stripe for portions of their payment processing. These enterprise customers provided stable, predictable revenue that was less volatile than startup customer revenue. However, serving enterprises required different capabilities—extensive customization, dedicated support teams, negotiated pricing—that complicated Stripe's originally simple model.

The platform customers (companies using Stripe to enable payments for their own customers, like Shopify, Lyft, and Instacart) became strategically crucial. These customers processed enormous volumes and generated substantial revenue, but they also created dependence—if major platform customers migrated away from Stripe, revenue would decline significantly. The platform business was attractive for its scale but also created concentration risks that Stripe needed to manage carefully.

The Valuation Volatility: From $95B to $50B and Back

Stripe's private valuation peaked at $95 billion in March 2021 during the technology funding boom, making it the most valuable private startup in the U.S. The valuation was based on expectations of continuous high growth, expanding margins, and eventual public offering that would provide liquidity. However, the valuation proved unsustainable as technology stocks collapsed in 2022 and profitability expectations shifted. In January 2023, Stripe cut its internal valuation by about 50% to $50 billion, acknowledging that private market valuations needed to reflect public market reality.

The valuation volatility reflected broader challenges in startup valuation. Private companies raised capital at valuations that were essentially negotiated numbers between companies and willing investors rather than market-determined prices from continuous trading. During boom periods, investors competed to invest in high-growth companies and accepted valuations that assumed sustained growth and eventual public market multiples. During downturns, those assumptions were questioned, and valuations needed to reset.

For Stripe specifically, the valuation questions centered on growth rates and profitability. The company was growing revenue rapidly but operating at losses or minimal profitability while investing heavily in product development, geographic expansion, and team building. The high valuation assumed that Stripe could achieve and sustain high growth rates while eventually achieving attractive margins. If growth slowed or margins remained compressed due to competition, the valuation would need to decline.

The employee impact of valuation changes was significant. Stripe's compensation included substantial equity grants, and employee net worth on paper fluctuated by hundreds of thousands or millions as the valuation changed. The 2023 valuation cut reduced employee wealth substantially, creating morale challenges and retention risks. Stripe addressed this partly through liquidity programs allowing employees to sell some shares to institutional investors at the reduced valuation, providing cash that wasn't dependent on future valuation recovery.

The valuation also raised questions about IPO timing. Stripe had delayed going public despite reaching scale where IPO was feasible, preferring to remain private to avoid quarterly earnings pressure and public market scrutiny. However, the valuation volatility created pressure for liquidity—employees wanted the ability to sell shares, and investors wanted realizations on their investments. The timing of Stripe's eventual IPO would significantly impact how the company was perceived: going public at valuations below the $95 billion peak would be seen as disappointing, even if the actual valuation and business were strong by historical standards.

The Collison Brothers: Technical Leaders in Suits

Patrick and John Collison's leadership was unusual in the technology industry for combining deep technical expertise with comfort operating in traditional finance and business contexts. The brothers could write code, discuss arcane technical topics about payment infrastructure, and also negotiate with bank executives, navigate regulatory environments, and represent Stripe to traditional business audiences. This combination was rare and valuable, allowing Stripe to bridge startup culture and established financial services industry.

The brothers' relationship and collaboration was central to Stripe's culture and operations. Patrick served as CEO while John served as President, with responsibilities divided but overlapping. The close partnership allowed rapid decision-making and aligned leadership vision. However, it also created questions about succession and governance—if one or both brothers left, could Stripe maintain its culture and strategic direction? The dependence on founder leadership was both strength and potential vulnerability.

The intellectual curiosity and long-term thinking were distinctive characteristics. The Collisons were known for reading extensively, funding scientific research through their philanthropic efforts, and thinking about Stripe's role in long-term economic development rather than just quarterly results. This patient capital approach was enabled by private ownership and supportive investors but was also genuine to the founders' values and vision. The long-term orientation allowed investments in products like Atlas that might take years to generate returns.

The public presence was carefully managed. The Collisons gave interviews and conference presentations regularly but maintained relatively low profiles compared to celebrity CEOs like Musk or Zuckerberg. The measured public engagement avoided controversy while building credibility. The tone was thoughtful, technical, and focused on Stripe's mission rather than personal brands. This restraint was strategic and temperamental—the brothers seemed genuinely more interested in building infrastructure than cultivating celebrity.

The leadership style emphasized hiring exceptional people and giving them autonomy rather than micromanaging. Stripe became known for hiring talented engineers and operators from prestigious institutions and companies, building a culture of excellence and high expectations. The approach created strong team but also generated criticism about elitism and lack of diversity. The company acknowledged these concerns and worked to improve diversity, but the cultural foundations of hiring from elite networks persisted.

The Global Expansion: Internet Commerce Everywhere

Stripe's geographic expansion was strategic and challenging. The company needed to launch in multiple countries to serve globally operating businesses and to address markets where internet commerce was growing rapidly. However, each country required significant investment in local bank relationships, regulatory compliance, payment method support, and operations. The expansion was expensive and slow, but it created competitive moats and positioned Stripe to capture the growth of global internet commerce.

The priorities reflected strategic decisions about where to invest limited expansion resources. Stripe launched in developed markets with large existing internet commerce volumes first (U.S., Canada, Western Europe, Australia), then expanded to high-growth emerging markets (India, Brazil, Southeast Asia), and only later to smaller markets. The sequencing was pragmatic but meant that entrepreneurs in smaller or less developed markets waited years for Stripe access, limiting Stripe's stated mission of expanding internet commerce globally.

The local payment method support was crucial for success in many markets. Credit cards dominated in the U.S. and some European countries, but alternative payment methods were essential elsewhere: direct bank transfers in the Netherlands (iDeal), QR code payments in China (Alipay, WeChat Pay), local card schemes in various countries, and cash-based payment methods in markets with low banking penetration. Supporting these payment methods required local partnerships and technical integrations, complicating Stripe's infrastructure but necessary for competitive viability.

The regulatory environment varied dramatically across jurisdictions. Some countries welcomed foreign payment companies and had clear regulatory frameworks; others had complex licensing requirements, data localization mandates, or nationalist preferences for domestic companies. Stripe needed to navigate these varied environments, obtaining necessary licenses, adapting products to local requirements, and sometimes partnering with local companies to facilitate market entry.

The acquisitions strategy complemented organic expansion. Stripe acquired PayStack (African payments platform) in 2020 for over $200 million, gaining established presence in African markets and local expertise that would have taken years to build organically. Similar acquisitions in other regions allowed Stripe to accelerate geographic expansion while buying rather than building local knowledge and relationships. The acquisition strategy was expensive but effective, though it also represented admission that organic global expansion was too slow to capture growth opportunities.

Conclusion: Infrastructure That Enabled the Internet Economy

Stripe's impact extended beyond its own commercial success to enabling millions of businesses to operate online that couldn't have done so otherwise. The simple API and transparent pricing democratized payment acceptance, allowing individuals and small businesses to start accepting payments as easily as large enterprises. The infrastructure platform powered the SaaS boom, creator economy, gig economy platforms, and countless internet businesses that depended on easy payment processing. The economic activity enabled by Stripe likely exceeded by many multiples the value Stripe itself captured.

The brothers built Stripe by identifying that payments infrastructure was broken, understanding that developers were the key constituency to win, and executing brilliantly on developer experience. The focus on making complex systems simple and elegant—developer documentation, API design, pricing transparency—created competitive advantages that were difficult for incumbents to replicate. The advantages were partly cultural (developer-first thinking) and partly execution (actually delivering excellent experience), and both were essential.

The company's ambition extended beyond payments to building comprehensive financial infrastructure for the internet economy. The expansion into subscription management, banking-as-a-service, corporate cards, lending, and other financial services positioned Stripe as fundamental platform for internet commerce. Whether Stripe could maintain its developer-friendly culture and execution excellence while operating these diverse, complex businesses was ongoing challenge. The pressure to serve enterprise customers, customize solutions, and achieve profitability could conflict with the simplicity and elegance that made Stripe special initially.

The future included existential questions: Would Stripe go public and face quarterly earnings pressure that might compromise long-term vision? Would competition from tech giants, banks, and fintech startups erode margins and market share? Would regulatory changes or economic downturns threaten the business model? Could Stripe maintain culture and execution quality as it scaled to tens of thousands of employees globally? These uncertainties were significant, but Stripe had proven ability to execute difficult technical and business challenges. The company that made payments not suck for developers had reasonable prospects for continuing to power internet commerce for decades, though the path would be complicated and success was not guaranteed. The infrastructure for the internet economy was built, but maintaining and extending it would require the same excellence and long-term thinking that built it initially.