Stripe’s early promise hinged on a headline that read “seven lines of code,” a claim that captured the industry’s imagination. In practice, the snippet that created a Charge boiled down to roughly seven curl commands. Developers could spin up a terminal, paste the code, and immediately see a successful transaction, a feat that felt almost magical.

Stripe’s first public API, launched in 2011, focused on U.S. credit cards. Alongside the Charge object, the team released Stripe.js, a JavaScript library that tokenized card data, letting merchants bypass PCI hassles. The Token and Charge concepts became the backbone of the payment flow, simplifying integration for hundreds of thousands of sites.

In 2015, Stripe broadened its reach with ACH debit and Bitcoin. ACH introduced a pending state to Charges, reflecting days‑long settlement. Bitcoin required a new BitcoinReceiver resource, a temporary holder that customers filled before a Charge could be created. These additions highlighted the difficulty of abstracting diverse payment methods under a single API.

Over the next two years, Stripe added more customer‑initiated methods, realizing that creating a new resource for each would clutter the API. The company pivoted toward a unified Payments API, later evolving into PaymentIntents, which consolidated state handling and reduced integration friction. Today, developers rely on this streamlined system to process millions of transactions daily.