Skip to content
Hraness
Theme
Appearance

Stripe History dataset

282 sourced events

These YAML files hold the data behind the timeline and the valuation, volume, and revenue pages. Each history entry has a date, title, category, summary, confidence level, and at least one source, plus a status where one applies. The research files hold the source catalog, valuation observations, leadership appearances, the definition of each research collection, and the log of research runs. The dataset and website code are available under the MIT License in the Stripe History repository.

Questions this history answers

How did Stripe start, and who has led the company?
Follow the sourced records for Stripe's origins and early company and executive and team changes.
What companies has Stripe acquired?
The Stripe acquisitions history distinguishes completed acquisitions, talent acquisitions, announced agreements, and reported deal discussions.
How have Stripe's funding and valuation changed?
Compare fundraising and liquidity events with the sourced Stripe valuation history.
How much payment volume has Stripe processed?
The annual payment and total volume record charts each disclosed figure on a linear scale.
What sourced net-revenue figures exist?
The net-revenue record charts sourced company full-year figures on a linear scale. Each figure comes from an event in the company milestones category, and years without a disclosed figure are left out.
When did Stripe launch products and expand globally?
Browse product launches, country expansion, and payment and payout expansion as separate sourced chronologies.

Sources and research files

Browse the valuation history or the net-revenue record, or inspect the machine-readable research records directly.

Weekly discovery also reads first-party publication feeds, including Stripe Economics, Works in Progress, Stripe Press, the Stripe Blog, the Stripe.dev Blog, and Cheeky Pint. The publishing history records those projects. It does not ingest every newsletter essay as its own event.

Read a history file

Each file under history/ has a category record, an events list with the newest event first, and the schema version stripe-history/history/v2. The appearances file has its own layout. Read a history file with a YAML parser that keeps each date as written, such as the yaml package this site uses. In Bun 1.3.14, the built-in YAML.parse reads a month-only date such as 2025-07 as the number 2025.

curl --fail --location --output acquisitions.yml https://hraness.com/stripe/history/acquisitions.yml
bun add yaml
bun -e 'import { parse } from "yaml"; const data = parse(await Bun.file("acquisitions.yml").text()); console.log(data.category.id); for (const event of data.events) console.log(event.id, event.date, event.date_precision, event.confidence, event.status ?? "");'

The output starts with acquisitions, then prints one line per event: its ID, date, date precision, confidence, and status. Among them are the Privy completion, dated to the month, the announcement before it, and a reported offer that Airwallex rejected:

privy-acquisition-completed 2025-07 month confirmed Completed
privy-acquisition-announced 2025-06-11 day confirmed Agreement announced; completed in July 2025
airwallex-acquisition-offer-rejected 2018-10 month reported Reported offer rejected; no agreement

  • date and date_precision: the date is written as YYYY, YYYY-MM, or YYYY-MM-DD, and the precision says which: year, month, or day. A year or month is not an exact day.

  • confidence: confirmed, reported, or disputed. It describes the evidence for the event, and the timeline prints it beside every event that is not confirmed.

  • status: where present, the state of a deal or launch in words. A confirmed agreement is not a completed acquisition until its status or a later event records the completion.

  • source_ids: each ID matches an id in the source catalog YAML listed above, which gives the source's title, publisher, kind, and URL, and its publication date when known.

  • amount: display keeps the figure's wording, including words such as reported. value is optional, so check for it before adding amounts.

  • annual_volume and annual_revenue: a calendar year, a USD value, and a qualifier such as lower-bound or approximate. Keep the qualifier with the number.

The history schema defines every field.