Stripe Connect for Non-Residents

Stripe Connect is the piece of Stripe that turns your business from a single merchant into a platform. Instead of only charging your own customers for your own products, Connect lets your Wyoming LLC accept money from buyers and route it to other businesses — the sellers, contractors, hosts, or service providers operating on top of your platform. If you are a non-resident running a marketplace, an on-demand booking service, or a SaaS product that bills on behalf of its users, Connect is almost always the right Stripe surface to build on. This guide goes well beyond "yes, non-residents can use it" and walks through how the money actually moves, what each account type changes, where the tax and sales-tax obligations land, and the mistakes that quietly cost platforms real money.

What Connect actually does that plain Stripe does not

A standard Stripe account answers one question: how do I, the business, get paid by my customers. Connect answers a harder one: how do I, the platform, accept money from a buyer and split it between myself and a third party who is not me. That third party is called a connected account or sub-merchant. Your Wyoming LLC sits in the middle as the platform, and Stripe handles the orchestration of charging the buyer, taking your cut, and paying the seller.

The reason this matters legally and financially is that the money is not all yours. When a customer pays one hundred dollars on your marketplace, most of that hundred dollars belongs to the seller. Your business only earns the platform fee — the slice you keep for providing the marketplace, the audience, the software, and the payment rails. Connect exists to keep these two pots of money separate at the infrastructure level, so you are not commingling other people's funds with your own and then trying to untangle it at tax time.

For a non-resident-owned Wyoming LLC this distinction is the whole game. Your reported revenue, your books, your Form 5472 and pro forma 1120 (for a single-member disregarded entity) or your partnership return (for a multi-member LLC) should reflect only what your platform actually earns. Treating gross transaction volume as your income is one of the most common and most damaging mistakes new platform operators make, and Connect is specifically designed to help you avoid it.

The three account types, and what each one shifts

Connect offers three connected-account types: Standard, Express, and Custom. They are not three tiers of the same thing — they represent three different answers to the question of who owns the relationship with the seller, who handles compliance and identity verification, and who the seller thinks they are paying.

• Standard accounts are full Stripe accounts that the seller owns. The seller signs up, sees the normal Stripe Dashboard, and has a direct relationship with Stripe. Your platform connects to that account through OAuth and charges a fee on top. This is the lightest lift for you because Stripe handles onboarding, identity verification, and disputes with the seller directly. It is the natural fit for marketplaces of established businesses.
• Express accounts are Stripe-hosted but lighter. Stripe still runs the onboarding flow and verification, but the experience is co-branded with your platform and the seller gets a stripped-down Express Dashboard rather than the full one. You control more of the journey. This suits on-demand and gig-economy platforms where the seller is an individual driver, freelancer, or host who does not want a full Stripe account.
• Custom accounts are white-label. The seller may never know Stripe is involved. Your platform builds the entire onboarding, collects all the identity information, and takes on responsibility for compliance and disputes. This is the most work and the most control, and it is what powers products that feel like they have their own embedded payments.

The practical takeaway: the further you move from Standard toward Custom, the more compliance, support, and liability your Wyoming LLC absorbs, and the more engineering you sign up for. Most non-resident founders should start with Standard or Express and only reach for Custom when the product genuinely requires an invisible, fully branded money experience.

Choosing the right type for your model

The right account type follows from what kind of platform you are building and how much of the seller relationship you want to own. A quick reference:

A useful rule of thumb is to pick the lightest type that still delivers the experience you need. Every step toward Custom adds onboarding screens you have to build, verification edge cases you have to handle, and dispute responsibility you have to staff. If your sellers are real businesses who will happily click through Stripe's own onboarding, Standard saves you months. If they are individuals who would abandon at the sight of a full Stripe signup, Express is the sweet spot.

Note that some of the more advanced setups — embedded finance, issuing cards to your sellers, holding balances — layer additional Stripe products (Treasury, Issuing) on top of Connect and bring meaningfully more regulatory weight. Those are not entry points; they are destinations you grow into after the core marketplace works.

How money actually moves: the three charge patterns

The single hardest concept for first-time Connect builders is the flow of funds, because Stripe offers several patterns and they change who is the merchant of record, where the money lands first, and who carries the risk. There are three main patterns.

• Direct charges create the charge directly on the connected account. The seller is effectively the merchant of record for that card transaction, the funds land in the seller's balance, and your platform takes an application fee out of it. This keeps your platform further from the transaction and is common with Standard accounts where the seller already owns the relationship.
• Destination charges create the charge on your platform account. The funds touch your platform balance first, then Stripe transfers the seller's share to their connected account while you retain an application fee. Your platform is closer to the transaction and carries more of its risk, but you also have more control over the customer-facing branding and the refund flow.
• Separate charges and transfers give you the most control. You charge the customer on your platform, then independently move money to one or more connected accounts in whatever splits you decide. This is the pattern for marketplaces that split a single purchase across multiple sellers, or that need to delay or condition payouts.

