You have 2 seconds to respond - Atob
summary
Authorization endpoint must answer Visa within two seconds so drivers don’t get stranded, and that constraint drives design choices: a fuel‑card and payroll product used by over 25,000 fleets with ~20–25% month‑over‑month growth and $100M+ raised, parallel checks via threads with strict timeouts, async work offloaded to Sidekick, feature flags with flipper, and production TracePoint tracing plus shadow mode to compare control and variant outputs before rolling changes.
AI-written summary · about
chapters (15)
- 0:00Introduction
- 1:46Atob products overview
- 4:13Two-second transaction limit
- 6:19System constraints variability
- 9:50APIs two-second constraint
- 12:16Safe design under constraints
- 13:21Single responsibility in code
- 14:22Necessary work immediately
- 15:47Concurrency in endpoints
- 18:34Parallel checks in authorizer
- 20:40Observability for critical parts
- 23:06Shadow mode deployment
- 25:34Shadow mode tools
- 26:15Shadow mode code walkthrough
- 31:10Closing and hiring
related talks
23mTrust, But Verify: Human-in-the-Loop for Agents That Actually Matter
24mSeamless and Secure: The Rise of Payment Passkeys
24mSeamless and Secure: The rise of payment passkeys
13mTrust, But Verify: Human-in-the-Loop for Agents That Actually Matter
51mThe Future of ATO
01h 22mIdentity for AI Agents
15mKeynote: The Operating System of Payments, UX and Security in Modern Apps
18mSecure your Apps and APIs with strong authentication and Adaptive Access.