The organization's Stripe account, read from Stripe
Retrieves the account from Stripe on every read (never a stored state presented as current): status (onboarding until details are submitted and charges enabled; active; restricted when Stripe disabled charges or lists past-due requirements; disconnected), the Stripe flags, requirements, capabilities, custody "organization", platform_fee_bps 0, and next_actions (complete_onboarding while incomplete, open_stripe_dashboard once active). 404 STRIPE_ACCOUNT_NOT_FOUND inside the caller's own authority when the organization has none; 403 without one. Never lifecycle-gated.
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
Path parameters
Run402 project ID. Public IDs are not UUIDs.
The project through which the organization's Stripe account is reached. A service_key acts only for its OWN project; principals and grant keys authorize via project.stripe.manage (mutations) or project.read (reads). The account belongs to the project's owning organization, read fresh.
Headers
SIWX auth header — base64-encoded JSON payload containing a signed CAIP-122 (EIP-4361) message. See https://docs.x402.org/extensions/sign-in-with-x.
Response
The account state.
Example response
{
"next_actions": [
{
"method": "POST",
"path": "/tiers/v1/hobby",
"auth": "x402"
}
]
}Changes
No recorded changes to this operation across all 1 revision of this API.