Stripe's payment API journey began in 2011 with a revolutionary seven-line integration that transformed how businesses handled credit card processing. The initial design introduced two core concepts: Tokens for secure card data handling and Charges for immediate payment processing. This simple approach helped businesses avoid complex PCI compliance requirements while providing instant payment results.

By 2015, Stripe faced its first major challenge when adding ACH debit and Bitcoin support. These payment methods introduced asynchronous processing and customer-initiated transactions that broke the existing synchronous model. ACH payments could take days to finalize, while Bitcoin required customers to actively send funds before any payment could be processed. The engineering team had to create new resources like BitcoinReceiver and add pending states to handle these complexities.

Over the next two years, Stripe unified these disparate payment methods with the Sources API, combining Tokens and receiver-like resources into a single client-driven state machine. This evolution supported dozens of payment methods including cards, bank transfers, and digital wallets across different countries. The Sources API represented a significant architectural shift that enabled Stripe to scale globally while maintaining developer-friendly integrations. This 10-year evolution demonstrates how payment infrastructure must continuously adapt to support diverse global payment ecosystems while keeping the developer experience simple.