How Spotify Payments Creates APIs to Manage Complexity
summary
Spotify runs 16 payment providers across 60+ markets and builds two internal APIs: a checkout API that makes clients stateless and drives a backend state machine for arbitrarily ordered checkout steps, and a billing API that normalizes provider APIs into a single "can I charge X" call while producing consistent events. The system deploys 3D Secure without client releases, handles multi-day bank transfers, and uses anomaly detection comparing 15min/1 week/1 month windows to surface provider failures.
AI-written summary · about
chapters (13)
- 0:00Start
- 1:37How Spotify Payments Has Evolved over Time
- 3:21What Are Payments
- 6:14Checkout Api
- 9:06Checkout Api
- 9:35Purchase Flow
- 10:08Anatomy of a Step
- 12:30The Billing Api
- 13:26Billing Api
- 14:29Spotify Automatic Alerts
- 14:50Anomaly Detection
- 16:14What Are the Advantages of Having Such Monitoring to Your Aps
- 18:00Spotify Why Api Design Is So Important
related talks
26mMastering API Platforms for Enhanced Payment Integration
17mUnveiling the Future of In-App Payments in Europe: The Evolution of app Stores
15mRe-designing an API to reach global scale
29mMoney Makes Your App Go Round
37mWeb Payment APIs
42mThe recurring nightmare. Implementing cross platform in-app subscription purchases
23mSearching for scale through API's
44mTaking your users’ money: In-app billing from start to best practices