Re-designing an API to reach global scale

on YouTube ↗15m

" summary

Claims a single unified endpoint /v1/sources plus a reverse API for vendor-specific logic lets Stripe add dozens of payment methods without new charge endpoints. Implementation uses per-method adapters that speak a small network spec; flows are categorized as non-flow, redirect, verification, and receiver so iDEAL, Sofort, Alipay, Bitcoin and 3D Secure all yield a chargeable source usable with the existing Charges, Subscriptions and Connect surfaces. The approach drastically shrinks integration code and successfully scales global coverage.

AI-written summary · about

" chapters (8)

1. 0:00Intro
2. 1:12What is an API
3. 2:00Stripe Payment API 2010
4. 3:11Stripe Payment API 2014
5. 4:49Stripe Payment API Redesign
6. 5:32Authentication Flows
7. 6:14V1 Sources
8. 10:22Reverse API

" related talks

• 32mHow we build APIs and Team at StripeRomain Huet · apidays London 2019
• 23mFrom Fragile to Future-Proof: Solving Web Monetization Chaos...Faris Aziz · CityJS London 2025
• 21mAPI Design in FinTech: Challenges and Opportunities for next-gen APIs.Jeremy Glassenberg · apidays New York 2024
• 23mSearching for scale through API'sAki Ranin · apidays Singapore 2019
• 26mMastering API Platforms for Enhanced Payment IntegrationAdrita Bhor · apidays New York 2023
• 22mHow Spotify Payments Creates APIs to Manage ComplexityHoria Jurcut · Nordic APIs Platform Summit 2016
• 22mCommercialising APIs: A Product Owner's perspective.Yogesh Sholapurkar · apidays London 2019
• 23mScale up your business with API integrationMathieu Rasse · apidays Paris 2021