From months to days: Stripe's embedded components for platform payments

Stripe Connect now serves more than 13,000 platforms, which in turn process payments for over 8 million small businesses and solopreneurs. Embedded payments have become a significant revenue driver for many software platforms, but building that capability in-house means wrestling with payments regulation, compliance engineering, and ongoing maintenance—on top of delivering a polished user experience.

At Sessions last month, Stripe introduced 17 new embedded components built on Connect. These are copy-and-paste UI components that wrap Stripe's payments capabilities into ready-made workflows. Instead of a multi-month build for a full team, each component is meant to be integrated in days by a single engineer, with no ongoing maintenance burden. Four of those components address particularly complex workflows: onboarding, disputes, payment method configuration, and payouts.

Localized onboarding in 118 countries

Onboarding is the first user experience a connected account sees, and it is one of the most compliance-heavy pieces of a payments platform. Identity verification and regulatory requirements differ by jurisdiction, and those rules change.

Stripe's onboarding component runs inside your own site and dynamically adapts to 118 countries and 45 languages. It also applies local business logic—for example, recognizing and validating Hong Kong Identity Card number formats during onboarding. When country or compliance requirements change, the component updates automatically, so your engineering team doesn't have to chase regulatory shifts.

MYOB, a business management platform, used the component to expand payments to New Zealand. The company launched its full payments stack in a new market in eight weeks and reports that future market expansion now requires no additional work. "We were able to add embedded components into existing workflows and use onboarding to effectively plug and play where we had gaps in our platform experience," said Steve Price, MYOB's head of product.

Self-service dispute resolution

Disputes present platforms with an unpalatable choice: run a support team to handle disputes on behalf of connected accounts, or manage disputes centrally and absorb the revenue risk. Both approaches are slow and error-prone, especially given the wide range of reason codes a platform may encounter.

The payments list component offloads dispute handling to connected accounts themselves. It reads the reason code attached to a dispute and automatically surfaces the right resolution workflow, guiding the account through evidence submission and status tracking with prebuilt UI. Platforms no longer need to understand the full taxonomy of dispute reason codes or build resolution flows for each one.

Thinkific, a course platform, estimates a 70% reduction in dispute-handling time using the component. "They also provide control to our customers and allow us to operate as a lean team," said Aditya Srivathsan, Thinkific's director of payments.

Payment method toggles without the integration backlog

More payment methods generally mean higher conversion and lower transaction costs, but each one traditionally requires its own integration and ongoing maintenance. Platforms field requests from customers for specific methods and often spend months keeping up.

A new embedded component for local payment method settings changes that. Connected accounts can switch up to 18 payment methods on or off with a few clicks—cards, wallets, ACH, and buy-now-pay-later options included. As Stripe adds support for additional methods, the component updates on its own, so keeping pace with payment method demand is no longer a backlog item.

Payout visibility and instant access

Cash flow is existential for small businesses, and Instant Payouts gives connected accounts near-immediate access to funds. But platforms still need to build custom UI to surface balances, payout history, and schedules—not to mention implement the instant payout option itself.

The payouts component packages all of that into an embedded dashboard: a balance summary, a payout list, and schedule information in one view. The same UI can offer connected accounts instant access to funds for a small fee, which becomes a new revenue line for the platform.

Trevor Johnston, cofounder and co-CEO of Jane.app, noted that the underlying infrastructure is what makes the product possible. "Instant Payouts is one of those things the old model couldn't do because of the constraints of our financial system. Stripe's infrastructure of real-time money movement makes it possible."

Beyond payments

The embedded component strategy extends beyond core payments. Seven additional components are in preview, covering embedded financial services—cards, bank account alternatives, and lending—plus Stripe Tax and the broader Apps ecosystem. A demo implementation is available at Furever.dev, a fictional dog-grooming platform.