How Sellers Connect Stripe
Every seller on your marketplace needs a Stripe account linked to yours so they can receive payouts. If you're new to how marketplace payments work under the hood, our Stripe for marketplaces guide covers the fundamentals. Prometora uses a deferred onboarding pattern, so sellers can start listing and earning before they verify with KYC. This page explains how that happens and what you, the marketplace owner, need to do.
The Short Version
Prerequisite: Your Webhook Must Be Configured
For sellers to be automatically linked after onboarding, your store's Stripe Connect webhook must be set up first. This is a one-time task done by you, the marketplace owner.
If the webhook isn't set up, seller status will not update automatically after they finish Stripe onboarding, and deferred payouts will not process.
See the webhook setup video & instructions in the Payments & Stripe docs.
Self-Serve Flow (Default)
This is how it works for sellers who sign up themselves and manage their own account.
The deferred-onboarding timeline
Seller signs up
No Stripe required. Creates a listing.
Lists & sells
Earnings tracked as pending. Buyer pays at checkout.
Verifies Stripe
Sees pending earnings, clicks Connect, fills out Stripe form (~5 min).
Auto payout
All accumulated earnings flow to their bank. No manual step.
The seller never sees a Stripe form before they have actual earnings waiting. That is the whole point.
Seller Signs Up & Starts Listing
A seller signs up on your marketplace and can immediately create listings and make sales. No Stripe setup is required up front — they don't have to configure anything before getting started.
Seller Clicks "Connect Stripe" in Their Dashboard
When ready, the seller goes to their seller dashboard (/s/<your-store>/dashboard) and clicks the Connect Stripe banner. Prometora creates a Stripe Connect account for them and opens an embedded onboarding form right inside your marketplace.
Seller Completes the Form Inline
An overlay opens directly on the marketplace dashboard with Stripe's embedded onboarding form. The flow is kept as short as the rules allow: Prometora prefills the seller's name, country, business website (your marketplace), and business category, and skips Stripe's separate sign-in step (the phone-code screen), so the seller only provides the essentials:
- Personal details (date of birth, home address, and a contact phone where required)
- Identity verification, if Stripe asks for it
- A bank account for payouts
There's no business-profile questionnaire and no separate Stripe sign-up — sellers go straight to who they are and where to send the money. The form is hosted by Stripe in an iframe inside your marketplace — the browser URL never leaves your store, and neither you nor Prometora ever sees their sensitive KYC data. The overlay closes itself when the seller finishes or cancels.
Automatic Linking (No Manual Step)
The moment they finish, Stripe sends an account.updated webhook to your Prometora store. The seller's status flips to Verified on their dashboard automatically. They can now receive payouts.
Deferred Earnings (Sales Before Onboarding)
Sellers can make sales before completing Stripe onboarding. Here's what happens:
- The customer pays normally — checkout isn't blocked.
- The seller's share of each sale is tracked in their Pending Earnings, visible on their dashboard.
- The money is safely held on the platform until the seller is ready to receive payouts.
- When the seller finishes Stripe onboarding, all pending earnings are automatically transferred to their Stripe account in a single payout.
- Nothing is lost. Nobody has to manually move money around.
Alternative: Managed Sellers
Some sellers aren't comfortable setting up Stripe themselves — for example, local artisans, small farmers, or non-technical vendors. For them, you can use the Managed Sellers feature, available on Pro & Business plans — see Prometora pricing for a full plan comparison.
With managed sellers, you create the account on their behalf and generate a Stripe Connect onboarding link you can share via email, SMS, or fill in together with them. Each seller still ends up with their own Stripe account — you just help them get there.
Learn more: Managed Sellers documentation
Supported Countries & France (PSD2)
Your sellers can connect from any country Stripe Connect supports. The onboarding flow adapts to each seller's country, collecting the identity and banking details Stripe requires for that region.
France is a special case. France's PSD2 / strong-customer-authentication rules require a seller's identity to be collected differently than the rest of the EU, and that mismatch used to block account creation for marketplaces based in France. That's now handled: for French platforms we mint a Stripe v2 account token and carry the seller's identity, contact, and Terms-of-Service attestation inside it, the way Stripe requires. Marketplaces outside France keep their existing flow unchanged.
What You (the Store Owner) Need to Do
For the self-serve flow, your involvement is minimal:
- Configure your Stripe Connect keys in Payments & Stripe (one-time setup).
- Configure the Stripe webhook pointing to your store — see the video walkthrough (also one-time).
- That's it. Sellers handle the rest themselves from their dashboard.
What This Setup Means for Your Risk Exposure
Prometora configures every new seller account so the seller has no Stripe-side dashboard. Everything they need (payout history, balance, account management, tax documents, KYC updates) lives inside your marketplace via embedded components. That is the white-label experience your sellers expect from a marketplace branded as yours.
The tradeoff is that Stripe treats you, the marketplace owner, as the operator of record for those connected accounts. There are three concrete things this means in practice:
Where the line sits
- KYC oversight — nudge sellers when Stripe needs more
- Chargeback & negative-balance liability
- Defending disputes from your Stripe dashboard
- Fraud detection (Stripe Radar)
- PCI compliance & card data security
- KYC document processing (never touches your servers)
- Tax forms (1099s & equivalents)
- Regulatory reporting
You own seller oversight and chargeback liability; Stripe keeps the regulated, security-critical pieces.
1. KYC oversight is on you
If Stripe needs additional verification from a seller (expiring ID, a new tax form, an updated business detail), the “Actions required” notification appears on your Stripe Dashboard, not the seller's.
You are expected to nudge the seller to resolve it via the embedded onboarding component in your marketplace. If you ignore it, that seller's payouts pause once Stripe's deadline passes.
2. Chargeback and negative-balance liability is on you
If a buyer disputes a charge and the seller cannot cover the chargeback (insufficient balance, funds already withdrawn, account closed), Stripe does not automatically debit the seller's external bank account first. The negative balance falls to the platform - that is, you.
This is the standard liability model for marketplaces operating connected accounts with no Stripe-side dashboard. It is the same risk profile Substack, Lyft, Instacart, and other Stripe Connect marketplaces operate under.
3. Disputes are defended from your dashboard
Sellers cannot defend their own disputes - they have no Stripe-side login.
When a chargeback comes in, you handle it from your Stripe Dashboard under Connect → Disputes. The seller can still provide you with evidence (proof of shipping, communication logs), but the submission to the card network is yours.
In practice, the day-to-day is light
Industry chargeback rates for marketplaces typically sit well under 1% of transactions, and your seller's connected Stripe account balance usually covers the few that occur - the platform only steps in when one of your sellers can't.
KYC re-verification happens years apart for verified sellers, not months.
Most marketplace owners on this model never absorb a chargeback loss. The bigger operational cost is the few minutes per week spent watching the “Actions required” panel.
What Stripe still handles on your behalf
This is not unrestricted exposure. Stripe still handles:
- Fraud detection (Stripe Radar)
- PCI compliance and card data security
- KYC document processing (the ID and verification details are processed by Stripe, never touch your servers)
- Tax form generation (1099s in the US, equivalents elsewhere)
- Regulatory reporting to financial authorities
Practical implications
- Watch the “Actions required” panel on your Stripe Dashboard home. That panel is your only proactive signal when a seller has a KYC item due.
- Vet new sellers before letting them transact at scale. You can hold back early payouts manually or require approval flows for high-volume sellers.
- Maintain a reserve in your platform Stripe account proportional to seller volume - enough to absorb realistic chargeback rates without affecting cash flow.
- Set expectations with sellers about KYC resolution time. Most items have a 14+ day grace period from Stripe before payouts pause.
About Emails to Sellers
With Prometora's default setup, your marketplace handles all routine seller communication directly:
- Payout-arrived emails come from your marketplace, not Stripe
- Payout-failed and onboarding-complete emails come from your marketplace, not Stripe
- Refund confirmations come from your marketplace, not Stripe
Compliance and tax-form emails (1099s, KYC document requests, regulatory notifications) still come directly from Stripe, because Stripe is the regulated entity required to send them. These cannot be disabled - they are a legal requirement.
What you can do: brand those Stripe-sent compliance emails so they look like they come from your marketplace.
- Go to your Stripe Dashboard → Settings → Connect → Emails.
- Under Related settings, click “Connect branding” to add your logo and brand colors.
- Under “Email domain”, add your custom domain so compliance emails appear to come from
noreply@<your-marketplace>.com.
If you're on Business or Scale tier, you can also customize the wording of your marketplace's payout, welcome, and refund emails (the ones Prometora sends) under Email Translations.
Troubleshooting
A seller's status isn't updating after they finished onboarding
- Check that your Stripe webhook is configured and showing Configured ✓ in Payments settings.
- In your Stripe dashboard, go to Developers → Webhooks → your Prometora destination → check the recent deliveries for failures.
- Make sure the webhook was created under “Events from: Connected and v2 accounts” — otherwise you won't receive
account.updatedevents.
The seller says they can't see the “Connect Stripe” button
- Confirm they're logged in as a seller (not a regular customer) on your marketplace.
- Confirm your Stripe Connect keys are saved in Payments settings — without them, the button cannot be created.
Pending earnings didn't pay out after onboarding
- The automatic payout is triggered by the same
account.updatedwebhook. Check webhook deliveries in Stripe for errors. - In rare cases, the seller's account may be onboarded but not yet payouts-enabled — Stripe may require additional verification. The payout will trigger once Stripe fully verifies them.
Frequently Asked Questions
No. Sellers can sign up, create listings, and make sales before connecting Stripe. Earnings are tracked as pending and paid out automatically the moment they complete Stripe onboarding.
This is called deferred onboarding and it dramatically reduces signup drop-off.
It is the same risk profile that Substack, Lyft, Instacart, and most other Stripe Connect marketplaces operate under. Industry chargeback rates for marketplaces are typically under 1% of transactions, and your seller's connected Stripe account balance covers most of those.
The marketplace operator only steps in when one of your sellers cannot cover their own chargeback. Most marketplace owners on this model never absorb a chargeback loss.
- Vet sellers before approving them on your marketplace
- Hold back early payouts for new sellers until they have a track record
- Require manual approval flows for high-volume sellers
- Maintain a reserve balance in your platform Stripe account proportional to seller volume
- Configure Stripe Radar fraud rules from your Stripe Dashboard
Prometora's seller management tools also let you suspend, approve, or limit sellers as needed.
Because marketplace owners want the white-label experience. When sellers have their own Stripe-hosted dashboard, they receive Stripe-branded emails, see Stripe-branded interfaces, and your white-label positioning fragments. Prometora's default keeps the entire seller experience inside your marketplace, branded as yours.
The tradeoff is that the marketplace operator (not Stripe) handles seller-related compliance oversight and chargeback liability. Most marketplace owners told us this tradeoff is the right one for their business.
The “Actions required” notification panel on your platform Stripe Dashboard home is the primary signal. When a seller has an outstanding KYC item (expiring ID, new tax form, etc.), it appears there.
Resolve it by directing the seller to update their info via the embedded Account Management component in their Prometora seller dashboard.
Yes. France's PSD2 / strong-customer-authentication rules require a seller's identity to be collected differently than in the rest of the EU, and that mismatch previously blocked the account-creation step for French platforms. That's now handled.
For French marketplaces, Prometora mints a Stripe v2 account token and carries the seller's identity, contact, and Terms-of-Service attestation inside it, the way Stripe requires. Marketplaces outside France keep their existing flow unchanged, and there's nothing extra to configure — the onboarding flow detects the case automatically.