Stripe Connect powers marketplace payments by enabling platforms to manage transactions between buyers and sellers. With the Accounts v2 API, a connected account is built from configurable roles, Merchant, Customer, and Recipient, instead of the older fixed account types. Core features include global payouts in 50+ countries, support for 135+ currencies and 40+ payment methods, automated tax handling, and gross earnings tracking with 1099s for US sellers, as detailed in Stripe Connect documentation. Transaction fees stand at 2.9% + 30¢ per successful charge, plus a 0.25% payout fee capped at $25 (2025 figures used as proxy for 2026, with regional variations).
For marketplace owners and developers building on greenmoov.app, Stripe Connect simplifies seller payments while handling compliance. This guide covers account configurations, onboarding workflows, features, pricing, and selection advice to implement without regulatory hurdles.
Stripe Connect Account Configurations: Merchant, Customer, and Recipient
With the Accounts v2 API, Stripe replaced the older Standard, Express, and Custom account types with a single, unified Account object. Instead of picking one fixed type at setup, a platform assigns one or more configurations to an account depending on what that account needs to do:
- Merchant configuration: lets the account accept payments. It includes the
card_paymentscapability and thestripe_balance.payoutscapability (the v2 name for the old v1payoutscapability). - Customer configuration: lets the account act as a paying customer of the platform. This replaces the separate Customer object from the v1 API, so a subscription or charge can reference the same Account instead of a linked Customer record.
- Recipient configuration: lets the account receive transfers. It includes the
stripe_balance.stripe_transferscapability (the v2 name for the old v1transferscapability), needed for indirect charges.
A single Account object can hold several of these configurations at once. For example, a seller on a marketplace might have the Merchant configuration to get paid, while a buyer making purchases on the same platform might be represented by an Account with the Customer configuration, all without maintaining a separate map between Account IDs and Customer IDs.
Dashboard access is set independently of these roles through the dashboard parameter, with values full, express, or none. This means the old distinction "Standard gets the full Dashboard, Express gets the lighter one" is now a separate setting rather than something baked into an account type. A platform can give a Merchant-configured account a full Dashboard for self-managed sellers, or an express Dashboard for a lighter, platform-led setup, depending on how much control it wants to hand to the seller.
Setup starts with the /v2/core/accounts endpoint, where the platform specifies configuration, identity, and defaults.responsibilities (such as who collects fees and who absorbs losses) instead of a fixed account type.
Onboarding Sellers with Stripe Connect: Traditional vs. Deferred Flows
Onboarding sellers traditionally takes 10-15 minutes via compliance forms before they can sell, according to Prometora (2026). Stripe Connect reduces this through API-driven flows.
Use the Account Links API to create temporary, single-use URLs for onboarding. Prefill personal, business, or external account details to streamline the process, as described in Stripe docs. In the v2 model, how much friction a seller faces during onboarding depends on the dashboard setting and which configuration requirements still need to be collected, not on a fixed "Standard vs Express" label. A platform that sets dashboard: express and collects banking and identity details itself can still offer a fast, platform-led signup, the same outcome the old Express type was used for.
Accounts with dashboard: full let sellers manage their own KYC information directly, similar to what the old Standard accounts offered. Accounts with dashboard: express or dashboard: none rely on the platform to collect banking and ID details from sellers and pass them through the API.
Deferred onboarding lets unverified sellers start immediately: platforms create charges and hold funds. Once verified, shift to destination charges with transfer_data.destination pointing to the seller's Recipient-configured account. Prometora (2026) and Stripe docs detail these verified and unverified paths, minimizing friction on platforms like greenmoov.app.
Key Features and Global Capabilities for Marketplaces
Stripe Connect supports end-to-end marketplace operations with a broad set of tools. Platforms track gross earnings, automate US 1099s, and manage sales tax, VAT, or GST, per the Stripe Connect page and Stripe docs.
Global reach includes payouts in 50+ countries, 135+ currencies, and 40+ payment methods. Onboarding uses embedded components, while the Accounts v2 API handles account creation and configuration in a single object.
These features let marketplaces route funds correctly, support diverse buyers, and stay compliant across regions without building everything from scratch.
Stripe Connect Pricing and Payout Fees
Stripe Connect pricing includes a 2.9% + 30¢ fee per successful transaction, covering standard card processing (Jeecart 2025). Payouts add 0.25% per connected account, capped at $25, based on Jeecart (2025) as a proxy for 2026, no confirmed changes noted. Fees vary by region, payment method, and volume.
Marketplaces budget these for seller transfers, with platforms often adding their commission on top. A transparent fee breakdown helps with greenmoov.app-style implementations.
Comparison Table: Which Stripe Connect Configuration Fits Your Marketplace?
| Configuration | What It Enables | Typical Dashboard Setting | Best For | Who Manages It |
|---|---|---|---|---|
| Merchant | Accepts payments (card_payments, payouts) | full for self-managed sellers, express for platform-led setup |
Any seller accepting payments, from store builders to rental and ride-hailing platforms | Seller self-managed (full) or platform-managed (express/none) |
| Customer | Acts as a paying customer of the platform | Not applicable | Subscriptions or charges where the same Account also pays the platform | Platform, via the same Account object |
| Recipient | Receives transfers, supports indirect charges | Not applicable | Payouts to drivers, hosts, or contractors after verification | Platform, via transfer_data.destination |
Choose dashboard: full with the Merchant configuration for seller autonomy and direct account management. Use dashboard: express on greenmoov.app when prioritizing speed and platform oversight. Combine Merchant with Recipient for marketplaces that both charge buyers and pay out sellers. Factors to weigh: onboarding speed versus seller control, and self-managed versus platform-managed KYC.
FAQ
What are the main differences between Merchant, Customer, and Recipient configurations in Stripe Connect?
Merchant lets an account accept payments through capabilities like card_payments and payouts. Customer lets an account act as a paying customer of the platform, replacing the separate v1 Customer object. Recipient lets an account receive transfers, which is needed for indirect charges. A single Account can combine more than one configuration, and Dashboard access (full, express, or none) is set separately from these roles (Stripe docs).
How long does seller onboarding take with Stripe Connect?
Traditional flows take 10-15 minutes; using Account Links and a leaner Dashboard setting (express or none) reduces this time, since the platform handles more of the data collection itself (Prometora 2026, Stripe docs).
What are Stripe Connect's transaction and payout fees for marketplaces?
2.9% + 30¢ per transaction; 0.25% payout fee capped at $25 (Jeecart 2025 proxy, regional variations).
Can marketplaces use deferred onboarding to let unverified sellers start immediately?
Yes, hold funds on unverified charges, then use destination charges with transfer_data.destination pointing to the seller's Recipient-configured account once verification is complete (Prometora 2026, Stripe docs).
Which Stripe Connect configuration is best for a ride-hailing or rental marketplace?
The Merchant configuration paired with dashboard: express, since it lets the platform collect driver or host details directly and manage payouts without handing sellers full Dashboard access (Stripe docs).
What global features does Stripe Connect offer for payouts and payments?
Payouts in 50+ countries, 135+ currencies, 40+ methods, plus tax and 1099 automation (Stripe Connect page/docs).
To implement on greenmoov.app, review the Accounts v2 docs for your region and test Account Links in sandbox mode.