Stripe Connect platform
Enabling Connect on the platform's Stripe account, choosing Standard or Express accounts, the keys, the Connect webhook endpoint and what a workspace sees.
With Stripe Connect a workspace gets (or links) its own Stripe account through hosted Stripe pages. Charges are direct charges: made on the workspace's account with the platform's key and the header Stripe-Account. The workspace is the merchant of record and pays Stripe's fees; the platform adds none.
Decide: Standard or Express#
The application asks for an account type and has no default, because the choice moves risk:
| Standard | Express | |
|---|---|---|
| Dashboard for the workspace | The full Stripe Dashboard | The lighter Express Dashboard |
| Onboarding | Hosted by Stripe | Hosted by Stripe |
| Negative balances (refunds or disputes larger than the balance) | Stripe's risk | The platform's risk |
| Disputes and refunds outside this system | The workspace can handle them in its Dashboard | Only through this system |
The type applies to accounts created from then on; existing accounts keep theirs.
Enable Connect#
- Sign in to the Stripe account that will be the platform (a separate account from any workspace's is cleanest).
- Settings → Connect → get started. Complete the platform profile; Stripe may ask what the platform does and who its users are.
- Under Connect → Settings → Branding, set the name and icon workspaces see during onboarding.
- Do this in test mode first. Live mode needs the platform profile approved by Stripe.
Add the application#
Super → Platform apps → Stripe:
- Platform publishable key and secret key — Developers → API keys of the platform account (
pk_test_…/sk_test_…for Test). - Connected account type — see above.
Save, then Verify: one call reads the platform account and one lists connected accounts, which Stripe refuses unless Connect is enabled.
Register the Connect webhook#
Developers → Webhooks → Add endpoint:
- Endpoint URL — the Platform webhook endpoint shown on the application's page.
- Choose Listen to events on Connected accounts. (An endpoint for "your account" receives nothing from workspaces.)
- Select the events listed under Events to send on the application's page:
account.updated,account.application.deauthorizedand the payment events. - Copy the endpoint's signing secret (
whsec_…) into Connect webhook signing secret.
Workspaces are offered Connect Stripe from this moment.
What a workspace does#
Settings → Gateways → Connect Stripe. The system creates the account at Stripe, then sends the owner to Stripe's onboarding pages. When Stripe has what it needs it sends the owner back; the set is Enabled as soon as Stripe accepts charges, which can be minutes or — when documents are reviewed — days. Meanwhile the set shows what Stripe still asks for, and Continue at Stripe opens a fresh link (Stripe's links expire after a few minutes and work once).
Bank payments (ACH): offered through a connected set only when the account's us_bank_account_ach_payments capability is active. Until then products show cards only for that set.
Ending a connection#
Disconnect on the set ends it here: the set is Revoked and no call is made for the account again. The Stripe account is the workspace's and is left as it is. If a workspace disconnects the platform inside Stripe instead, Stripe reports account.application.deauthorized and the set is revoked the same way.
Go live#
- [ ] Platform profile approved by Stripe for live mode.
- [ ] A Live application with
pk_live_…/sk_live_…and the account type. - [ ] A live Connect webhook endpoint with the live application's URL and its own signing secret.
- [ ] One workspace connected, one small real payment and refund.
Common errors#
"Only Stripe Connect platforms can work with other accounts" on Verify — Connect is not enabled on that Stripe account, or the key belongs to another account.
The set stays Restricted — the set's page lists what Stripe still needs (currently_due). The owner supplies it through Continue at Stripe.
Payments are made but stay Pending here — the Connect endpoint is missing, listens to "your account" instead of connected accounts, or its signing secret was not saved. The application's page shows the latest deliveries.