Stripe Express vs Standard

Stripe Connect is the product you reach for when your business does not just charge customers for its own services, but instead moves money to other people. A marketplace pays its sellers. A booking platform pays the venues. A freelance site pays the freelancers. A SaaS tool routes a customer's payment to the merchant who owns that customer. In every one of these cases, your Wyoming LLC sits in the middle as the platform, and the parties you pay out to are "connected accounts" — what Stripe calls sub-merchants. Connect is the layer that makes that legal, auditable, and operationally sane.

The first real decision you make in Connect is the account type. Standard, Express, and Custom (now largely folded into Stripe's newer onboarding model) describe how much of the sub-merchant relationship Stripe owns versus how much you own. This page focuses on the two most common choices for a non-resident-owned platform LLC: Standard and Express. The choice is not cosmetic. It changes who holds compliance liability, who handles disputes, who carries negative-balance risk, which countries your sub-merchants can live in, and how much of the user experience you control. Picking wrong is expensive to undo, so it is worth understanding the mechanics before you write a line of integration code.

What "connected account" actually means

A connected account is a Stripe account that belongs to one of your sub-merchants but is linked to your platform account. When a customer pays on your platform, the charge can be created directly on the connected account or on your platform account and then transferred. Either way, the money ultimately settles to the sub-merchant, and your platform takes its cut as an "application fee." This is the core of the model: your LLC is not the merchant of record for the sub-merchant's sales — the sub-merchant is, or close to it, depending on the configuration.

The account type controls the boundary of responsibility around that connected account. With Standard, the connected account is almost a fully independent Stripe customer who happens to be reachable through your platform. With Express, Stripe hosts a stripped-down experience and pushes more of the operational and compliance weight onto your platform. That single difference cascades into everything else: onboarding screens, dashboards, dispute handling, tax forms, payout timing, and how much support email you personally answer.

It helps to think in terms of "who is the merchant." If your sub-merchants are real businesses that should own their customer relationships, you want them to be the merchant — Standard. If your sub-merchants are individuals you are effectively activating through your platform (a gig worker, a creator, a freelancer), you are functionally the merchant and they are payees — Express centralizes that reality.

Standard in depth: independent merchants on your rails

With Standard, each sub-merchant gets a full Stripe account. They log in to the real Stripe Dashboard. They see their own balance, payouts, customers, disputes, and reporting. They agree directly to Stripe's Services Agreement during onboarding, which means a meaningful chunk of compliance liability — know-your-customer (KYC), tax identity, dispute defense — lives with them, not with you.

Onboarding works through OAuth. You send the sub-merchant to a Stripe-hosted flow, they either connect an existing Stripe account or create a new one, and they come back to your platform with an authorized connection. From your side this is light to build: you are not collecting identity documents, you are not designing onboarding forms, and you are not responsible for verifying that a seller is who they claim to be. Stripe does that. Your platform's main job is to take its application fee and route the right money to the right account.

This model shines for marketplaces with established business sellers — the Etsy or Shopify-app pattern — and for B2B SaaS where each customer organization needs its own payment routing and wants its own dashboard for refunds and customer service. The trade-off is that the experience is "Stripe-branded." Your sub-merchant knows they are using Stripe, manages their money in Stripe's interface, and can in principle take that account elsewhere. If you want a seamless, white-labeled, you-never-see-Stripe experience, Standard is not it.

Express in depth: a hosted middle ground you mostly control

Express is designed for platforms whose sub-merchants are individuals or small operators who do not want — and should not have — a full Stripe account to manage. Stripe still hosts the sensitive parts: a lightweight onboarding form (Stripe handles the KYC questions and identity verification), and a simplified "Express Dashboard" where the payee can see their payouts and update their bank details. But your platform owns much more of the surrounding experience and much more of the responsibility.

The onboarding flow is shorter and friendlier. A freelancer enters their basic details and bank account, Stripe runs verification behind the scenes, and they are ready to receive payouts in minutes rather than completing a full merchant signup. You decide payout timing (instant, daily, weekly, or manual). You control the application fee. You can keep your branding front and center, because the payee spends most of their time inside your product, not inside Stripe.

The cost of that control is liability. With Express, your platform absorbs more of the support burden, more of the negative-balance risk (if a payee's account goes negative from refunds or disputes, the platform is often on the hook), and — for US payees — more of the tax-reporting responsibility. Express fits on-demand and gig-style platforms: rideshare, delivery, freelance marketplaces, creator payouts, tutoring, home services. The mental model is "these are my workers/creators, and I am paying them," not "these are independent shops renting space in my mall."

Side-by-side comparison

The table below summarizes the practical differences. Treat it as a decision aid, not gospel — Stripe periodically adjusts what each type supports, so confirm the current capabilities in your Stripe Dashboard before committing.

Read the table top to bottom and a pattern emerges: every row where Standard says "the sub-merchant," Express says "the platform." Choosing Express is choosing to take on responsibility in exchange for control and a cleaner experience. Choosing Standard is choosing to offload responsibility in exchange for a more Stripe-branded relationship.

Who carries liability, disputes, and negative balances

The onboarding screens are what people compare first, but they are the least important difference. The decision that actually matters is who carries risk when something goes wrong, because that is what determines your real operating cost and your real exposure as the platform owner.

Under Standard, the connected account is closer to its own merchant. A chargeback lands on the sub-merchant, who defends it from their own dashboard. A refund comes out of the sub-merchant's balance. If their balance goes negative, Stripe's relationship is primarily with them. Your platform's exposure is comparatively low — you facilitated the payment and took a fee, but you did not become the merchant of record for that sale.

Under Express, the platform takes on more of everything. You are more involved in dispute handling, you carry more of the negative-balance risk, and you own more of the support relationship because the payee cannot self-serve as fully. If a gig worker receives a payout, then the underlying charge is reversed by a dispute, and their balance cannot cover it, the platform frequently eats the shortfall. This is not a flaw in Express — it is the deliberate design. Express assumes you are the responsible party and the payee is a recipient, so the system places risk where the control is. Budget for this: a meaningful Express platform should hold reserves and design payout timing (for example, delaying payouts or using a rolling reserve) to protect against negative balances.

Tax reporting: 1099-K, W-8 forms, and the platform-vs-payee split

For US-based sub-merchants, running payouts can trigger information-reporting obligations, and Stripe can generate the relevant forms. The most common is the 1099-K, which reports payment-card and third-party-network volume. With Express, the platform is typically the party arranging that reporting; with Standard, the connected account owns more of it. Stripe also supports 1099-MISC/NEC for certain non-card payments, again more commonly platform-arranged under Express.

The 1099-K threshold matters and is widely misquoted. For 2025 and 2026, a 1099-K is issued when payments to a payee exceed more than $20,000 and more than 200 transactions in the year. Both conditions must be met. The much-discussed $600 threshold that was once scheduled to take effect was repealed by the One Big Beautiful Bill Act in 2025, so do not design your reporting around $600 or any $5,000 phase-in figure — use the more-than-$20,000-and-more-than-200-transactions rule and verify it against the IRS "Understanding Your Form 1099-K" page each tax year.

For non-resident sub-merchants, the picture shifts away from 1099s and toward W-8 forms. An individual foreign payee provides a W-8BEN; a foreign entity provides a W-8BEN-E. These certify foreign status and, where a tax treaty in force applies, can reduce withholding on US-source income. If there is no treaty in force, the default 30% rate applies and the treaty-claim section of the W-8 stays blank — never invent a treaty or a rate. Stripe can collect these forms during Connect onboarding. Because the exact platform-vs-payee reporting split depends on your specific Connect configuration (direct charges versus destination charges, who is the merchant of record, where the funds flow), confirm the details with a US tax professional before you launch. Getting this wrong is not a cosmetic error; the platform can end up holding reporting obligations it did not anticipate.

Country support and non-resident realities

A frequent surprise: Express supports fewer countries for connected accounts than Standard does. If your payees are concentrated in well-supported countries, Express is fine. If you are building a global freelance marketplace where designers, developers, and writers could be in dozens of countries — including ones Express does not support — Standard typically gives you broader reach, because each sub-merchant brings their own Stripe account from a country Stripe supports for full accounts.

Note the distinction between two separate questions. The first is whether your platform LLC can use Connect at all — and yes, a non-resident-owned Wyoming LLC works as the platform for either Standard or Express, the same way a non-resident-owned LLC can run an ordinary Stripe account once it has an LLC, EIN, a US business bank account, and a W-8BEN-E on file. The second question is which countries your sub-merchants can live in. Those are governed by Stripe's connected-account country support, which differs by account type and changes over time.

Because that list moves, do not hard-code assumptions about payee countries. Check Stripe's current supported-country documentation for connected accounts before you promise onboarding to a given region, and tell your prospective sub-merchants to confirm their own country is supported. If a large share of your payees fall outside Express's supported set, that alone can be the deciding factor in favor of Standard, regardless of which onboarding experience you would have preferred.

Fees and what actually drives cost

People ask "which is cheaper?" expecting a clean answer, but the honest one is that core Stripe processing fees — the per-transaction percentage plus fixed fee on the customer's payment — are broadly similar between the two models. The differences are at the margins. Express can carry slightly higher Stripe-side account or payout fees because Stripe hosts more infrastructure on your behalf (the hosted dashboard, the managed onboarding, instant-payout options). Standard pushes more of that onto the connected account's own Stripe relationship.

Your platform sets its own application fee per transaction in both models — that is your revenue, and it is independent of the account type. So the real cost question is not "which type has a lower headline rate," it is "what is my total cost of ownership including engineering time, support load, dispute losses, and reserve requirements." Express trades higher Stripe-side fees and higher risk-bearing for less engineering and a smoother payee experience. Standard trades a more Stripe-branded experience and broader country reach for lower platform risk.

Model it with your own numbers before deciding. Estimate monthly payout volume, average transaction size, expected dispute rate, and how many payees you will onboard. A high-volume gig platform with thin per-payout margins feels fee differences sharply; a low-volume marketplace of established sellers barely notices them and should optimize for reach and reduced liability instead.

Worked example: a freelance design platform

Suppose your Wyoming LLC runs a platform that connects clients with freelance designers around the world. The designers are individuals, not registered businesses. You want one consistent payout experience, the ability to set payout timing, and the option to handle support and any required tax forms centrally. This is the textbook Express case. Stripe hosts a light onboarding for each designer, you control the dashboard and payout schedule, you can keep your own branding throughout, and you are positioned to manage US tax reporting for any US-based designers while collecting W-8BEN forms from the non-US ones.

Now change one assumption. Suppose your "sub-merchants" are not individual freelancers but incorporated design agencies that want their own full Stripe dashboards, want to manage their own refunds and dispute defense, and operate from a wide range of countries. The same platform would now be a far better fit for Standard. The agencies are real businesses that should own their customer relationships and their compliance; Standard lets them do that while you take a clean application fee, and its broader country support means you do not turn away an agency just because Express does not reach their country yet.

The lesson is that the right answer depends on what your sub-merchants are, not on which onboarding screen looks nicer in a demo. Name your sub-merchant type honestly — individual payees or independent businesses — and the account type usually picks itself.

Common mistakes and edge cases

The most expensive mistake is choosing the model casually and discovering the mismatch in production. Switching between Standard and Express is generally possible, but it requires a migration coordinated with Stripe and re-onboarding your connected accounts — re-collecting consent, re-running verification, and reconnecting payout details. That is real work and real friction for your users, so decide up front rather than "starting simple and changing later."

A second common error is underestimating risk under Express. Teams launch a gig platform, set instant payouts to delight their workers, and then get hit by a wave of disputes that leave payee balances negative — with the platform absorbing the loss. The fix is boring but essential: hold reserves, consider delayed or rolling payouts, and watch your dispute rate. A third mistake is botching tax reporting — assuming the connected account handles 1099s when your Express configuration actually put that obligation on the platform, or quoting the dead $600 1099-K threshold instead of the current more-than-$20,000-and-more-than-200-transactions rule.

Edge cases worth flagging: mixed payee populations (some individuals, some businesses) sometimes justify running both models, which adds engineering complexity; payees in Express-unsupported countries simply cannot be onboarded that way, so a single important market can force the choice; and any non-resident payee who claims reduced withholding needs a treaty actually in force, otherwise the default 30% applies and the treaty section of their W-8 stays blank. Throughout, "confirm with a CPA" is not a cop-out — the platform-vs-payee compliance split genuinely depends on your exact Connect setup, and a short consultation is far cheaper than a mistaken assumption at scale.

Whichever Connect model fits your platform, the prerequisite is a clean US foundation: a Wyoming LLC, an EIN, and a US business bank account, with a W-8BEN-E on file. If you have not formed your platform entity yet, you can set up a Wyoming LLC for $397, all-inclusive — registered agent, filing, and EIN guidance included — without visiting the US, so you can get your Stripe Connect platform live and start onboarding sub-merchants.