In every one of these patterns, the part you keep — the application fee — is your LLC's revenue, and the pass-through portion belongs to the seller. The pattern you choose affects your processing-fee responsibility, your dispute liability, and how cleanly your books separate your income from money you are merely routing. Decide this deliberately and early, because changing charge patterns after launch is a real migration, not a config flip.

A worked example: a digital-goods marketplace

Make it concrete. Your Wyoming LLC runs a marketplace where independent creators sell fifty-dollar digital templates, and your platform takes a fifteen percent fee. A customer pays fifty dollars for one template using destination charges.

Stripe's processing fee comes off the top first. At roughly 2.9 percent plus thirty cents, that is about one dollar seventy-five on a fifty-dollar charge, leaving about forty-eight dollars twenty-five. Your platform's fifteen percent application fee on the fifty-dollar sale is seven dollars fifty, which Stripe records as your platform revenue. The remaining balance is transferred to the creator's connected account. Who bears the processing fee — platform or seller — depends on how you configure the application fee and which charge pattern you use, so model it explicitly rather than assuming.

For your books, the number that is your LLC's income is the seven dollars fifty, not the fifty dollars. Across a thousand such sales, your platform earned seven thousand five hundred dollars, even though fifty thousand dollars of gross volume flowed through. The creators are responsible for their own income tax on their share, and if a creator is themselves a non-resident, they are responsible for their own W-8 form on file with you or with Stripe. This split — your fee as your income, the rest as pass-through — is exactly what keeps your reported revenue accurate and your 5472 or partnership filing honest.

The bookkeeping discipline that keeps your taxes clean

The accounting principle underneath all of this is simple to state and easy to get wrong: only your platform fee is revenue; the seller's share is a liability you are holding and then paying out, not income you earned. If your books record the full fifty dollars as revenue and then the forty-two-fifty payout as an expense, your top line is wildly inflated, your margins look impossible, and any reviewer — a bank, an accountant, the IRS — will be confused at best.

Set up your chart of accounts so that platform fees flow into a revenue account and seller balances flow through a liability or pass-through account. Stripe's Connect reporting and the balance-transaction data tag application fees separately, which makes this reconciliation tractable if you wire it in from day one. Reconcile monthly. A platform that waits a year to sort out gross-versus-net has a genuinely painful cleanup ahead.

For a foreign-owned single-member Wyoming LLC, this matters because you file Form 5472 with a pro forma 1120 each year, reporting reportable transactions with the foreign owner, and the penalty for getting that filing wrong is twenty-five thousand dollars under the relevant code section. For a multi-member foreign-owned LLC taxed as a partnership, you file Form 1065 with K-1s, and effectively-connected income can trigger withholding obligations. In both cases, clean books that show only your real platform earnings are not optional polish — they are what makes those filings defensible.

Marketplace facilitator sales tax: a real obligation that lands on you

Here is the obligation that ambushes platform founders. Many US states have marketplace facilitator laws that make the platform — not the individual seller — responsible for collecting and remitting sales tax on facilitated sales, once the platform crosses that state's economic nexus threshold. The logic is that states would rather collect from one platform than chase thousands of small sellers. The consequence is that the duty to collect and remit can land on your Wyoming LLC even though the goods or services came from third-party sellers you do not control.

This is independent of the fact that Wyoming itself has no state income tax. Sales tax is about where your customers are, not where your LLC is formed. If buyers in a state where you have crossed the facilitator threshold purchase taxable goods through your platform, you may be the one who has to register, collect, file, and remit in that state. Thresholds and definitions are state-specific, they have changed repeatedly since the 2018 Wayfair decision opened the door to economic nexus, and whether a given category (physical goods, digital products, services) is even taxable varies by state.

Practical guidance: plan for this before launch, not after a state sends a notice. Tools such as Stripe Tax with marketplace support, or third-party engines, can automate the calculation and filing mechanics. But the legal responsibility to determine where you have nexus and what is taxable is yours to confirm with a US tax professional. Do not assume your sellers are handling it — under facilitator law, in many states, they are explicitly not the responsible party. You are.

Onboarding, verification, and why payouts get held

Every connected account must pass Stripe's identity verification before it can receive payouts, and this is where new platforms hit friction. Each seller — whether on Standard, Express, or Custom — has to provide the information Stripe needs to satisfy know-your-customer and anti-money-laundering rules: legal name, business details, identity documents, and a bank account or supported payout method. Until that is complete and approved, funds intended for that seller can be held.

For non-resident sellers on your platform, this is more involved than for US-based ones. A seller in another country has to be in a country Stripe supports for Connect payouts, provide the right documents, and often supply tax information. Some countries are not supported. Approval is Stripe's decision, made against the seller's country profile and documents, and it is not guaranteed. You should set expectations with your sellers up front and surface clear onboarding states in your product so a seller who is not yet verified understands why their money is pending rather than blaming your platform.

