Stripe Connect Growth Accelerates 106% YoY

Something wild is happening with Stripe Connect right now. We've added more platforms on Stripe in the last 3 months than we did in the last 6 months of 2025. New platform businesses on Stripe are up 106% year over year. And, fascinatingly, that growth rate is still accelerating. A few things stand out to me: 1. These are real businesses onboarding real users with real volume. We did a deep audit of our newest platforms (manual reviews, LLM classification, heuristic checks) and they're legit. Even better, our January 2026 cohort is hitting $1M in volume at a higher rate than any previous cohort. 2. AI is changing how developers build on Stripe, with 42% of new integrations involving some form of AI assistance. For Connect users, we're leaning into this trend heavily with better docs, blueprints, and agent-friendly tooling. We recently added a new connect-recommend skill to the official Stripe plugin for Claude, available to users who install or invoke the plugin. This skill provides agent-steering resources that help AI recommend the Connect integration for the use case. In Claude skill evals, the rewritten Connect guidance improved the pass rate from ~40% to ~90% across our six core Connect scenarios. 3. The macro tailwinds are real and, at the same time, we've also shipped a ton of improvements to onboarding and integration flows that are compounding. Users building “complete” integrations (a leading indicator for us) is up 200% YoY. For SaaS platforms thinking about embedded payments or financial services, the barrier to entry has never been lower. The platforms building now are scaling faster than we've ever seen. So excited for what’s happening with the segment and we want your feedback. If you're a platform founder or leader, would love to hear what's top of mind for you right now.

The six-scenario evaluation result is a useful example of where AI-assisted integration work compounds: not just faster code generation, but better guidance that measurably improves completion quality. The broader moat may be developer context embedded in docs, blueprints, and agent steering rather than the model itself.

This growth is encouraging to see, but I hope Stripe also improves how it reviews and supports legitimate new businesses. We are a startup virtual support company providing trained virtual assistants to healthcare practices. Our account was suddenly closed after a client experienced several unsuccessful payment attempts. Despite providing business documents, client contracts, invoices, and proof of legitimate services, we did not receive what felt like a complete manual review or a clear explanation. For a growing business, losing payment processing without warning can significantly disrupt operations, contractor payments, and client relationships. I would appreciate the opportunity for Stripe to properly review our account and reconsider the decision based on the actual nature of our business and transaction history.

We switched to Stripe last year for our subscription service and can't be happier. This year we partner with Flex to offer HSA/FSA payments to our customers to buy our hardware on our Shopify store and Flex also uses Stripe, it is a great customer experience.

The 40% to 90% eval jump is impressive. The failure mode I would watch in payments is an integration that is technically complete but encodes the wrong liability model. Platform versus merchant of record, charge type, negative-balance ownership, disputes, refunds, and regional onboarding rules can all change the architecture. The most valuable eval may be whether the agent asks the few business-model questions that alter the design before it recommends code. Are you measuring clarification quality as well as scenario completion? A fast, wrong Connect design is expensive to unwind.

Like
Reply

The 40%→90% pass-rate jump on the Connect skill is the more interesting number here than the platform growth stats. In my experience shipping Connect integrations, the failure mode with agent-assisted setups isn't wrong API calls, it's onboarding flows that pass functional tests but miss country-specific KYC/document requirements, which only surface once real users hit them. Worth watching whether that skill closes that gap too, not just the integration pattern.

Like
Reply

The AI-assisted integration number is the one I'd watch closest. In my own build, the place AI actually helped wasn't writing the integration code it was reasoning about edge cases in the eligibility/decision logic sitting in front of the payment layer. The API call is usually the easy part; the business rules wrapping it are where teams lose weeks. On "barrier to entry has never been lower" agreed for the integration itself, but for anything touching regulated money movement, the barrier just moves downstream to compliance and audit trail design. Be curious whether that's where you're seeing platforms stall out now.

Like
Reply

106% year-over-year growth in new platform businesses is the headline, but the detail that matters for hiring is the 42% of new integrations involving AI assistance. That's already the majority use case for anyone building on Connect right now. I'd be curious whether Stripe partner teams are seeing the same shift in the profile of engineers platforms are trying to hire: more agent-tooling literacy, less pure API integration experience.

Like
Reply

The 3x platform growth number says more about webhook and event volume than about Connect adoption itself. Every new platform onboarded through this skill means more account.updated and payout events hitting your system from day one, before anyone's built backpressure handling for that scale. We've seen platforms treat the Connect webhook stream as an afterthought until a signup burst turns a slow endpoint into a growing retry queue.

Like
Reply

The 42% figure is the one worth watching over time. Once a real share of integrations get written with an assistant in the loop, documentation quality stops being a support cost and starts acting like distribution, because a model can only recommend what it can read cleanly. Do the mistakes in AI-assisted integrations cluster differently from the hand-written ones, or is it the same short list of things people always get wrong?

Like
Reply

If 42% of new integrations already involve AI assistance, the build stops being the moat fairly quickly. What is left is the unglamorous part: getting the first hundred sellers or providers to actually move volume through you. That is a distribution problem, and it usually gets solved by explaining what the first cohort earns in month one rather than what the platform does.

Like
Reply
See more comments

To view or add a comment, sign in

Explore content categories