---
title: "Set up Stripe Connect for your platform"
description: "Reconcile an existing platform-level Stripe Connect OAuth setup, including client identifiers and callback URIs."
canonical: https://docs.ordering.co/docs/products/dashboard/addons/stripe-connect/platform-setup/
---

# Set up Stripe Connect for your platform

[Back to the main guide](https://docs.ordering.co/docs/products/dashboard/addons/stripe-connect/)

## Historical platform OAuth configuration

> **Use only to reconcile an existing integration**
>
> This procedure preserves a historical OAuth-style setup and its captured screens. It is not a new Connect implementation guide. Before changing an existing configuration, identify the account model, onboarding owner, charge pattern, merchant-of-record responsibility, fee collection, and negative-balance liability, then compare the current setup with Stripe’s [onboarding guidance](https://docs.stripe.com/connect/onboarding).

## Historical account topology

The preserved procedure describes one primary Stripe account for the Dashboard and a separate Stripe account for each business. It says that a different business account could be linked per business while the primary account remained the same.

This is a record of the captured legacy topology, not a current configuration model. It does not establish an available authorization or OAuth path, account onboarding, payment settlement, payout behavior, or a successful connection.

## Prepare the platform account

1. Use the intended Stripe platform account and complete the provider requirements that apply to it. A Stripe account or Dashboard session does not by itself establish live-payment capability.
2. In Stripe Dashboard, open **Settings** and then **Connect**.

![Stripe Connect settings](https://docs.ordering.co/assets/images/507537a5537f6e995d12d2fb-02c9d60d101c4986f67fd3b95fe9766a.png)

[Open the historical full-size reference](https://d.pr/i/gWpo65)

3. Review **Onboarding Options** and the country scope for the accounts that will connect. Current Stripe onboarding requirements vary by account and country.

![Stripe onboarding options](https://docs.ordering.co/assets/images/e52f7f287744d6cfd991978b-484faff376a3c386f4d793aa5c6a4099.png)

[Open the historical full-size reference](https://d.pr/i/RgEU9j)

![Stripe account country selection](https://docs.ordering.co/assets/images/8a337ae30a10ebdf2fb5e26a-c142fa23f1173d91077c590aa4ac2598.png)

[Open the historical full-size reference](https://d.pr/i/0dzlEM)

## Preserve the legacy callback only when applicable

The captured OAuth flow instructs an existing integration to register this callback URI, replacing `<project>` with the approved project identifier:

`https://api.orderingplus.com/v400/en/<project>/payments/stripe_connect/callback`

The source says to register it in both live and sandbox modes. Confirm the actual callback, mode, and OAuth availability with the integration owner before changing anything; this document does not establish that the legacy endpoint is deployed or appropriate for a new setup.

The same source says its legacy flow enabled **OAuth for Standard Accounts**. Keep that label only as historical context for an approved existing integration; it does not verify a current OAuth setting, account type, authorization path, or availability.

![Historical Stripe OAuth callback settings](https://docs.ordering.co/assets/images/68730f0fe3e96e7b85ad09e8-e5f9bc0a9ec9754e22546c24c34e4bf0.png)

[Open the historical full-size reference](https://d.pr/i/hmvn1l)

## Store the approved client identifiers

The historical flow captures a **Live Client ID** and places the matching live and sandbox client identifiers in the Stripe Connect add-on settings. Use only approved values in the intended fields, and do not copy identifiers into tickets, messages, screenshots, or source control.

![Historical Stripe client identifier](https://docs.ordering.co/assets/images/512c330dbfc0c88e31a1f303-c09ee80e633fe5ac719c4f6cbcad5c63.png)

[Open the historical full-size reference](https://d.pr/i/USfHZW)

The captured Dashboard URL is `https://dashboard.orderingplus.com`; retain it only as a historical technical endpoint. In the captured UI, the operator opens **My Addons**, selects **Stripe Connect Addon**, enters the approved live and sandbox client identifiers, then selects **Save**.

![Historical Stripe Connect add-on settings](https://docs.ordering.co/assets/images/f684976e362a277b202bafdb-faccac68b4659d029894113705dc46a5.png)

[Open the historical full-size reference](https://d.pr/i/pkkWel)

## Link a business account

The business owner (or another authorized account holder) opens the business payment-method settings, selects **Stripe Connect**, and uses the provider page to select the intended Stripe account. Return to the Dashboard and review any populated fields before saving. A populated field or saved view does not prove a connected account is onboarded or eligible for charges, transfers, or payouts.

![Historical business payment-method setting](https://docs.ordering.co/assets/images/e0bbca36093f53e945ca1541-d4892b1ab4ef62b245ec4d727a1bd487.png)

[Open the historical full-size reference](https://d.pr/i/kt3lt7)

![Historical Stripe account selection](https://docs.ordering.co/assets/images/8ca02268a8fb2d4565dbf0f0-399255a22c9c5f4d6e87c4e999a04fea.png)

[Open the historical full-size reference](https://d.pr/i/1pzQLu)

![Historical connection confirmation screen](https://docs.ordering.co/assets/images/33b3d7bdf126418a18370e0b-25f8d10b3c7ee3b915b1f94b44179f03.png)

[Open the historical full-size reference](https://d.pr/i/uMzdP5)

## Verify readiness separately

After the connection step, inspect the provider’s current account requirements and requested capabilities in the approved test environment. Do not infer payment readiness from the redirect, a client identifier, or a saved Dashboard field.