Build for the verification lifecycle explicitly. Listen to Stripe's account webhooks so your platform knows when a connected account becomes able to accept charges and able to receive payouts — these are two separate capabilities and can be enabled at different times. Surface required-action prompts to sellers when Stripe asks for more information. A platform that treats onboarding as a one-time event rather than an ongoing state machine will repeatedly confuse sellers and strand payouts.

Refunds, disputes, and where the liability sits

When a buyer disputes a charge or you issue a refund, the question of who actually loses the money depends on the charge pattern. With direct charges, the connected account is closer to the merchant-of-record position, and disputes are generally that account's responsibility, though your application fee can be clawed back. With destination charges and separate charges and transfers, your platform is closer to the transaction, and you may bear more of the chargeback exposure and any associated fees.

This is not a detail to discover during your first big dispute. Decide deliberately how refunds and disputes flow, write it into your seller agreement, and configure Stripe to match. A common arrangement is that when a buyer is refunded, the seller's share is reversed from their connected balance and your application fee is returned too, so neither party profits from a reversed sale. If a seller has already withdrawn their balance and then a chargeback hits, your platform can end up covering the gap — which is exactly why payout timing and reserves matter.

Consider holding a short payout delay or a rolling reserve on connected accounts for higher-risk categories. It is unpopular with sellers who want their money instantly, but it protects your platform from the scenario where a seller is paid, the buyer charges back, and the seller's balance is empty. The right reserve policy is a business decision about risk tolerance; the mechanism to implement it is built into Connect.

Tax forms flowing through the platform

Two tax-reporting threads run through a Connect platform, and you should not confuse them. The first is your own platform's tax position: your Wyoming LLC earns platform fees, files Form 5472 with a pro forma 1120 if it is a foreign-owned single-member disregarded entity (due April 15, extendable with Form 7004), or Form 1065 with K-1s if it is a foreign-owned multi-member partnership (due March 15). Whether any of your platform-fee income is even taxable in the US turns on whether it is effectively connected to a US trade or business — a question to settle with a CPA, not assume.

The second thread is the sellers' reporting. Sellers handle their own income tax on their own share, and non-resident sellers are responsible for their own W-8 forms, such as the W-8BEN-E for foreign entities. On the information-return side, the 1099-K threshold for the 2025 rules is more than twenty thousand dollars and more than two hundred transactions — the earlier six-hundred-dollar proposal was repealed, so do not design your reporting around six hundred dollars. Stripe can generate 1099-Ks for eligible connected accounts; understand whether that responsibility is configured to your platform or to Stripe for your account type.

Keep these threads separate in your mind and in your documentation. Your platform is not your sellers' tax authority, and your sellers' filings are not your platform's revenue. Where the lines genuinely blur — facilitator sales tax, withholding on effectively-connected income, whether a given seller's payout creates a reporting obligation for you — get a US tax professional to draw them for your specific setup. The cost of one consultation is trivial against a twenty-five-thousand-dollar 5472 penalty or a multi-state sales-tax cleanup.

Common mistakes and edge cases

A short field guide to the errors that cost the most:

• Booking gross volume as revenue. The single most damaging mistake. Only your application fee is income. Fix your chart of accounts before you scale.
• Ignoring marketplace facilitator law until a state notice arrives. Map your nexus and taxability up front; the obligation can be yours even though the goods are your sellers'.
• Treating onboarding as one-and-done. Verification is an ongoing state. Wire up webhooks for charge and payout capabilities and surface required-action prompts, or you will strand payouts and lose sellers.
• Picking the wrong charge pattern and migrating later. Direct versus destination versus separate charges changes liability and tax footprint. Decide deliberately before launch.
• No reserve policy for risky categories. A seller paid out before a chargeback can leave your platform holding the loss.
• Assuming any seller's country is supported. Connect payout support is country-specific and Stripe's decision; check the current supported-country list before promising a seller they can join.

Edge cases worth flagging: a single buyer purchase split across several sellers needs separate charges and transfers, not a single direct charge. A seller who changes their tax residency mid-year changes which W-8 or W-9 applies. And a platform that grows into holding balances or issuing cards crosses into Treasury and Issuing territory, which brings added regulatory obligations you should not stumble into unprepared.

Stripe Connect is genuinely accessible to a non-resident-owned Wyoming LLC, but it rewards founders who treat the money flow, the bookkeeping split, and the sales-tax question as first-class design decisions rather than afterthoughts. The platforms that get into trouble are not the ones that picked the wrong account type — they are the ones that confused pass-through funds with revenue and discovered facilitator obligations a year too late.

To run a Connect platform you first need the legal entity underneath it: a US LLC with an EIN and a US business bank account, plus a W-8BEN-E on file with Stripe. A Wyoming LLC is a clean foundation for exactly this — no state income tax, strong asset protection, and no requirement to visit the US. You can form one fully remotely for $397 all-inclusive, with the LLC typically formed in about 24 hours and the EIN obtainable without an SSN, giving you the entity your Connect platform stands on.