Stripe engineering blog

Stripe demonstrates how to build a whitelabeled connected-account dashboard with embedded payments, payouts, and notification components. The walkthrough covers account-session setup, role-based feature permissions, theming, localization, and React integration using Stripe Connect.

Stripe describes how it built an agentic factory for repeated payment-method integrations using more than 100 reusable prompts, observer agents, coded orchestration, and autonomous testing. The approach reduced integration timelines from up to six months to two-to-six weeks and cut one benchmark task from roughly 20 days to four.

Stripe explains how it integrated WebMCP into Checkout to give browser-based AI agents state-aware tools instead of requiring DOM interpretation. Progressive tool disclosure and shared form logic reduced token consumption by 42%, tool calls by 38%, and checkout time by 39% in tests across six models.

Stripe demonstrates how to replace SFTP-based financial reconciliation with flexible, event-driven reporting workflows using the Reports API v2 and Query Run API. The post provides SQL patterns for multi-account payout reconciliation, foreign exchange reporting, and itemized IC+ fee analysis.

Stripe explains how Harbor enables AI-assisted, browser-based prototyping with React and TypeScript. The post details in-browser compilation, agent-driven inspection, resilient comment anchoring across rewrites, and integrations through MCP and the reusable Drydock rendering engine.

Stripe explains how Scripts, Workflows, Custom Objects, and UI extensions let businesses customize logic, data models, and Dashboard experiences within Stripe. Using a vehicle-rental example, the post shows how these capabilities can replace surrounding orchestration infrastructure while coordinating business-specific operations.

Mike North explains how AI reshaped Stripe’s extensibility SDK workflow beyond code generation. The team used rapid prototypes, agent-drafted specifications, repository-local guidance, and faster feedback loops to evaluate architecture earlier and produce more consistent implementations.

Stripe explains why it replaced Envoy with mesh-proxy, a Go-based service-mesh data plane designed to reduce connection cardinality and improve reliability at massive scale. The post details its concurrency model, service discovery, routing features, and reported results of roughly half the CPU usage and a 50% latency reduction.

The post explains how AI-generated payment integrations can be technically correct while violating unstated business rules. It shows how to detect signals such as stuck PaymentIntents, unsafe retries, orphaned authorizations, and mishandled asynchronous payments, then encode those rules in metadata, verification agents, and CI checks.

Stripe explains how Connect platforms can move from blended pricing to IC++ network cost passthrough, including eligibility requirements, Dashboard and API setup, balance recovery behavior, and reporting options. It also outlines a pilot-based rollout strategy for connected accounts.

Stripe presents an architecture for letting autonomous agents shop on behalf of households without exposing reusable card credentials. Using ACP, hosted marketplace surfaces, deterministic household policies, bounded payment authority, SPTs, and idempotent order reconciliation, the smart-fridge example shows how to keep agentic purchases safe and auditable.

Stripe explains how it built Kai, a surface-agnostic knowledge AI platform for secure, multi-turn work across more than 1,000 internal tools and skills. The post covers its APIs, AgentStudio control plane, per-session sandboxes, context isolation, orchestration, and adoption results across the company.

Stripe describes an auto-remediation system that models MongoDB shard infrastructure as a state graph and uses BFS and Dijkstra search to generate safe recovery plans. An in-memory simulation layer shared with Temporal execution preserves fidelity while reducing pager volume by 30% and enabling support for new shard layouts without manual workflows.

Stripe explains how marketplaces can use Connect’s segregated separate charges and allocated balances to ring-fence seller funds from platform operations. The guide covers payment creation, per-payment balance inspection, transfers, fees, refunds, reversals, disputes, prerequisites, and regulatory considerations for PSD3.

Stripe introduces event notification handlers for thin events, reducing the boilerplate required to validate, route, and process webhook notifications. The post demonstrates a TypeScript implementation that provides compile-time event typing, automatic connected-account context handling, and more maintainable, testable business logic.

Stripe explains how it integrated stablecoin settlement into the Global Payments and Treasury Network rather than building a parallel system. The post details graph-based routing, liquidity pools, asynchronous fiat settlement, netting, urgent direct transfers, reconciliation, and the operational changes required for 24/7 blockchain payments.

Anna Spysz details how she used coding agents to build a production-style leaderboard app, including authentication, database design, serverless rate limiting, hosting, and multi-provider integration. She explains why the initial Supabase-based plan failed, how provider limits prompted a migration to Clerk and Upstash Redis, and what planning and verification practices improved the result.

Stripe explains how it uses OpenAPI, vendor extensions, API versioning, and automated pipelines to keep SDKs, the CLI, documentation, changelogs, and internal tools synchronized with API changes. The post details the architectural trade-offs of supporting v1 and v2 APIs and the validation and release workflows that reduce manual errors.

The post explains how to build a repeatable Apache Spark replay harness that executes production decision logic against historical, production-shaped inputs. It covers reconstructing dependency state, isolating deterministic code from side effects, comparing current and candidate implementations, and exposing replay limitations through debuggable outputs.

Stripe describes a replay-testing harness that runs deterministic microservice logic over production-shaped historical data with Apache Spark. The approach supports regression comparisons, what-if analysis for rule changes, privacy-aware golden datasets, and quantified behavior diffs before deployment.