---
title: "Detach the organization's Stripe account from the platform"
method: DELETE
path: "/projects/v1/{project_id}/stripe/account"
tags: ["Projects"]
---

# Detach the organization's Stripe account from the platform

`DELETE /projects/v1/{project_id}/stripe/account`

## Request

- Base URL: `https://api.run402.com`
- URL: `https://api.run402.com/projects/v1/{project_id}/stripe/account`
- Auth: one of:
  - HTTP bearer
  - API key in header `SIGN-IN-WITH-X`
  - HTTP bearer
  - HTTP bearer

Removes the connected account from Run402's platform (the Stripe account itself is untouched and keeps working as a normal Stripe account the organization controls), marks it disconnected, audits, and emits stripe_account_disconnected on the organization feed. Connecting again creates a NEW Stripe account. Behind the lifecycle gate.

## Path parameters

- `project_id` string, required: Run402 project ID. Public IDs are not UUIDs.

## Headers

- `SIGN-IN-WITH-X` string, required

## Response `200`

Detached.

- StripeAccountDisconnectResponse
  - `disconnected` true, required
  - `account_id` string, nullable, required
  - `stripe_account_unaffected` true, required
  - `org_id` string, uuid, required
  - `next_actions` NextAction[]
    - `type` string, required: Advisory machine-readable action type such as retry, authenticate, submit_payment, fund_wallet, renew_tier, check_usage, resume_deploy, edit_request, edit_migration, contact_support, upgrade_client, poll (poll the project events feed — appended when the envelope carries a correlated_platform_incident), or hand_to_member (on a commit/promote response that just activated a public site: show the human urls.site and urls.console, relay Run402's offer to promote the build on @run402com, and ask yes or no — see `credited_as` below).
    - `method` string
    - `path` string
    - `auth` string
    - `why` string
    - `credited_as` string, nullable: `hand_to_member` only. The caller's own live presence name in the project's default room, else that room's most recently active live presence, else `null` — in which case `why` tells the agent that joining the room with a name (`run402 rooms join --name ...`) is how the promotion credits it.
    - `body` object: `hand_to_member` only. A ready-to-send `POST /feedback/v1` template: `{ project_id, message: "promote: yes", handle? }`.

## Other responses

- `403`: Not authorized, or the lifecycle gate.
- `404`: STRIPE_ACCOUNT_NOT_FOUND.
- `503`: STRIPE_CONNECT_UNAVAILABLE.

---

[API](https://skmtc.dev/run402/apis/run402-api.md) · [All operations](https://skmtc.dev/run402/apis/run402-api/llms.txt) · [OpenAPI document](https://skmtc.dev/run402/apis/run402-api/revisions/893607557f50?raw)