--- title: "Stripe Connect" description: "Review Stripe Connect configuration categories without exposing payment credentials or starting external setup." canonical: https://docs.ordering.co/docs/products/dashboard/addons/stripe-connect/ --- # Stripe Connect The fixed Dashboard mounts `/stripe-connect` for level 0 only when `addon_stripe_connect` is true or configuration is still loading. Its My addons item has separate level-0, non-read-only, availability, and add-on gates. > **Payment-provider configuration** > > This surface sits next to payment-routing and store-commission configuration. It can expose provider-sensitive values and persistent configuration writes; no page, category, connection, credential, payment, or provider action was opened for this guide. ## Review available categories The page requests categories whose key is `addon_stripe_connect`, then renders the returned records through the generic settings UI. A selection writes `?category={id}` to client history; IDs, fields, descriptions, and values are runtime data, not fixed-source inventory. ![Stripe Connect page showing its add-on category without account or credential details](https://docs.ordering.co/img/docs/dashboard/addons/stripe-connect-categories.jpg) The page does not establish a generic set of OAuth or credential fields. Review the specific, approved test-project configuration before documenting or changing it. ## Source-verified request and write boundary The category request and subsequent config reads are authenticated. Category records are administrator-only in the inspected API source. Generic settings edits are buffered in the client until **Save**, then submitted one config at a time; partial completion is possible if a later update fails. Accepted updates can create audit-log records, refresh global config state, and run plugin hooks. Those contracts do not prove the returned Stripe category, a connected account, OAuth availability, commission behavior, or deployed payment routing. The separate store payment-method flow contains provider connection and credential persistence behavior; it is not copied into this category guide. ## Keep sensitive data out of captures Do not capture or disclose provider credentials, connected-account identifiers, webhook destinations, payment data, or live settings values. The retained image is an existing sanitized category-list capture; it was not replaced or refreshed. For commission-related store configuration, use the applicable store payment-method workflow with the same approval and test-data safeguards. ## Troubleshooting If the menu item is absent, check the account level, read-only status, add-on availability, and add-on flag. A direct route, empty list, or visible category does not grant entitlement, confirm billing, or establish a provider connection. --- **Related guides:** [Add-ons overview](https://docs.ordering.co/docs/products/dashboard/addons/) · [Apps & Addons catalog](https://docs.ordering.co/docs/products/dashboard/apps-addons-catalog/) · [Store payment methods](https://docs.ordering.co/docs/products/dashboard/stores/view-edit-store/) ## Related procedures - [Stripe Connect V2: automatic payouts to stores and drivers](https://docs.ordering.co/docs/products/dashboard/addons/stripe-connect/payouts-v2/) - [Set up Stripe Connect as a business owner](https://docs.ordering.co/docs/products/dashboard/addons/stripe-connect/business-owner-setup/) - [Set up Stripe Connect for your platform](https://docs.ordering.co/docs/products/dashboard/addons/stripe-connect/platform-setup/) ## Understand the Connect configuration Stripe Connect can support a marketplace that collects customer payments and distributes funds to connected accounts. Before changing a setting, define the merchant-of-record responsibility, charge pattern, fee collection, negative-balance liability, and the onboarding path for each connected account. A visible field or successful redirect does not establish any of those decisions. ## Historical account topology The preserved setup describes one primary Stripe account for the Dashboard and a separate Stripe account for each business. It says that different business accounts could be linked per business while the primary account remained the same. This is historical account-topology context only. It does not establish the current account model, OAuth path, onboarding, payment settlement, payout behavior, availability, or a successful connection. Use the [historical platform procedure](https://docs.ordering.co/docs/products/dashboard/addons/stripe-connect/platform-setup/) only to reconcile an approved existing integration. > **Historical OAuth procedure** > > The source below records a legacy OAuth-style redirect configuration, including `https://apiv4.orderingplus.com/v400/en/YOURPROJECTNAME/payments/stripe_connect/callback`. Preserve that endpoint only for an approved existing integration; do not treat it as a default for a new Connect implementation. Review Stripe’s current [onboarding guidance](https://docs.stripe.com/connect/onboarding) and [account capability requirements](https://docs.stripe.com/connect/account-capabilities) before configuring a connected account. ## Configure Dashboard fields The captured Dashboard flow shows separate **Client ID** fields for sandbox and production. Enter only the corresponding approved identifier in its intended field; do not copy credentials or connected-account identifiers into documentation or messages. [![Stripe Connect Client ID settings](https://docs.ordering.co/assets/images/8a820d1c3d3ca78d19efbbb0-f8a77d6d939b1d4156ed63354c63b491.png)](https://docs.ordering.co/assets/files/b7a83ba12286f17339c4660b-a446a6eb2b7026bbc8a85d5c80de834b.png) [![Stripe Connect sandbox and production Client ID fields](https://docs.ordering.co/assets/images/0f284852becf4092ff0175ad-5a5685aee653e5808af4416bb672412f.png)](https://docs.ordering.co/assets/files/54e64a7c37831963e1179664-0a85a2bfd1246210d3f8602296fec557.png) ## Configure a store connection 1. Open the intended store’s payment-method settings. 2. Select **Stripe Connect** when that payment method is available for the store. 3. Select **Connect With Stripe** only in an approved configuration workflow. 4. In the Stripe page, select the intended connected account and complete the provider’s visible authorization or onboarding requirements. 5. Return to the Dashboard and review the displayed fields before selecting **Save**. [![Store payment methods with Stripe Connect](https://docs.ordering.co/assets/images/2e8ae905587bbd1e39c9f65e-0afbafb7d0ae2de5ce8acf2e9417d068.png)](https://docs.ordering.co/assets/files/6c665c68241286eb25f4165f-7f7845fc0511b29fb3df335a877ab274.png) If the store UI exposes **Fixed Fee** or **Percentage Fee**, record the approved commercial calculation before saving. A fee field, redirect, returned identifier, or accepted save does not prove a charge was created, a transfer was made, or a payout is eligible. [![Stripe Connect store fee settings](https://docs.ordering.co/assets/images/32c404d55d3bc7ed316237be-5eb629ea8894f221c561475ed65c5f65.png)](https://docs.ordering.co/assets/files/80c8da3c295bcdaf764e6a9f-d6d8935611995cf588e2035f0350f74d.png) ## Default percentage split In the default Stripe Connect setup, the platform's configured **Percentage Fee** is calculated from the **product subtotal only**. That percentage goes to the platform account. The remaining product subtotal, together with the full tax amount, delivery fee, and driver tip, goes to the connected business account. Tax, delivery, and tip amounts are not included in the platform percentage calculation. For example, with a product subtotal of 100 and a 10% platform fee, 10 goes to the platform and 90 of the product subtotal goes to the business. The order's taxes, delivery fee, and driver tip are added to the business's share. This example is before any Stripe processing fee, which is separate from the platform percentage; confirm its allocation in the applicable Stripe charge rather than assuming which account bears it. A driver tip reaching the business account does **not** automatically pay the driver. [Driver Invoice](https://docs.ordering.co/docs/products/dashboard/reports/invoice-manager/driver-invoices/) can document the amount owed, but the actual driver payment is a separate process. If a project uses a custom payment flow, verify its configuration and a test transaction before applying this default split. ## Typical marketplace uses - A multi-vendor marketplace can collect a customer payment and distribute funds under its approved payment design. - A marketplace that connects customers with service providers can use connected accounts when its approved configuration assigns payment responsibilities accordingly. - A recurring-payment flow can involve multiple stakeholders, but recurring billing and fund distribution still need their own approved Connect design. ## Confirm readiness separately A connection can still have outstanding provider requirements, disabled capabilities, incomplete onboarding, or an ineligible payment flow. Use Stripe’s current provider status and the approved test environment to verify those independently. Do not use a live order, live credential, or customer account as a documentation test. ## Related integration [Explore Stripe Connect for platform and business payment splits](https://www.ordering.co/integrations/stripe-connect/) for an overview of the integration. Use this guide for configuration and operating details.