Stripe's product for platforms and marketplaces that move money between multiple parties. Handles payment splitting (buyer → seller, with platform taking a cut), seller verification (KYC), payouts, and tax reporting. Different from regular Stripe (which is for one business collecting payments). All multi-vendor marketplaces on Prometora use Stripe Connect.
See also: Complete Stripe for Marketplaces guide · Stripe Connect setup
Three flavors of Stripe Connect accounts in the v1 API. Standard: seller manages a full Stripe dashboard themselves. Express: simplified onboarding hosted by Stripe; most v1 marketplaces pick this. Custom: maximum control, requires a dedicated payments engineering team. In late 2025 Stripe shipped Accounts v2, which replaces these fixed types with flexible configurations. Prometora moved to v2 in May 2026 and provisions sellers with dashboard: "none" + embedded components - the modern equivalent of Express but with the entire seller experience inside the marketplace site, not on Stripe.
See also: Which account type to choose
The December 2025 rebuild of Stripe Connect that replaces the fixed Standard / Express / Custom account types with composable configurations: independent dashboard, configuration, and responsibilities settings you combine to get the exact behavior you want (see Stripe's connected account configuration docs). Prometora migrated to v2 in May 2026 and provisions every new seller with dashboard: "none" plus embedded components, so the seller's entire payment experience lives inside the marketplace rather than on Stripe.
See also: How sellers connect Stripe
Stripe's prebuilt UI blocks - onboarding, payouts, balances, transactions, account management, tax documents, and an action-required notification banner - that mount inline inside your own site through a Stripe-hosted iframe. The seller never leaves your marketplace and never sees a Stripe-branded page, while Stripe still handles all the sensitive KYC and compliance behind the iframe. These are what make Prometora's white-label seller experience possible.
See also: How sellers connect Stripe
The identity-verification process every seller must complete before receiving payouts. Stripe collects legal name, DOB, address, tax ID, and bank account from each seller. Required by financial regulations. Cannot be skipped (though it can be deferred until the seller has actual earnings waiting).
A pattern where sellers can list and sell on the marketplace BEFORE completing full Stripe verification. Earnings are tracked and held until the seller verifies, at which point accumulated funds are paid out automatically. Dramatically improves seller retention because verification happens when there's real money waiting, not at signup when the seller is still evaluating the platform.
Where the money sits. During the deferred window the funds are custodied by Stripe (a licensed payment / e-money institution), not by the marketplace in its own bank account. They rest in the platform's Stripe balance and are attributed to the seller in the marketplace's own records (the seller's pending-earnings balance), then released to the seller's connected account with a Stripe transfer once verification completes. The marketplace can only move these funds along Stripe's rails; it never gains free use of them.
Regulatory note (EU / EEA). Under PSD2, only parties that never come into possession or control of user funds are exempt from being regulated as a payment institution. Because the deferred window briefly holds and directs seller funds, EU/EEA operators should confirm their position with Stripe and local payments counsel before relying on it. The usual basis is that Stripe is the licensed fund-holder and the platform never takes funds into its own account, but the "control" question is jurisdiction-specific and is best cleared up front rather than assumed.
See also: How sellers connect Stripe · Deferred onboarding deep dive